feat: landing page#5
Merged
lucky-ivanius merged 6 commits intomainfrom Apr 26, 2026
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 46 minutes and 18 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (20)
📝 WalkthroughWalkthroughIntroduces a new SvelteKit-based marketing website in Changes
Sequence Diagram(s)sequenceDiagram
participant Dev as Developer
participant GitHub as GitHub
participant Actions as GitHub Actions
participant CF as Cloudflare Pages
Dev->>GitHub: Push tag www@x.y.z
GitHub->>Actions: Trigger deploy-www workflow
Actions->>Actions: validate job: install deps (Bun)
Actions->>Actions: Verify version matches tag
Actions->>Actions: Run check & lint
alt validation passes
Actions->>Actions: deploy job: install & build
Actions->>CF: Deploy build output via Wrangler
CF-->>Actions: Deployment success
else validation fails
Actions-->>Dev: Workflow fails
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (8)
packages/www/static/robots.txt (1)
1-3: Optional: Reference a sitemap for SEO.For a marketing/landing site, consider adding a
Sitemap:directive once asitemap.xmlis generated. Helps crawlers discover routes and improves indexing.♻️ Example
# allow crawling everything by default User-agent: * Disallow: + +Sitemap: https://<your-domain>/sitemap.xml🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/www/static/robots.txt` around lines 1 - 3, Add an optional Sitemap directive to the existing robots.txt so crawlers can discover routes (e.g., add a "Sitemap: https://yourdomain.com/sitemap.xml" line after the Disallow entry once sitemap.xml is generated); update the robots.txt file (the User-agent / Disallow block in packages/www/static/robots.txt) to include this Sitemap URL and ensure it uses the full absolute URL to your sitemap.packages/www/svelte.config.js (1)
7-8: Defensive: handle missingfilename.If the compiler ever invokes this without a
filename(e.g., synthetic or virtual modules),filename.split(...)will throw onundefined. A small guard makes this robust.♻️ Proposed guard
- runes: ({ filename }) => - filename.split(/[/\\]/).includes("node_modules") ? undefined : true, + runes: ({ filename }) => + filename && filename.split(/[/\\]/).includes("node_modules") + ? undefined + : true,🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/www/svelte.config.js` around lines 7 - 8, The runes option callback (runes: ({ filename }) => filename.split(...)) can throw if filename is undefined; update the runes function (the arrow callback that destructures filename) to defensively check that filename is a string before calling split (e.g., return undefined or true when filename is falsy/non-string), so synthetic/virtual modules won't cause an exception.packages/www/src/routes/+layout.svelte (1)
1-7: Optional: typechildrenasSnippetfor stronger inference.Functionally correct, but typing the destructured prop helps editor tooling and catches misuse.
♻️ Proposed refactor
<script lang="ts"> import "./layout.css"; + import type { Snippet } from "svelte"; - let { children } = $props(); + let { children }: { children: Snippet } = $props(); </script>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/www/src/routes/`+layout.svelte around lines 1 - 7, The prop destructuring in +layout.svelte currently leaves children untyped; update the declaration of the destructured prop (the let { children } = $props() or equivalent prop declaration) to explicitly type children as Snippet (e.g., annotate the destructured binding or export let children: Snippet) so editor tooling gets stronger inference and misuse is caught; locate the children symbol in +layout.svelte and add the Snippet type annotation to that declaration..github/workflows/deploy-www.yml (2)
42-66: Optional: avoid duplicating install + build between jobs.
deployrepeats checkout, Bun install, andbun run buildeven thoughvalidatealready did install/check/lint on the same commit. For tag-triggered prod deploys it's a small cost, but you can shave time and reduce drift between "what was validated" and "what gets shipped" by uploadingpackages/www/buildfrom a single build step and downloading it before the wrangler step.# in validate (or a single combined job): after build - uses: actions/upload-artifact@v4 with: name: www-build path: packages/www/build retention-days: 1 # in deploy: replace install + build with - uses: actions/download-artifact@v4 with: name: www-build path: packages/www/build🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/deploy-www.yml around lines 42 - 66, The deploy job duplicates checkout/install/build; modify the workflow so the validate job uploads the produced site artifact (packages/www/build) using actions/upload-artifact@v4 (name: www-build) after bun run build, and update the deploy job (job: deploy) to remove the checkout + bun install + bun run build steps and instead download that artifact with actions/download-artifact@v4 (name: www-build, path: packages/www/build) before the cloudflare/wrangler-action@v3 step to ensure the same build is deployed.
19-21: Pinbun-versionfor reproducible CI.
bun-version: latestmeans a Bun release between PR-validate and tag-deploy could change behavior (lockfile semantics, install resolution, etc.). Pin to a specific major or exact version, ideally matching what developers run locally.♻️ Suggested change
- uses: oven-sh/setup-bun@v2 with: - bun-version: latest + bun-version: 1.2.x # or an exact version, e.g. 1.2.21Also applies to: 50-52
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/deploy-www.yml around lines 19 - 21, The workflow currently pins the action oven-sh/setup-bun@v2 but sets bun-version: latest which is non-reproducible; update the bun-version key to a specific version (either a pinned exact version like "1.8.6" or a major-locked value like "1.x") in the setup step that uses oven-sh/setup-bun@v2 (and repeat the same change for the other occurrence around lines 50-52) so CI uses a stable Bun release matching developers' local environment.packages/www/src/routes/+page.svelte (2)
127-127: Promote the brand accent color to a theme token.
#c596fais hardcoded twice (Lines 127 and 182).layout.cssalready defines theme tokens for surface/line/muted/fg/heading via@theme inline; add the accent there so it's themable, easier to grep, and benefits from Tailwind v4's slash-opacity syntax (e.g.,text-accent/70).:root { --accent: oklch(78% 0.13 305); /* approx of `#c596fa` */ } `@theme` inline { --color-accent: var(--accent); }Then
text-[#c596fa]→text-accent.Also applies to: 182-182
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/www/src/routes/`+page.svelte at line 127, Replace the two hardcoded color usages `text-[`#c596fa`]` in +page.svelte with the theme token (e.g., `text-accent`) and add the accent token to your theme in layout.css: define a root `--accent` color (approx oklch for `#c596fa`) and expose it inside `@theme inline` as `--color-accent` so Tailwind can map `text-accent` (and use slash-opacity like `text-accent/70`); update the two `text-[`#c596fa`]` occurrences to use `text-accent` so the color is themable and centralized.
76-76: Extract the repeated entry-animation utility chain.The same long Tailwind utility chain (
opacity-0 translate-y-2 transition-[opacity,translate] duration-420 ease-[cubic-bezier(0.23,1,0.32,1)] will-change-[opacity,translate] [&.is-in]:opacity-100 [&.is-in]:translate-y-0 motion-reduce:translate-none) is repeated on ~12 elements with only thedelay-*varying. This is a DRY hit and any future tweak (e.g., changing the easing) requires touching every site.In Tailwind v4 you can collapse this into a single utility via the
@utilitydirective inlayout.css:`@utility` enter { `@apply` opacity-0 translate-y-2 transition-[opacity,translate] duration-420 ease-[cubic-bezier(0.23,1,0.32,1)] will-change-[opacity,translate] motion-reduce:translate-none; } `@utility` enter-in { `@apply` opacity-100 translate-y-0; }Then in the markup:
class="enter [&.is-in]:enter-in delay-120".Also applies to: 113-113, 134-134, 156-156, 167-167, 174-174, 190-190, 200-200, 250-250, 268-268, 303-303, 338-338
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/www/src/routes/`+page.svelte at line 76, Extract the repeated Tailwind utility chain into two custom utilities named enter and enter-in in your global CSS (use `@utility` enter { `@apply` opacity-0 translate-y-2 transition-[opacity,translate] duration-420 ease-[cubic-bezier(0.23,1,0.32,1)] will-change-[opacity,translate] motion-reduce:translate-none; } and `@utility` enter-in { `@apply` opacity-100 translate-y-0; }) and then replace the long class strings in the markup (the class attribute containing opacity-0 translate-y-2 transition-[opacity,translate] … [&.is-in]:opacity-100 [&.is-in]:translate-y-0) with the shorter form class="enter [&.is-in]:enter-in delay-XXX" preserving the existing delay-* token for each element so only the delay values remain per element.packages/www/src/app.html (1)
1-19: LGTM — standard SvelteKitapp.html.Two optional notes:
<meta name="text-scale" content="scale">on Line 7 isn't a standard meta tag I'm aware of and likely has no effect; consider removing it.- Google Fonts loaded from
fonts.googleapis.comships the visitor's IP to Google. If GDPR/CCPA matters for this site, consider self-hosting via@fontsource/interand@fontsource/jetbrains-mono— also removes a render-blocking third-party request and the preconnects.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/www/src/app.html` around lines 1 - 19, Remove the nonstandard <meta name="text-scale" content="scale"> tag from the HTML head (it appears in app.html) and, if you need to avoid third-party font requests for privacy or performance, replace the external Google Fonts usage (the two <link rel="preconnect"> tags and the <link href="https://fonts.googleapis.com..."> stylesheet tag) with self-hosted fonts via `@fontsource` (e.g., `@fontsource/inter` and `@fontsource/jetbrains-mono`) and update your app entry (e.g., global stylesheet or root layout) to import those packages instead, then remove the preconnect and external stylesheet tags from app.html.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/deploy-www.yml:
- Around line 22-26: The cache key in the GitHub Actions steps using
actions/cache@v5 currently hashes 'bun.lockb' which doesn't exist; update the
hashFiles call used in the key (and the matching step at the other block) to
reference the actual lockfile 'bun.lock' so the key becomes ${{ runner.os
}}-bun-${{ hashFiles('**/bun.lock') }} and will change when dependencies change;
locate the actions/cache step (the 'uses: actions/cache@v5' block and its 'key'
property) and replace 'bun.lockb' with 'bun.lock' in both occurrences.
In `@packages/www/package.json`:
- Around line 28-30: The package.json currently lists an incompatible Svelte 3/4
package "lucide-svelte" in the "dependencies" block which conflicts with Svelte
^5.55.2; either remove "lucide-svelte" if it's unused or replace it with the
Svelte‑5 compatible package "@lucide/svelte" and update any imports to reference
`@lucide/svelte` (search for "lucide-svelte" in imports) so the project uses the
correct runtime for Svelte 5.
In `@packages/www/src/routes/`+page.svelte:
- Around line 7-31: The parallax update ignores users' prefers-reduced-motion
and doesn't re-evaluate on resize: modify the onMount logic (functions update,
onScroll, vars bg and ticking) to first check
window.matchMedia('(prefers-reduced-motion: reduce)') and skip any background
translation (set backgroundPosition to a non-moving fallback) when
reduced-motion matches; replace the hardcoded 768 check with
matchMedia('(min-width: 768px)') (or a named constant) when deciding between
mobile/desktop behavior; and add a window 'resize' listener that calls update
(and updates the matchMedia state if cached) so the layout toggles immediately
when crossing the breakpoint; ensure you remove both 'scroll' and 'resize'
listeners on destroy.
---
Nitpick comments:
In @.github/workflows/deploy-www.yml:
- Around line 42-66: The deploy job duplicates checkout/install/build; modify
the workflow so the validate job uploads the produced site artifact
(packages/www/build) using actions/upload-artifact@v4 (name: www-build) after
bun run build, and update the deploy job (job: deploy) to remove the checkout +
bun install + bun run build steps and instead download that artifact with
actions/download-artifact@v4 (name: www-build, path: packages/www/build) before
the cloudflare/wrangler-action@v3 step to ensure the same build is deployed.
- Around line 19-21: The workflow currently pins the action oven-sh/setup-bun@v2
but sets bun-version: latest which is non-reproducible; update the bun-version
key to a specific version (either a pinned exact version like "1.8.6" or a
major-locked value like "1.x") in the setup step that uses oven-sh/setup-bun@v2
(and repeat the same change for the other occurrence around lines 50-52) so CI
uses a stable Bun release matching developers' local environment.
In `@packages/www/src/app.html`:
- Around line 1-19: Remove the nonstandard <meta name="text-scale"
content="scale"> tag from the HTML head (it appears in app.html) and, if you
need to avoid third-party font requests for privacy or performance, replace the
external Google Fonts usage (the two <link rel="preconnect"> tags and the <link
href="https://fonts.googleapis.com..."> stylesheet tag) with self-hosted fonts
via `@fontsource` (e.g., `@fontsource/inter` and `@fontsource/jetbrains-mono`) and
update your app entry (e.g., global stylesheet or root layout) to import those
packages instead, then remove the preconnect and external stylesheet tags from
app.html.
In `@packages/www/src/routes/`+layout.svelte:
- Around line 1-7: The prop destructuring in +layout.svelte currently leaves
children untyped; update the declaration of the destructured prop (the let {
children } = $props() or equivalent prop declaration) to explicitly type
children as Snippet (e.g., annotate the destructured binding or export let
children: Snippet) so editor tooling gets stronger inference and misuse is
caught; locate the children symbol in +layout.svelte and add the Snippet type
annotation to that declaration.
In `@packages/www/src/routes/`+page.svelte:
- Line 127: Replace the two hardcoded color usages `text-[`#c596fa`]` in
+page.svelte with the theme token (e.g., `text-accent`) and add the accent token
to your theme in layout.css: define a root `--accent` color (approx oklch for
`#c596fa`) and expose it inside `@theme inline` as `--color-accent` so Tailwind
can map `text-accent` (and use slash-opacity like `text-accent/70`); update the
two `text-[`#c596fa`]` occurrences to use `text-accent` so the color is themable
and centralized.
- Line 76: Extract the repeated Tailwind utility chain into two custom utilities
named enter and enter-in in your global CSS (use `@utility` enter { `@apply`
opacity-0 translate-y-2 transition-[opacity,translate] duration-420
ease-[cubic-bezier(0.23,1,0.32,1)] will-change-[opacity,translate]
motion-reduce:translate-none; } and `@utility` enter-in { `@apply` opacity-100
translate-y-0; }) and then replace the long class strings in the markup (the
class attribute containing opacity-0 translate-y-2
transition-[opacity,translate] … [&.is-in]:opacity-100 [&.is-in]:translate-y-0)
with the shorter form class="enter [&.is-in]:enter-in delay-XXX" preserving the
existing delay-* token for each element so only the delay values remain per
element.
In `@packages/www/static/robots.txt`:
- Around line 1-3: Add an optional Sitemap directive to the existing robots.txt
so crawlers can discover routes (e.g., add a "Sitemap:
https://yourdomain.com/sitemap.xml" line after the Disallow entry once
sitemap.xml is generated); update the robots.txt file (the User-agent / Disallow
block in packages/www/static/robots.txt) to include this Sitemap URL and ensure
it uses the full absolute URL to your sitemap.
In `@packages/www/svelte.config.js`:
- Around line 7-8: The runes option callback (runes: ({ filename }) =>
filename.split(...)) can throw if filename is undefined; update the runes
function (the arrow callback that destructures filename) to defensively check
that filename is a string before calling split (e.g., return undefined or true
when filename is falsy/non-string), so synthetic/virtual modules won't cause an
exception.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 0f8f1d4d-30f2-46d7-9cc2-7a9165a03360
⛔ Files ignored due to path filters (3)
bun.lockis excluded by!**/*.lockpackages/www/src/lib/assets/logo.pngis excluded by!**/*.pngpackages/www/static/favicon.icois excluded by!**/*.ico
📒 Files selected for processing (22)
.github/workflows/deploy-www.ymldocs/docs.jsondocs/introduction.mdxpackages/www/.gitignorepackages/www/.npmrcpackages/www/.vscode/extensions.jsonpackages/www/.vscode/settings.jsonpackages/www/README.mdpackages/www/biome.jsonpackages/www/package.jsonpackages/www/src/app.d.tspackages/www/src/app.htmlpackages/www/src/lib/assets/background.webppackages/www/src/lib/index.tspackages/www/src/routes/+layout.sveltepackages/www/src/routes/+layout.tspackages/www/src/routes/+page.sveltepackages/www/src/routes/layout.csspackages/www/static/robots.txtpackages/www/svelte.config.jspackages/www/tsconfig.jsonpackages/www/vite.config.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
New Features
Documentation
Chores