mizcausevic-dev/kinetic-gain-suite-landing

Purpose and principal workflow

This repository is the static public front door for the Kinetic Gain Protocol Suite, linking visitors to its governance-spec descriptions and sibling repositories. A visitor’s browser requests the published pages from the hosting site; maintainers can also run the Node generator to update the vertical hub and eligible vertical pages. Separately, a push to main triggers the documented GitHub Actions deployment workflow, which FTP-syncs the site to Hostinger.

Components

Public pages

• Suite landing page — index.html: the primary suite entry page; the README identifies it as the landing page.

• Vertical directory — verticals/index.html: presents the vertical categories and the suite’s six canonical artifact shapes; the generator renders this page from vertical data.

• Vertical detail pages — verticals/healthtech/index.html: representative hand-authored detail page; the tree contains detail pages for the other verticals as well. Three vertical pages are explicitly marked in the generator as hand-maintained.

• MCP page — mcp/index.html: a separate static page in the public site; its behavior and relationship to the suite are not established by the sampled source.

• Site styling — style.css: shared styles for the main site. verticals/vertical.css supplies styles for vertical pages, including the dark theme and cards shown in the generator excerpt.

Vertical-page authoring

• Vertical content data — verticals/_verticals-data.json: data consumed by the generator for vertical pages and directory cards.

• Vertical page generator — verticals/_generate.mjs: when run manually with Node, renders the directory, shared vertical CSS, and data-driven detail pages; it skips the three hand-maintained pages. It links repo cards to GitHub and escapes dynamic text for HTML output.

Publishing

• Deployment workflow — .github/workflows/deploy.yml: the README documents a push-to-main workflow that FTP-syncs the site root to /suite/ on Hostinger.

External participants

• Site visitor — null repository path: requests and reads the published static pages.

• GitHub Actions push trigger — null repository path: an external platform event that starts the documented deployment workflow.

• Hostinger site hosting — null repository path: the documented destination for the FTP deployment.

• Sibling spec repositories — null repository path: external GitHub repositories linked from vertical content.

Relationships

• Site visitor -> Suite landing page: requests the published entry page in a browser.

• Site visitor -> Vertical directory: requests the directory page to browse the vertical offerings.

• Site visitor -> Vertical detail pages: follows directory links to vertical-specific information.

• Site visitor -> MCP page: can request this separate page; its purpose is not established by the sampled inputs.

• Vertical content data -> Vertical page generator: supplies the vertical records used to render pages and directory cards; evidenced by the JSON read and data.verticals mapping.

• Vertical page generator -> Vertical directory: writes the rendered directory HTML.

• Vertical page generator -> Vertical detail pages: writes pages for eligible verticals and skips the hand-maintained entries.

• Vertical page generator -> Site styling: writes the vertical stylesheet.

• Vertical detail pages -> Sibling spec repositories: generated repo cards link to GitHub repositories named by the vertical data.

• GitHub Actions push trigger -> Deployment workflow: a push to main starts the documented workflow.

• Deployment workflow -> Hostinger site hosting: FTP-syncs the site root to /suite/.

Coverage limits

The deployment workflow source, page contents beyond the excerpts, vertical data, and most CSS were not sampled. Deployment details and the no-build-step claim come from the README; runtime behavior of the MCP page and the exact links and content in the hand-maintained pages could not be verified.