chore: landing page

[aritra1999]

Pivoting from a sveltekit application to a smile html approach.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR removes the entire SvelteKit-based site implementation and replaces it with a static HTML landing page. All SvelteKit configurations, components, routes, and utilities are deleted. The deployment workflow is simplified by removing build steps. A deployment guide and version file are added.

Changes

Cohort / File(s)	Summary
Deployment & Release .github/workflows/deploy.yml, DEPLOYMENT.md, VERSION	Simplified deploy workflow by removing build steps (Setup Bun, Install, Prepare SvelteKit, Build); changed artifact upload path from site/build/ to site/. Added comprehensive deployment guide documenting CI/CD pipeline, release methods, troubleshooting, and best practices. Added version file with v0.3.0.
Static Landing Page site/index.html	New 1022-line static HTML landing page replacing SvelteKit site, featuring responsive layout with navbar, hero section, features grid, tabbed documentation, contribute section, and footer. Includes inline JavaScript for tab switching, clipboard functionality, and GitHub star count fetching.
SvelteKit Configuration & Dependencies site/svelte.config.js, site/tsconfig.json, site/components.json, site/package.json	Deleted SvelteKit configuration, TypeScript setup, ShadCN-Svelte config, and npm package manifest.
SvelteKit App Structure site/src/app.d.ts, site/src/app.html, site/.gitignore, site/README.md, site/src/lib/index.ts, site/src/lib/utils.ts	Removed SvelteKit app shell, TypeScript declarations, project documentation, and utility functions/types (cn helper, WithElementRef, etc.). Cleaned up .gitignore patterns for build artifacts and dependencies.
Svelte Components site/src/lib/components/...svelte, site/src/lib/components/ui/...svelte	Deleted all Svelte components: layout components (Navbar, Hero, Features, Documentation, Contribute, Footer), UI component library (Button, Card, Tabs with all subcomponents), and their barrel exports (index.ts files).
Route Structure site/src/routes/+page.svelte, site/src/routes/+layout.svelte, site/src/routes/+layout.js, site/src/routes/layout.css	Removed all SvelteKit routes, layout configuration, and global styles including theme tokens and CSS custom properties.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• chore: fix github pages deployment action #23: Modifies the same .github/workflows/deploy.yml file with conflicting Bun-related setup steps (adds vs. removes build tooling configuration).
• chore: landing and docs #18: Directly affects the same site files and deploy workflow; this PR removes the landing site that PR #18 previously modified.
• chore: fix github pages deployment issue  #21: Conflicts with deploy workflow changes around the "Prepare SvelteKit" step and site/package.json modifications.

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Merge Conflict Detection	⚠️ Warning	❌ Merge conflicts detected (2 files): ⚔️ .github/workflows/deploy.yml (content) ⚔️ site/.gitignore (content) These conflicts must be resolved before merging into main.	Resolve conflicts locally and push changes to this branch.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: landing page' accurately summarizes the main change: replacing the SvelteKit application with a static HTML landing page and updating deployment infrastructure.
Description check	✅ Passed	The description 'Pivoting from a sveltekit application to a smile html approach' is related to the changeset, describing the high-level architectural shift from a SvelteKit framework to static HTML.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/landing-and-docs

⚔️ Resolve merge conflicts (beta)

• Auto-commit resolved conflicts to branch chore/landing-and-docs
• Create stacked PR with resolved conflicts
• Post resolved changes as copyable diffs in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 5

🤖 Fix all issues with AI agents

In `@DEPLOYMENT.md`:
- Around line 150-153: Under "### Documentation Not Deployed" update the
troubleshooting bullet that currently reads "Verify SvelteKit build succeeds
locally" to reflect the new static HTML site: replace that line with a note like
"Verify static site files exist in /site and can be served locally (e.g., open
/site/index.html or run a simple static server)". Ensure the heading
"Documentation Not Deployed" and the other bullets remain unchanged.
- Around line 40-42: The multi-line git commit example in DEPLOYMENT.md opens a
double-quote on the first line of the commit message but isn't visually paired,
so update the example to make the quoting explicit and unambiguous—either close
the quote on the final line, switch to single quotes around the commit message,
or present the message in a fenced code block; ensure the example around the git
commit (the lines showing git commit -m "feat: change default timeout to 30s ...
BREAKING CHANGE: ...") displays matching quotes or uses an alternative format so
readers clearly see the full commit string.

In `@site/index.html`:
- Around line 966-977: The click handler can call document.getElementById(tabId)
when tabId is undefined or doesn't match any element, causing a null
dereference; update the handler in the tabButtons.forEach callback to validate
btn.dataset.tab (tabId) is truthy and to retrieve the element into a variable
(e.g., const tabEl = document.getElementById(tabId)), then only call
tabEl.classList.add("active") if tabEl is not null (otherwise skip or log a
warning). Ensure you still remove previous active classes on tabButtons and
tabContents as before, but guard the add of the "active" class on the target
element.
- Around line 1001-1017: The fetchStars function should check response.ok before
calling response.json(); modify fetchStars to verify the HTTP status (use
response.ok) and handle non-2xx cases by logging the error (including
response.status and optionally response.statusText or parsed error body) and
returning early so you don't attempt to read data.stargazers_count for error
responses; keep updating DOM only when response.ok is true and
data.stargazers_count is defined, and ensure errors still fall through to the
existing catch block for network exceptions.
- Around line 717-728: The paragraph contains leftover template-escaping text in
the code element (the sequence shown as {{"{{"}}{{"}}"}}) which will render
literally; locate the <p> block containing the inline <code> element that
currently shows the escaped template and replace that escaped sequence with a
plain mustache pair `{{ }}` so the content displays as intended (look for the
code element with classes "font-mono text-[0.875em] bg-white text-[`#333`] py-0.5
px-1.5 rounded-sm border border-[`#e5e5e5`]" within the paragraph that begins
"Define variables with @ and use with").

🧹 Nitpick comments (2)

site/index.html (2)

89-147: .hero-btn and .btn are nearly identical — consider consolidating.

These two CSS blocks share the same font, weight, text-transform, letter-spacing, border, box-shadow, transition, display, alignment, gap, padding, font-size, cursor, and text-decoration. Only the class names differ. A single base class would eliminate this duplication.

---

74-74: Pin the Lucide version instead of using @latest.

Using @latest on unpkg means any new release (including breaking changes) can silently break your site. Pin to a specific version for reproducibility and to mitigate supply-chain risk.

Proposed fix

-<script src="https://unpkg.com/lucide@latest/dist/umd/lucide.js"></script>
+<script src="https://unpkg.com/lucide@0.563.0/dist/umd/lucide.js"></script>

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Unclosed quote in the multi-line commit example.

The commit message on line 40 opens with a double-quote but is never closed, which could confuse contributors copying this example.

Proposed fix

-git commit -m "feat: change default timeout to 30s
-
-BREAKING CHANGE: Default request timeout changed from 10s to 30s"
+git commit -m 'feat: change default timeout to 30s
+
+BREAKING CHANGE: Default request timeout changed from 10s to 30s'

Note: Alternatively, use single quotes or escape the inner content. The key issue is the opening " on line 40 isn't visually paired for readers — it looks like a missing closing quote even though the " at end of line 42 closes it. Consider clarifying the formatting.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	git commit -m "feat: change default timeout to 30s
	BREAKING CHANGE: Default request timeout changed from 10s to 30s"
	git commit -m 'feat: change default timeout to 30s
	BREAKING CHANGE: Default request timeout changed from 10s to 30s'

🤖 Prompt for AI Agents

In `@DEPLOYMENT.md` around lines 40 - 42, The multi-line git commit example in
DEPLOYMENT.md opens a double-quote on the first line of the commit message but
isn't visually paired, so update the example to make the quoting explicit and
unambiguous—either close the quote on the final line, switch to single quotes
around the commit message, or present the message in a fenced code block; ensure
the example around the git commit (the lines showing git commit -m "feat: change
default timeout to 30s ... BREAKING CHANGE: ...") displays matching quotes or
uses an alternative format so readers clearly see the full commit string.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Stale SvelteKit reference — SvelteKit was removed in this PR.

Line 152 says "Verify SvelteKit build succeeds locally", but this PR replaces SvelteKit with a static HTML page. Update this troubleshooting item accordingly.

Proposed fix

 ### Documentation Not Deployed
 - Check if changes exist in `/site` directory
-- Verify SvelteKit build succeeds locally
+- Verify the static site files are correct
 - Review deploy.yml workflow logs

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### Documentation Not Deployed
	- Check if changes exist in `/site` directory
	- Verify SvelteKit build succeeds locally
	- Review deploy.yml workflow logs
	### Documentation Not Deployed
	- Check if changes exist in `/site` directory
	- Verify the static site files are correct
	- Review deploy.yml workflow logs

🤖 Prompt for AI Agents

In `@DEPLOYMENT.md` around lines 150 - 153, Under "### Documentation Not Deployed"
update the troubleshooting bullet that currently reads "Verify SvelteKit build
succeeds locally" to reflect the new static HTML site: replace that line with a
note like "Verify static site files exist in /site and can be served locally
(e.g., open /site/index.html or run a simple static server)". Ensure the heading
"Documentation Not Deployed" and the other bullets remain unchanged.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Leftover template escaping — will render incorrectly in static HTML.

{{"{{"}}{{"}}"}} is Svelte/template-engine escaping syntax. In a plain HTML file, this renders literally as garbage text. It should just be {{ }}.

Proposed fix

-							>@</code
-						>
-						and use with
-						<code
-							class="font-mono text-[0.875em] bg-white text-[`#333`] py-0.5 px-1.5 rounded-sm border border-[`#e5e5e5`]"
-							>{{"{{"}}{{"}}"}}</code
+							>@</code
+						>
+						and use with
+						<code
+							class="font-mono text-[0.875em] bg-white text-[`#333`] py-0.5 px-1.5 rounded-sm border border-[`#e5e5e5`]"
+							>{{ }}</code

🤖 Prompt for AI Agents

In `@site/index.html` around lines 717 - 728, The paragraph contains leftover
template-escaping text in the code element (the sequence shown as
{{"{{"}}{{"}}"}}) which will render literally; locate the <p> block containing
the inline <code> element that currently shows the escaped template and replace
that escaped sequence with a plain mustache pair `{{ }}` so the content displays
as intended (look for the code element with classes "font-mono text-[0.875em]
bg-white text-[`#333`] py-0.5 px-1.5 rounded-sm border border-[`#e5e5e5`]" within
the paragraph that begins "Define variables with @ and use with").

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Potential null dereference if tabId doesn't match an element ID.

document.getElementById(tabId) could return null if a data-tab attribute doesn't match any element ID, which would throw a runtime error.

Proposed fix

  btn.classList.add("active");
- document.getElementById(tabId).classList.add("active");
+ document.getElementById(tabId)?.classList.add("active");

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	tabButtons.forEach((btn) => {
	btn.addEventListener("click", () => {
	const tabId = btn.dataset.tab;
	// Update active states
	tabButtons.forEach((b) => b.classList.remove("active"));
	tabContents.forEach((c) => c.classList.remove("active"));
	btn.classList.add("active");
	document.getElementById(tabId).classList.add("active");
	});
	});
	tabButtons.forEach((btn) => {
	btn.addEventListener("click", () => {
	const tabId = btn.dataset.tab;
	// Update active states
	tabButtons.forEach((b) => b.classList.remove("active"));
	tabContents.forEach((c) => c.classList.remove("active"));
	btn.classList.add("active");
	document.getElementById(tabId)?.classList.add("active");
	});
	});

🤖 Prompt for AI Agents

In `@site/index.html` around lines 966 - 977, The click handler can call
document.getElementById(tabId) when tabId is undefined or doesn't match any
element, causing a null dereference; update the handler in the
tabButtons.forEach callback to validate btn.dataset.tab (tabId) is truthy and to
retrieve the element into a variable (e.g., const tabEl =
document.getElementById(tabId)), then only call tabEl.classList.add("active") if
tabEl is not null (otherwise skip or log a warning). Ensure you still remove
previous active classes on tabButtons and tabContents as before, but guard the
add of the "active" class on the target element.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Missing response.ok check before parsing the GitHub API response.

If the API returns a non-2xx status (e.g., rate limiting with 403), response.json() will still succeed but data.stargazers_count may be undefined or the response may contain an error message. The current code silently swallows this. Consider checking response.ok.

Proposed fix

 async function fetchStars() {
     try {
         const response = await fetch(
             "https://api.github.com/repos/aritra1999/httpyum",
         );
+        if (!response.ok) return;
         const data = await response.json();

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	async function fetchStars() {
	try {
	const response = await fetch(
	"https://api.github.com/repos/aritra1999/httpyum",
	);
	const data = await response.json();
	if (data.stargazers_count !== undefined) {
	document.getElementById("star-count").textContent =
	data.stargazers_count.toLocaleString();
	document
	.getElementById("stars-container")
	.classList.remove("hidden");
	}
	} catch (error) {
	console.error("Failed to fetch stars:", error);
	}
	}
	async function fetchStars() {
	try {
	const response = await fetch(
	"https://api.github.com/repos/aritra1999/httpyum",
	);
	if (!response.ok) return;
	const data = await response.json();
	if (data.stargazers_count !== undefined) {
	document.getElementById("star-count").textContent =
	data.stargazers_count.toLocaleString();
	document
	.getElementById("stars-container")
	.classList.remove("hidden");
	}
	} catch (error) {
	console.error("Failed to fetch stars:", error);
	}
	}

🤖 Prompt for AI Agents

In `@site/index.html` around lines 1001 - 1017, The fetchStars function should
check response.ok before calling response.json(); modify fetchStars to verify
the HTTP status (use response.ok) and handle non-2xx cases by logging the error
(including response.status and optionally response.statusText or parsed error
body) and returning early so you don't attempt to read data.stargazers_count for
error responses; keep updating DOM only when response.ok is true and
data.stargazers_count is defined, and ensure errors still fall through to the
existing catch block for network exceptions.