# Cognitievo Static Website

This repository contains the tracked static website for Cognitievo and a separate local-only draft environment used to explore new landing-page and supporting-page directions safely before touching deployable files.

## Overview

- Pure HTML, CSS, and JavaScript
- No build step required for local preview
- Tracked production pages live at the repo root
- Local review concepts live in `_drafts/` and are intentionally ignored by git
- Deployment is triggered only when approved changes are ported into tracked files

## Repository Structure

```text
StaticWebsite/
|-- index.html
|-- company.html
|-- careers.html
|-- digital-workers.html
|-- styles.css
|-- script.js
|-- _headers
|-- _redirects
|-- assets/
|-- _drafts/
|-- .gitignore
`-- README.md
```

## Tracked Production Files

### Pages

- `index.html` - current tracked homepage
- `company.html` - current tracked company page
- `careers.html` - current tracked careers page
- `digital-workers.html` - current tracked digital workers page

### Shared assets

- `styles.css` - tracked site-wide styling
- `script.js` - tracked site-wide JavaScript
- `assets/` - images, icons, and other static assets

### Hosting configuration

- `_headers` - static security and browser-behavior headers
- `_redirects` - static redirect rules

## Draft Review Environment

The `_drafts/` folder is the safe review space for new design and content directions.

Important:

- `_drafts/` is ignored by git through the repo-root `.gitignore`
- work in `_drafts/` does not change deployable pages by itself
- the draft environment is intended for review, copy iteration, and visual validation before promotion into tracked files

Current draft review set:

- `_drafts/landing-v2.html`
- `_drafts/company-v2.html`
- `_drafts/digital-workers-v2.html`
- `_drafts/cyber-security-v2.html`
- `_drafts/landing-v2.css`
- `_drafts/README.md`

Current draft direction:

- more aligned to the Cognitievo brand system
- more enterprise-first in tone and structure
- clearer on governed deployment, operating fit, and accountable digital workers
- includes a dedicated cyber security page
- intentionally excludes careers from the draft review flow to reduce noise

## Local Preview

You can preview either the tracked site or the draft site locally.

### Option 1: open files directly

- Open `index.html` for the tracked site
- Open `_drafts/landing-v2.html` for the draft site

### Option 2: run a local static server

From the `StaticWebsite` folder:

```powershell
python -m http.server 8000
```

Then browse to:

- `http://127.0.0.1:8000/` for the tracked site
- `http://127.0.0.1:8000/_drafts/landing-v2.html` for the draft homepage

If you prefer Node:

```powershell
npx serve .
```

## Safe Update Workflow

Use this workflow when exploring or approving redesign work.

1. Build and review concepts inside `_drafts/`.
2. Validate copy, layout, navigation, and brand alignment locally.
3. Approve the draft direction before touching tracked production files.
4. Port approved changes into tracked files such as `index.html`, `company.html`, `digital-workers.html`, and `styles.css`.
5. Re-review the tracked version before merging or pushing to any branch that triggers deployment.

This keeps experimentation isolated and reduces the risk of accidental rebuilds from half-finished landing-page work.

## Suggested Promotion Order

When the current draft direction is approved, a safe port order is:

1. Update `index.html`
2. Update `company.html`
3. Update `digital-workers.html`
4. Add or update a tracked cyber security page if approved
5. Move approved draft styling from `_drafts/landing-v2.css` into `styles.css` or another tracked stylesheet
6. Reconcile any shared navigation, footer, legal, or asset changes across the tracked pages

## Content And Contact Notes

- Avoid exposing raw public email addresses repeatedly across page templates where possible
- Prefer CTA-driven contact paths, booking flows, or dedicated contact experiences over scrapeable footer email text
- Keep public claims measured, especially for cyber security, compliance, and assurance positioning
- Treat `_drafts/` copy as review material until it has been intentionally promoted into tracked pages

## Frontend Conventions

- Edit HTML files directly for page-level content changes
- Edit `styles.css` for tracked global styling changes
- Keep draft-only styling in `_drafts/landing-v2.css` until approved
- Reuse the existing modal and navigation patterns unless there is a clear reason to change them
- Favor semantic HTML, keyboard-accessible interactions, and descriptive alt text

## Deployment Notes

- This is a static site with no application build pipeline required in the repo itself
- Deployment behavior depends on the hosting setup connected to the tracked files in this repository
- `_headers` currently sets:
  - `X-Frame-Options: DENY`
  - `X-Content-Type-Options: nosniff`
  - `Referrer-Policy: strict-origin-when-cross-origin`
- `_redirects` is available for static redirect handling when needed

## Maintenance Checklist

When updating tracked pages:

1. Review navigation consistency across all tracked pages
2. Review footer consistency across all tracked pages
3. Confirm assets are referenced with the correct relative paths
4. Check local preview on desktop and mobile widths
5. Review copy for customer-facing tone and claim accuracy
6. Re-check any contact paths, legal links, and modal content

## Browser Support

- Current Chrome and Edge
- Current Firefox
- Current Safari
- Current mobile browsers

## Ownership

This README is intended to help contributors understand the difference between:

- tracked production files that can affect deployment
- ignored draft files used for safe local exploration

Update this document whenever the review workflow, page set, or deployment assumptions change materially.