Add GitHub Pages landing site

[josephsenior]

What changed

• Adds a focused, static canonical landing page under site/.
• Adds GitHub Pages deployment through the official Pages Actions workflow.

Why

The repository has strong technical proof and a polished README; this gives it a stable, shareable URL for search and social distribution.

Validation

• Parsed site/index.html with Python's HTML parser.
• Ran git diff --check.

Summary by Sourcery

Add a static marketing landing page and configure automated deployment to GitHub Pages.

New Features:

• Introduce a static, single-page HTML landing site under site/ for the Grinta project.
• Add social sharing metadata and calls to action linking to installation, demo, and documentation resources.

Deployment:

• Configure a GitHub Actions workflow to build and deploy the site directory to GitHub Pages on main branch updates.
• Add .nojekyll configuration to ensure the static site is served without Jekyll processing.

[sourcery-ai]

Reviewer's Guide

Adds a static marketing landing page under site/ and configures an official GitHub Pages Actions workflow to deploy it from the main branch.

File-Level Changes

Change	Details	Files
Introduce a static GitHub Pages landing site for Grinta.	Create a standalone, styled HTML landing page describing Grinta’s value proposition, capabilities, and usage entry points. Include Open Graph and Twitter metadata for rich link previews and SEO. Link primary calls-to-action to installation instructions, demo video, quick start, and case studies in the repository.	site/index.html
Configure automated deployment of the site directory to GitHub Pages via GitHub Actions.	Add a workflow that triggers on main branch pushes affecting the site or the workflow file, plus manual workflow_dispatch. Grant minimum required permissions and set up a dedicated github-pages environment with URL taken from deployment output. Upload the site/ directory as a Pages artifact and deploy it using the official configure-pages, upload-pages-artifact, and deploy-pages actions. Prevent Jekyll processing of the static site via a .nojekyll marker file.	.github/workflows/deploy-pages.yml site/.nojekyll

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• The landing page hard-codes multiple full GitHub URLs (including og:url and all CTAs) to josephsenior/Grinta-Coding-Agent, which will be misleading for forks or repo moves; consider using relative URLs or a single configurable base URL to avoid future breakage.
• The demo link in the hero section points to a specific versioned asset (releases/download/v1.0.0/grinta_raft.mp4); you may want to point to the latest release or a stable asset path to avoid the page drifting out of date as new releases are published.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The landing page hard-codes multiple full GitHub URLs (including `og:url` and all CTAs) to `josephsenior/Grinta-Coding-Agent`, which will be misleading for forks or repo moves; consider using relative URLs or a single configurable base URL to avoid future breakage.
- The demo link in the hero section points to a specific versioned asset (`releases/download/v1.0.0/grinta_raft.mp4`); you may want to point to the latest release or a stable asset path to avoid the page drifting out of date as new releases are published.

## Individual Comments

### Comment 1
<location path="site/index.html" line_range="31" />
<code_context>
+      .actions { display: flex; flex-wrap: wrap; gap: 12px; margin-top: 30px; }
+      .button { background: var(--accent); border: 1px solid var(--accent); border-radius: 8px; color: white; font-weight: 750; padding: 11px 16px; text-decoration: none; }
+      .button.secondary { background: transparent; border-color: var(--line); color: var(--text); }
+      .evidence { border: 1px solid var(--line); border-radius: 12px; background: color-mix(in srgb, var(--surface) 87%, transparent); margin: 0 0 72px; padding: 26px; }
+      .evidence strong { color: var(--accent-soft); }
+      .stats { display: grid; grid-template-columns: repeat(3, 1fr); gap: 18px; }
</code_context>
<issue_to_address>
**suggestion:** Consider a fallback for browsers that don't support `color-mix()`.

Older browsers that don’t support `color-mix()` will ignore this rule. Add a plain `background: var(--surface);` before the `color-mix()` declaration so they get a reasonable background while newer browsers use the enhanced style.

```suggestion
      .evidence { border: 1px solid var(--line); border-radius: 12px; background: var(--surface); background: color-mix(in srgb, var(--surface) 87%, transparent); margin: 0 0 72px; padding: 26px; }
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion: Consider a fallback for browsers that don't support color-mix().

Older browsers that don’t support color-mix() will ignore this rule. Add a plain background: var(--surface); before the color-mix() declaration so they get a reasonable background while newer browsers use the enhanced style.

Suggested change

	.evidence { border: 1px solid var(--line); border-radius: 12px; background: color-mix(in srgb, var(--surface) 87%, transparent); margin: 0 0 72px; padding: 26px; }
	.evidence { border: 1px solid var(--line); border-radius: 12px; background: var(--surface); background: color-mix(in srgb, var(--surface) 87%, transparent); margin: 0 0 72px; padding: 26px; }