[Website/Content] Define the complete SightAdapt™ website content and page copy

[KeyffMS]

Parent project: #95
Depends on: #96, #99, #103, #104
Supports: #97, #100, #101, #102, #105, #106, #108, #110, #111, #112

Objective

Define the complete information architecture, visible copy, navigation, calls to action, trust content and asset usage for the public SightAdapt™ product website.

The implementation target is a product section of the Aiteracja website rather than a separate canonical subdomain.

Canonical URL decision

• Canonical product root: https://aiteracja.pl/sightadapt/
• GitHub Pages build/origin and fallback: https://keyffms.github.io/SightAdapt/
• Optional convenience address: https://sightadapt.aiteracja.pl/
• The convenience subdomain must permanently redirect to https://aiteracja.pl/sightadapt/; it must not host a competing indexed copy.
• All canonical tags, structured data, release links, directory entries and social profiles must use the /sightadapt/ URL.
• Public paths use lowercase ASCII and trailing slashes.

Canonical SVG brand assets

Use the repository assets merged in PR #123:

• SightAdapt product mark
• SightAdapt™ horizontal lockup for light backgrounds
• SightAdapt™ horizontal lockup for dark backgrounds

Raw asset URLs for site builds:

• https://raw.githubusercontent.com/KeyffMS/SightAdapt/main/assets/brand/sightadapt-mark.svg
• https://raw.githubusercontent.com/KeyffMS/SightAdapt/main/assets/brand/sightadapt-lockup-dark.svg
• https://raw.githubusercontent.com/KeyffMS/SightAdapt/main/assets/brand/sightadapt-lockup-light.svg

Asset usage rules

• Use the dark lockup in the light header and light-content areas.
• Use the light lockup in the dark hero and footer.
• Use the standalone mark for favicon, compact navigation, repository links and small product cards.
• Do not stretch, skew, recolor, rotate or add effects to the assets.
• Keep clear space around a lockup of at least half the mark height.
• Minimum visible lockup width: 180px; below that use the standalone mark.
• The visual artwork includes ™; accessible names should normally be SightAdapt home or SightAdapt logo rather than forcing screen readers to announce the trademark symbol repeatedly.
• Do not use ®.

Trademark notation policy

Visible first or most prominent use on every page must be SightAdapt™.

Examples:

• page logo: SightAdapt™;
• hero/product heading: SightAdapt™;
• release title: SightAdapt™ 0.5.0.50 Alpha.

Subsequent prose may use plain SightAdapt for readability.

Every page footer must include:

SightAdapt™ is an unregistered product mark used by KeyffMS / aiteracja.pl.

Third-party trademark wording must remain separate:

Third-party product names and trademarks are the property of their respective owners and are used only to identify user-selected applications. SightAdapt is not affiliated with or endorsed by those owners.

Audience

Primary audiences:

1. Windows users seeking per-application color and contrast adaptation.
2. People evaluating accessibility tools for themselves, relatives or colleagues.
3. Open-source developers and technical reviewers.
4. Accessibility specialists evaluating a non-medical desktop utility.
5. Users searching for the exact product name after seeing a recommendation, repository or release link.

Content voice

• Direct, factual and calm.
• Accessibility-focused without medical promises.
• Technical claims must be verifiable from the current release.
• State alpha limitations clearly.
• Prefer short paragraphs and descriptive headings.
• Avoid revolutionary, perfect, works everywhere, clinically proven, safe for everyone and similar unsupported claims.
• Describe SightAdapt as a visual-accessibility and display-personalization tool, not a treatment or diagnostic product.
• Use free and open source, not freeware.

Language policy

The initial public product site should be written in English to match the application UI, repository and international open-source distribution.

The structure must allow a maintained Polish translation later. Do not publish an incomplete machine-translated language switch. If a Polish version is added, every legal, privacy, download and safety page must be translated together.

Global site structure

Header

Required elements:

• SightAdapt™ lockup linked to /sightadapt/;
• primary navigation: Features, Download, Documentation, FAQ;
• secondary navigation or menu: Releases, Privacy, Security, GitHub;
• prominent Download alpha action when a compliant release exists;
• responsive mobile navigation with keyboard-accessible disclosure behavior.

Header must remain understandable without icons. The current page must be indicated semantically and visually.

Alpha status banner

Display on home, download and documentation pages:

SightAdapt is currently an alpha release. Core functionality is available, but broad compatibility and endurance testing are still in progress.

Link alpha release to the current limitations section.

Footer

Footer groups:

• Product: Features, Download, Documentation, Releases.
• Project: GitHub, Issue tracker, Security, License.
• Policies: Privacy, Third-party notices, Trademark notice.
• Publisher: A SightAdapt project by KeyffMS / aiteracja.pl linked to the Aiteracja home page.

Required footer text:

SightAdapt™ is an unregistered product mark used by KeyffMS / aiteracja.pl.

SightAdapt is free and open-source software distributed under the MIT License. Third-party components remain subject to their respective terms.

Do not place tracking pixels, advertising scripts or behavioral analytics in the footer.

Sitemap and complete page content

1. Product home — /sightadapt/

Metadata

Title:

SightAdapt™ — per-application visual accessibility for Windows | Aiteracja

Description:

SightAdapt is a free, open-source Windows application that applies configurable color correction to selected application windows through an input-transparent overlay.

Hero

Eyebrow:

Free and open source · Windows 10 and 11 · Alpha

H1:

Adapt the application in front of you.

Lead:

SightAdapt™ applies configurable color correction to individual Windows application windows. Keep the rest of the desktop unchanged, assign profiles per application and stop every overlay immediately when needed.

Primary action:

Download SightAdapt™ Alpha

Secondary actions:

• View source on GitHub
• Read the documentation

Release summary beside or below the actions:

• current version;
• Windows x64;
• MIT licensed;
• alpha status;
• release date.

Hero visual:

• use an authentic screenshot of the configuration panel and an affected application window;
• do not use third-party private content;
• include alt text describing what changed visually rather than saying screenshot.

Suggested alt text:

SightAdapt configuration beside a Windows application showing a soft-invert visual profile applied only to that application window.

Immediate trust strip

Four short statements:

• No code injection
• No driver installation
• No screen-content telemetry
• Runs with the current user's privileges

Each statement links to How it works or Security for detail.

Problem and solution section

Heading:

Change one application, not your entire desktop.

Copy:

System-wide display filters can affect every monitor, application and notification. SightAdapt targets the active application through a separate overlay, allowing different applications to use different visual profiles while unrelated windows remain unchanged.

Main benefit cards

1. Profiles per application

   Assign a saved color profile to an application and let SightAdapt activate it when that application becomes active.

2. Separate native-menu correction

   Use the application profile for native popup menus or assign a different menu profile when menu contrast needs separate treatment.

3. Flexible overlay scope

   Choose the client area, full window, current screen or all screens according to the application and display setup.

4. Editable visual profiles

   Adjust output black and white levels, brightness, contrast, saturation and hue, then preview the result before assigning it.

5. Manual and automatic controls

   Toggle the active window temporarily or save an automatic application assignment.

6. Immediate shutdown

   Remove active overlays from the notification-area menu through the emergency-disable command.

How it works summary

Heading:

Three steps to a per-application profile.

Steps:

1. Select or activate an application.
2. Choose or create a visual profile.
3. Enable the assignment or use the temporary shortcut.

Link: See the complete quick start.

Profile examples section

Show the built-in profiles without promising suitability:

• None — leave the application unchanged.
• Exact invert — apply a fixed full inversion.
• Soft invert — use an editable lower-intensity starting profile.
• Custom profiles — duplicate and adjust a profile for a particular application or display.

Include a note:

Visual preferences are individual. SightAdapt does not choose a medically appropriate profile and does not replace professional advice.

Privacy and boundaries section

Heading:

Local settings. No screen-content upload.

Copy:

SightAdapt stores its configuration locally. The current alpha does not transmit captured screen content, does not inject code into target applications and does not install a kernel driver. Application assignments may include executable paths and file metadata stored in the local settings file.

Links: Read privacy details and Review security boundaries.

Open-source section

Heading:

Built in public.

Copy:

SightAdapt is developed in a public GitHub repository and distributed under the MIT License. Source code, architecture documentation, test results, issues and release history are available for inspection.

Actions:

• Browse the source
• Report an issue
• Read the license

Current limitations section

Heading:

Current alpha limitations

Visible summary:

• one foreground application session is corrected at a time;
• native menu-specific handling applies only to Win32 #32768 popup menus;
• protected or DRM-controlled content may not be capturable;
• elevated applications may require a compatible integrity level;
• remote desktop and some graphics drivers may behave differently;
• broad compatibility and endurance testing are incomplete.

Link: Read all known limitations.

Final CTA

Heading:

Try SightAdapt™ and inspect every part of it.

Actions:

• Download the current alpha
• View the GitHub repository

2. Features — /sightadapt/features/

Title:

SightAdapt™ features — profiles, overlays and Windows controls

H1:

Features designed around individual applications.

Required sections:

Application assignments

Explain persistent executable-based assignments, enable/disable state and automatic foreground activation.

Visual profile management

Explain built-in and user-defined profiles, duplication, renaming, editing, deletion constraints and preview behavior.

Available controls

List output black, output white, brightness, contrast, saturation and hue. Avoid implying color calibration accuracy.

Native popup menus

Explain inherited or separate menu profiles and clearly identify the Win32-only limitation.

Overlay scopes

Describe client area, full window, current screen and all screens, including the practical implications of each scope.

Shortcuts and notification-area controls

Document both global shortcuts and the emergency shutdown command. Link to the authoritative keyboard-control documentation.

Multi-monitor and DPI behavior

Describe per-monitor awareness and the fact that unusual display drivers or remote sessions may require testing.

Settings and migration

Explain local schema-versioned JSON settings, migration and atomic persistence without exposing implementation jargon unnecessarily.

What SightAdapt does not do

Required list:

• does not modify another application's files;
• does not inject code into another process;
• does not install a driver;
• does not upload screen content;
• does not bypass DRM or access controls;
• does not guarantee compatibility with every rendering framework;
• does not provide medical diagnosis or treatment.

3. Download — /sightadapt/download/

Title:

Download SightAdapt™ for Windows

H1:

Download the current SightAdapt™ release.

Release card

Display from authoritative release metadata:

• product version;
• release date;
• alpha/stable status;
• supported Windows versions;
• architecture;
• archive size;
• SHA-256 checksum;
• link to release notes;
• link to source tag;
• link to SBOM and legal bundle when available.

Primary action:

Download SightAdapt™ for Windows x64

Secondary action:

View this release on GitHub

System requirements

• Windows 10 version 2004 or later, or Windows 11;
• x64 processor;
• user permission to start a desktop application;
• compatible desktop composition and graphics driver.

Install and start

1. Download only from aiteracja.pl, the official GitHub repository or an approved package listing.
2. Verify the checksum when practical.
3. Extract the archive to a user-controlled directory.
4. Start SightAdapt.exe.
5. Use the notification-area icon to open configuration.

Checksum verification

Provide a current PowerShell example using the published filename:

Get-FileHash .\SightAdapt-<version>-win-x64.zip -Algorithm SHA256

Explain that the output must match the checksum shown on the release page.

Windows reputation warning

Explain factually that unsigned or newly published open-source binaries may trigger Microsoft Defender SmartScreen. Do not instruct users to disable system protection. Users should verify the source, hash and release page before choosing whether to run a file.

Removal

Explain how to exit the application, remove its files and optionally delete:

%LOCALAPPDATA%\SightAdapt\settings.json

Warn that deleting the settings file removes saved profiles and assignments.

Alpha warning

This is an alpha release. Keep the emergency-disable command available and test the application with non-critical work before relying on it for extended sessions.

4. Documentation hub — /sightadapt/docs/

Title:

SightAdapt™ documentation

H1:

Set up SightAdapt and understand each control.

Required navigation groups:

Getting started

• install and first run;
• notification-area menu;
• quick profile assignment;
• temporary correction for the active window.

Applications

• add an application;
• enable, disable and remove assignments;
• understand executable identity and path storage;
• configure automatic mode.

Profiles

• built-in profiles;
• create and duplicate;
• edit controls;
• rename and delete;
• choose None;
• profile preview limitations.

Menus and scopes

• native popup-menu profiles;
• inherited versus explicit menu settings;
• client/full-window/screen scopes;
• limitations for WPF, WinUI, Electron, Qt and custom-rendered menus.

Keyboard and emergency controls

• Ctrl+Alt+I;
• Ctrl+Alt+Shift+I;
• emergency-disable behavior;
• shortcut registration conflicts.

Troubleshooting

• elevated target applications;
• missing tray icon;
• overlay not appearing;
• menu correction not applying;
• multiple monitors and scaling;
• remote desktop;
• corrupted settings and recovery;
• protected content.

Developer documentation

Link to build, architecture, tests, contribution and security documents in GitHub.

5. How it works — /sightadapt/how-it-works/

Title:

How SightAdapt™ works on Windows

H1:

A separate overlay, not a modification of the target application.

Required explanation:

1. SightAdapt observes the foreground window and resolves the corresponding application assignment.
2. It creates or retargets an input-transparent overlay.
3. The Windows Magnification API applies the selected color transform to the chosen source area.
4. Filtering prevents the overlay from recursively capturing itself.
5. Native popup menus may receive transient overlays when supported.
6. Emergency shutdown removes active overlays.

Security-boundary statement:

SightAdapt does not inject DLLs, write target-process memory or modify target application files. It reads limited window and process metadata required to identify the selected application.

Add a simple architecture diagram with text alternatives and a link to the full architecture documentation.

6. FAQ — /sightadapt/faq/

Include concise answers to at least these questions:

1. Is SightAdapt free?

   Yes. SightAdapt is free and open source under the MIT License.

2. Does SightAdapt change application files?

   No. It uses a separate Windows overlay and does not modify the target application's installed files.

3. Does it inject code into other applications?

   No. The current alpha does not use DLL injection or write another process's memory.

4. Does it record or upload my screen?

   The current alpha does not save or transmit captured screen content. See the privacy and security pages for the exact boundaries.

5. Why does it store executable paths?

   Paths are used locally to identify saved application assignments. A path can contain a Windows account or organization name, so it should be redacted from public bug reports when necessary.

6. Does it work with every application?

   No guarantee is made. Framework, privilege level, DRM, remote sessions and graphics drivers can affect behavior.

7. Can it correct only menus?

   For supported native Win32 popup menus, an application can use None while an explicit menu profile is assigned. Custom-rendered menus are not separately detected.

8. Is SightAdapt a medical device?

   The current project is a general-purpose visual-accessibility and display-personalization utility. It does not diagnose or treat medical conditions.

9. Why might Windows show a warning?

   New or unsigned binaries may have limited reputation. Download only from official project-controlled sources and verify the published checksum.

10. How do I stop all overlays?

    Use Emergency disable all overlays from the notification-area menu, or exit SightAdapt.

11. Can I build it myself?

    Yes. Link to the documented .NET 8 build and publish instructions.

12. Where do I report a problem?

    Link to the GitHub issue tracker and security-reporting route, with a warning not to attach private screenshots or unredacted paths.

7. Releases — /sightadapt/releases/

Title:

SightAdapt™ release history

H1:

Public, dated SightAdapt releases.

Display:

• current recommended release;
• all retained releases in reverse chronological order;
• version, date, status, summary, supported platform and GitHub Release link;
• checksums, SBOM and legal files per release;
• withdrawn-release notices without silently deleting history;
• clear distinction between source archives and official Windows binaries.

GitHub Releases remain authoritative; the website must not host divergent binaries.

8. Privacy — /sightadapt/privacy/

Content must be generated from the approved output of #86 and must cover:

• data read by the application;
• data stored locally;
• executable paths and metadata;
• settings location;
• absence or presence of network requests;
• telemetry and crash reporting status;
• deletion instructions;
• support-data submission and redaction;
• project contact/controller details when support data is received;
• policy version and effective date.

Required summary near the top:

The current SightAdapt alpha stores configuration locally and does not transmit captured screen content or behavioral telemetry.

Do not publish this sentence if implementation behavior changes.

9. License and notices — /sightadapt/legal/

Title:

SightAdapt™ license and legal notices

Required sections:

• SightAdapt MIT License;
• third-party component notices;
• Microsoft/.NET redistribution notices;
• dependency inventory and SBOM links;
• SightAdapt™ unregistered product-mark notice;
• third-party trademark and no-endorsement notice;
• DRM/non-circumvention statement;
• general warranty limitation consistent with the applicable licenses;
• links to source and release-specific legal files.

Required trademark text:

SightAdapt™ is an unregistered product mark used by KeyffMS / aiteracja.pl. The ™ notation identifies product branding and does not represent a registered trademark.

10. Security — /sightadapt/security/

Title:

SightAdapt™ security and reporting

Required sections:

• current application security boundaries;
• no injection, driver, saved screen content or transmitted screen content;
• current-user privilege model;
• elevated-application limitation;
• emergency shutdown;
• alpha security-review status;
• how to report a vulnerability privately;
• information that must not be posted publicly;
• link to SECURITY.md and current known limitations.

11. Support and contact — /sightadapt/support/

Title:

SightAdapt™ support and contact

Required paths:

• usage questions: documentation and FAQ;
• reproducible defects: GitHub issue tracker;
• feature requests: GitHub issue tracker;
• security issues: private security route;
• general publisher information: Aiteracja page.

Bug-report checklist:

• SightAdapt version;
• Windows version;
• monitor arrangement and scaling;
• target application and framework when known;
• target privilege level;
• exact reproduction steps;
• whether emergency disable remained available;
• sanitized logs or paths.

Privacy warning:

Do not attach screenshots containing private information or publish unredacted paths, usernames, organization names or confidential application content.

Visual content inventory

The site implementation should plan for these authentic visual materials:

1. configuration-panel overview;
2. application assignment list;
3. profile editor and preview;
4. native-menu profile configuration;
5. overlay-scope selector;
6. notification-area menu including emergency disable;
7. before/after example using project-owned or purpose-created content;
8. simplified architecture diagram.

Every visual requires:

• meaningful alt text;
• no private user data;
• no third-party copyrighted content used as decoration;
• no implication of endorsement by applications visible in screenshots;
• a documented source and capture version.

Decorative gradients and abstract shapes must not replace functional screenshots where users need to understand the product.

SEO and structured-content requirements

Each page must have:

• one unique <title>;
• one unique meta description;
• one H1;
• canonical URL under https://aiteracja.pl/sightadapt/;
• Open Graph title, description, URL and image;
• crawlable textual content rather than text embedded only in images;
• descriptive internal links;
• inclusion in sitemap.xml when public and indexable.

The home page should expose SoftwareApplication structured data with accurate fields only:

• name: SightAdapt;
• operating system: Windows 10 and Windows 11;
• application category: accessibility or utilities as supported by the schema implementation;
• price: 0 with an appropriate currency only if required by the selected schema shape;
• open-source license URL;
• source repository;
• current version derived from release metadata;
• canonical download or release page.

Do not add fabricated ratings, review counts, awards or medical categories.

Accessibility requirements for content

• Use semantic heading order without skipped structural levels.
• Keep link text meaningful out of context.
• Do not identify controls only by color or position.
• Define abbreviations such as DRM, DPI and SBOM on first use.
• Provide visible keyboard focus and skip navigation.
• Keep important safety and alpha notices in text, not only icons.
• Use plain language and short paragraphs.
• Ensure zoom and reflow do not obscure the product name or ™ mark.
• Do not repeat ™ in every sentence; first prominent use and footer notice are sufficient.
• SVG logo accessible labels should not create repetitive trademark announcements in navigation.

Analytics and privacy constraint

The initial website must not use cookies, ad networks, behavioral analytics, session replay, external font tracking or third-party embeds that contact remote services without user action.

Privacy-respecting aggregate measurement may be considered only after #86 defines and approves the website data flow.

Acceptance criteria

• The canonical product URL is https://aiteracja.pl/sightadapt/ everywhere.
• sightadapt.aiteracja.pl is treated only as an optional redirect.
• The three canonical SVG assets are used according to this specification.
• Every lockup and prominent first use includes SightAdapt™.
• No page uses ®.
• The footer contains the unregistered product-mark notice.
• Home, Features, Download, Documentation, How it works, FAQ, Releases, Privacy, Legal, Security and Support pages are implemented.
• Visible copy covers every required section described above.
• Download and release information is sourced from canonical GitHub Releases.
• Claims match the implemented application and documented alpha limitations.
• No medical, universal-compatibility or endorsement claims are introduced.
• Privacy, legal and security content is synchronized with repository source documents.
• All screenshots and diagrams have documented provenance and useful alt text.
• Titles, descriptions, canonical links, Open Graph and structured data validate.
• Internal links, release links and legal-document links pass automated checks.
• The content remains usable without JavaScript except for nonessential enhancement.
• Keyboard, zoom, contrast and screen-reader checks are included in manual acceptance.
• The completed site is reviewed against [Project] Establish SightAdapt public presence and discoverability #95, [Brand] Standardize SightAdapt™ naming and public attribution #96, [Website] Build the SightAdapt GitHub Pages site #99, [SEO] Add canonical metadata, Open Graph and SoftwareApplication structured data #101, [SEO] Publish sitemap.xml, robots.txt and canonical URL behavior #102, [Website/Compliance] Publish privacy, license, security and contact pages #103 and [Downloads] Add verified release downloads, checksums and release history to the website #104 before publication.