Skip to content

Add Captail landing page - #15

Merged
FaulMit merged 2 commits into
mainfrom
agent/captail-landing-page
Aug 3, 2026
Merged

Add Captail landing page#15
FaulMit merged 2 commits into
mainfrom
agent/captail-landing-page

Conversation

@FaulMit

@FaulMit FaulMit commented Aug 3, 2026

Copy link
Copy Markdown
Owner

What changed

  • add a polished static Captail landing page under /site
  • add responsive desktop/mobile layouts, real product screenshots, accessible focus states, reduced-motion support, metadata, favicon, robots, and sitemap
  • add a GitHub Pages deployment workflow
  • add a branded, clickable Windows download button and website link to README
  • ignore local visual QA output

Why

Captail needs a public product page that immediately explains its reliability-focused Instant Replay promise and routes Windows users to the latest release.

User impact

Visitors get a focused product overview, verified capability and limitation details, direct Windows download access, and clear source/contribution links. The desktop application is unchanged.

Validation

  • node --check site/script.js
  • html-validate site/index.html
  • SVG XML parse
  • git diff --check
  • Playwright desktop QA at 2048×1085
  • Playwright mobile QA at 390×844
  • no browser console warnings or horizontal mobile overflow
  • prefers-reduced-motion verified

@FaulMit
FaulMit marked this pull request as ready for review August 3, 2026 12:42
@FaulMit
FaulMit merged commit 835bb71 into main Aug 3, 2026
5 of 6 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b0bea738d6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread site/styles.css
Comment on lines +584 to +585
[data-reveal] { opacity: 0; transform: translateY(24px); transition: opacity 650ms cubic-bezier(.2,.7,.2,1), transform 650ms cubic-bezier(.2,.7,.2,1); }
[data-reveal].is-visible { opacity: 1; transform: none; }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep reveal content visible without JavaScript

When JavaScript is disabled, blocked, or fails to load, every element marked data-reveal remains permanently transparent because visibility is only restored by script.js. This hides most headings, feature descriptions, screenshots, compatibility details, and FAQ entries while leaving large empty sections; make content visible by default and apply the hidden animation state only after JavaScript initializes.

Useful? React with 👍 / 👎.

Comment thread site/index.html
"name": "Captail",
"applicationCategory": "UtilitiesApplication",
"operatingSystem": "Windows 10 version 2004 or newer, Windows 11",
"softwareVersion": "0.1.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Avoid hard-coding the release version in the landing page

When .github/workflows/release.yml publishes any version after 0.1.5 through its independent workflow_dispatch version input, this value and the visible v0.1.5 labels remain unchanged because the release workflow neither edits nor deploys site/. The page links to /releases/latest, so users and search engines will receive conflicting version information unless the site derives the version dynamically or the release process updates every occurrence.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant