feat: CalmKernel website redesign — Dark Amber theme (Stitch AI)

[ahm3t0t]

Summary

Complete website redesign generated via Google Stitch MCP and refined for production.

Before → After

• Old: Aiero IT Services template (Bootstrap, turquoise/red)
• New: Custom dark amber theme (Tailwind CSS v4, glassmorphism, modern agency aesthetic)

What Changed

Design

• Dark theme with amber/orange (#f59e0b) accent colors
• Sora headlines + Inter body (self-hosted WOFF2, KVKK/GDPR compliant)
• Glassmorphism product cards with hover effects
• Terminal mockup for BigFive Updater section
• Gradient CTA section
• Mobile-responsive with hamburger menu

Technical

• Tailwind CSS v4 with purged build (32KB vs ~300KB CDN)
• Font Awesome icons (replaced Google Material Symbols)
• Zero external font dependencies (no Google Fonts CDN)
• Proper anchor navigation (#products, #open-source, #about)
• Skip-to-content link for accessibility

Pages

• index.html — TR landing page (new design)
• en/index.html — EN landing page (new design)
• index-old-aiero.html — Old design preserved as backup
• stitch-reference.html — Original Stitch output for reference
• src/input.css — Tailwind source CSS

Sections

1. Hero — "Building the Future of Data Infrastructure"
2. Products — DataWash, DataWatch, DataSuite
3. Open Source — BigFive Updater with terminal mockup
4. About — Turkish Engineering, Security First, Open Source DNA, AI-Powered
5. CTA — meet@calmkernel.tr + social links
6. Footer — Privacy, Tools, GitHub, LinkedIn

Stitch MCP Project

• Project ID: 9648627339346328816
• Design System: CalmKernel Dark Amber (Sora + Inter, Vibrant, #FF6B2C)
• 7 screens generated (desktop + variants)

Rollback

Old design preserved as index-old-aiero.html. To rollback:

mv index.html index-stitch.html && mv index-old-aiero.html index.html
```"
<!-- devin-review-badge-begin -->

---

<a href="https://app.devin.ai/review/calmkerneltr/calmkerneltr.github.io/pull/5" target="_blank">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://static.devin.ai/assets/gh-open-in-devin-review-dark.svg?v=1">
    <img src="https://static.devin.ai/assets/gh-open-in-devin-review-light.svg?v=1" alt="Open with Devin">
  </picture>
</a>
<!-- devin-review-badge-end -->

[coderabbitai]

Warning

Rate limit exceeded

@ahm3t0t has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 30 seconds before requesting another review.

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 9 minutes and 30 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7df8229b-0b01-4cfa-99e4-3beb9ef89a11

📥 Commits

Reviewing files that changed from the base of the PR and between c3f52f0 and 0371867.

📒 Files selected for processing (3)

• assets/css/main.css
• en/index.html
• index.html

📝 Walkthrough

Walkthrough

The changes represent a comprehensive migration from Bootstrap to Tailwind CSS v4.2.2 framework, including new Tailwind stylesheet assets, restructured landing pages with simplified layouts, and updated color schemes. Multiple marketing and reference pages were added alongside the new styling infrastructure.

Changes

Cohort / File(s)	Summary
Tailwind CSS Framework Setup assets/css/main.css, src/input.css	New Tailwind CSS v4.2.2 stylesheet with precompiled utilities, theme tokens (fonts: Inter/Sora, colors: brand/charcoal), custom utility classes (glass-card, text-gradient), responsive breakpoints, and @font-face declarations for self-hosted fonts.
Landing Page Restructures index.html, en/index.html	Major restructuring from Bootstrap to Tailwind-based layouts. Replaced legacy multi-section marketing structures (preloader, modal overlays, swiper sliders, FAQ/blog sections) with simplified fixed navigation, hero sections, product/ecosystem cards, open-source highlights, and minimal footers. Updated SEO metadata, removed legacy script bundles, and added inline mobile menu toggle logic.
Marketing & Reference Pages stitch-reference.html, index-old-aiero.html	New static HTML pages: stitch-reference.html is a Tailwind-based dark-themed marketing layout with navigation, hero, product ecosystem, feature grids, and CTA sections; index-old-aiero.html is an archival Turkish landing page preserving legacy Bootstrap-based structure with swiper carousels, FAQ accordion, and multi-section content.
Cookie Consent Styling assets/css/cookie-consent.css	Color palette update: replaced teal accent colors with amber/orange across banner border, link text, button backgrounds, and hover states.
Git Configuration .gitignore	Added .gitmem/ directory to ignore list under Environment section.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 From Bootstrap chains to Tailwind's flight,
Our humble pages now shimmer bright,
With amber accents and Sora's grace,
A sleeker, simpler design takes place,
CalmKernel's heart beats fresh and true! 🌟

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: a complete website redesign transitioning from the old Aiero template to a new dark amber theme using Tailwind CSS, generated via Stitch AI.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, explaining the design system overhaul, technical stack changes, new pages, and accessibility improvements introduced by the redesign.
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 unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/stitch-redesign

---

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.}

[blocksorg]

[Severity 7] Missing cookie consent / KVKK banner

The previous design included assets/css/cookie-consent.css and an active cookie consent mechanism. The new design removes it entirely — no cookie banner is present on the page.

The "Security First" section on this very page states "Fully KVKK and GDPR compliant," but if the site uses any cookies (analytics, session tracking, etc.), the absence of a consent UI is a KVKK/GDPR compliance risk.

Before merging, please confirm:

1. Does the site set any cookies at all (including via server-side or third-party scripts)?
2. If yes, the cookie consent mechanism must be reinstated.
3. If no cookies are used, it would be good to document this explicitly (e.g., in the privacy policy) so this isn't flagged in future audits.

The old cookie consent CSS/JS was deliberately built in PR #2 — intentionally removing it here without a replacement or explicit decision to drop cookies should be called out.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9824dad5d6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Correct @font-face paths in generated CSS

The new @font-face rules point to src:url(../assets/fonts/...), but this stylesheet is served as /assets/css/main.css, so those relative URLs resolve to /assets/assets/fonts/... and return 404. That means Inter/Sora never load on the redesigned pages and browsers fall back to default fonts. Use paths resolved from /assets/css/ (for example ../fonts/... or absolute /assets/fonts/...).

Useful? React with 👍 / 👎.

[gemini-code-assist]

Code Review

This pull request overhauls the project's landing pages for both English and Turkish locales, transitioning to a modern, streamlined design powered by Tailwind CSS. The content is updated to reflect a new focus on enterprise data infrastructure platforms, including DataWash, DataWatch, and DataSuite. Key feedback focuses on correcting font paths in the source CSS to prevent loading issues, completing the localization of the Turkish page, and enhancing the mobile navigation menu with better accessibility attributes and UX refinements. It is also recommended to use root-relative paths for static assets to ensure reliability across different directory levels.

[gemini-code-assist]

The font paths in the source CSS seem to be causing incorrect relative paths in the built assets/css/main.css. In the generated file, the path is ../assets/fonts/, which resolves to assets/assets/fonts/ if the CSS is in assets/css/. This will prevent fonts from loading. Please adjust the paths to be relative to the output directory.

  src: url("../fonts/Inter-Light.woff2") format("woff2");

[gemini-code-assist]

The Turkish landing page (index.html) contains a significant amount of untranslated English content in the Hero, Products, and About sections. To maintain a professional localized experience, all user-facing text should be translated into Turkish.

Suggested change

	<h1 class="text-4xl sm:text-5xl md:text-7xl font-extrabold font-headline text-white mb-6 leading-tight tracking-tight">
	Building the Future of<br/>
	<span class="text-amber-500">Data Infrastructure</span>
	</h1>
	<h1 class="text-4xl sm:text-5xl md:text-7xl font-extrabold font-headline text-white mb-6 leading-tight tracking-tight">
	Veri Altyapısının<br/>
	<span class="text-amber-500">Geleceğini İnşa Ediyoruz</span>
	</h1>

[gemini-code-assist]

The mobile menu toggle script is missing accessibility attributes and UX refinements. Specifically, it should toggle aria-expanded on the button and aria-hidden on the menu. Additionally, the menu should automatically close when an anchor link is clicked to improve the user experience on mobile.

    const menuBtn = document.getElementById('mobileMenuBtn');
    const menu = document.getElementById('mobileMenu');
    menuBtn.addEventListener('click', () => {
      const isHidden = menu.classList.toggle('hidden');
      menuBtn.setAttribute('aria-expanded', !isHidden);
      menu.setAttribute('aria-hidden', isHidden);
    });
    menu.querySelectorAll('a').forEach(link => {
      link.addEventListener('click', () => {
        menu.classList.add('hidden');
        menuBtn.setAttribute('aria-expanded', 'false');
        menu.setAttribute('aria-hidden', 'true');
      });
    });

[gemini-code-assist]

For consistency and robustness across different environments (especially when pages are in subdirectories like /en/), it is recommended to use root-relative paths (starting with /) for all static assets.

Suggested change

	<link rel="stylesheet" href="assets/css/main.css"/>
	<!-- Font Awesome (async) -->
	<link rel="stylesheet" href="assets/css/font-awesome.min.css" media="print" onload="this.media='all'"/>
	<link rel="stylesheet" href="/assets/css/main.css"/>
	<!-- Font Awesome (async) -->
	<link rel="stylesheet" href="/assets/css/font-awesome.min.css" media="print" onload="this.media='all'"/>

[gemini-code-assist]

The mobile menu button and container are missing critical accessibility attributes. Adding aria-expanded, aria-controls, and aria-hidden ensures that screen readers can correctly interpret the state of the navigation menu.

Suggested change

	<button id="mobileMenuBtn" class="md:hidden text-white text-xl" aria-label="Menüyü aç">
	<i class="fa fa-bars"></i>
	</button>
	</div>
	</div>
	<!-- End Preloader -->
	<button id="themeBtn"><i class="far fa-moon"></i></button>
	<div class="video-modal">
	<div class="video-modal-content">
	<span class="close-btn">&times;</span>
	<iframe allow="autoplay; encrypted-media" allowfullscreen></iframe>
	</div>
	<!-- Mobile menu -->
	<div id="mobileMenu" class="hidden md:hidden bg-zinc-950/95 backdrop-blur-md border-t border-zinc-800 px-6 pb-6">
	<button id="mobileMenuBtn" class="md:hidden text-white text-xl" aria-label="Menüyü aç" aria-expanded="false" aria-controls="mobileMenu">
	<i class="fa fa-bars"></i>
	</button>
	</div>
	</div>
	<!-- Mobile menu -->
	<div id="mobileMenu" class="hidden md:hidden bg-zinc-950/95 backdrop-blur-md border-t border-zinc-800 px-6 pb-6" aria-hidden="true">

[coderabbitai]

Actionable comments posted: 5

🧹 Nitpick comments (2)

index-new.html (1)

6-57: Avoid publishing a second copy of the landing page.

This is another full root-level landing page with production metadata and the same canonical target as /. If it is only a staging artifact, keeping it in the web root invites accidental indexing and content drift alongside index.html.

Move it out of the published artifact, or add a noindex guard if you need to keep it in the repository.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@index-new.html` around lines 6 - 57, This file is a duplicate production
landing page (index-new.html) that risks accidental indexing; either remove it
from the published web root or add a noindex guard. To fix: if this is a staging
artifact, move or exclude index-new.html from the deployed assets (remove from
build/publish list); otherwise add a robots noindex meta tag (<meta
name="robots" content="noindex">) near the existing meta tags and change the
canonical/link alternates to point to a non-production preview URL or remove
them so it cannot claim the same canonical as index.html; locate the edits
around the title/og/canonical blocks and the JSON-LD block in index-new.html.

index-old-aiero.html (1)

9-73: Archive pages should not stay indexable in the public root.

As a rollback copy this is useful, but keeping it as a standalone root HTML page leaves the old site publicly reachable with live metadata and assets. That creates a stale entry point even after the redesign ships.

Move it outside the published artifact, or add a noindex guard if it must stay in the repository.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@index-old-aiero.html` around lines 9 - 73, The archive HTML
(index-old-aiero.html) is currently indexable via its <head> metadata and public
assets; either remove/move this rollback file out of the published artifact or
add a noindex guard in the <head> to prevent indexing (e.g., insert a <meta
name="robots" content="noindex"> and/or X-Robots-Tag on responses), and ensure
any canonical/og/twitter tags are removed or updated so search engines and
social previews won't treat this page as live.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@en/index.html`:
- Line 60: The skip link is permanently moved off-screen (left:-9999px) so it
remains invisible when focused; update the styling for the element with class
"skip-link" (the <a> anchor) to keep it visually hidden by default but bring it
into view when focused—add a :focus (and :active) CSS rule that resets
left/top/width/height or uses transform/clip to position it on-screen (e.g.,
left/top to a visible offset, restore width/height/overflow) so keyboard users
can see and use the link when tabbing.

In `@index.html`:
- Around line 6-7: Page at lang="tr" still contains English strings; update the
Turkish variant by translating the <title> element, the <meta
name="description"> content, navigation labels, hero headline/body, and primary
CTA text into Turkish so the root (/) is a proper TR mirror of the /en/ page;
look for the HTML elements <title>, <meta name="description">, nav links
(navigation labels), the hero section (headline/paragraph), and the main CTA
button text and replace their English copy with the correct Turkish equivalents
used elsewhere in the project.
- Line 60: The skip link anchor (<a href="#main-content" class="skip-link">) is
visually hidden via an inline style left:-9999px even on focus; add CSS to make
.skip-link visible when focused (e.g., override the off-screen positioning on
:focus or :focus-visible to bring it into view, restore width/height/left/top
and any padding/background so keyboard users can see and use it) and remove or
adjust the inline positioning so the :focus rule takes effect.

In `@src/input.css`:
- Around line 17-18: The font `@font-face` src URLs are written relative to the
source file and produce paths like /assets/assets/fonts/... in the emitted
assets/css/main.css; update each src: url("...") entry (e.g., the lines
referencing Inter-Light.woff2, Inter-Regular.woff2, Inter-Medium.woff2,
Inter-SemiBold.woff2, Inter-Bold.woff2, Inter-ExtraBold.woff2) so they point
from the built CSS location to the fonts directory (use ../fonts/Inter-*.woff2
or an absolute /assets/fonts/Inter-*.woff2) so the compiled assets/css/main.css
resolves to /assets/fonts/... instead of /assets/assets/fonts/....

In `@stitch-reference.html`:
- Around line 7-10: stitch-reference.html currently pulls Tailwind via the CDN
and includes Google Fonts/Material Symbols (with Material Symbols linked twice),
which reintroduces third-party requests; either remove it from publishing by
adding stitch-reference.html to .gitignore (or your deploy exclude list) OR
update the file to use the same local assets as index.html/en/index.html:
replace the CDN <script> and external <link> tags with the local
assets/css/main.css and the Font Awesome/local icon approach, and remove the
duplicate Material Symbols <link> entry so only the local asset references
remain.

---

Nitpick comments:
In `@index-new.html`:
- Around line 6-57: This file is a duplicate production landing page
(index-new.html) that risks accidental indexing; either remove it from the
published web root or add a noindex guard. To fix: if this is a staging
artifact, move or exclude index-new.html from the deployed assets (remove from
build/publish list); otherwise add a robots noindex meta tag (<meta
name="robots" content="noindex">) near the existing meta tags and change the
canonical/link alternates to point to a non-production preview URL or remove
them so it cannot claim the same canonical as index.html; locate the edits
around the title/og/canonical blocks and the JSON-LD block in index-new.html.

In `@index-old-aiero.html`:
- Around line 9-73: The archive HTML (index-old-aiero.html) is currently
indexable via its <head> metadata and public assets; either remove/move this
rollback file out of the published artifact or add a noindex guard in the <head>
to prevent indexing (e.g., insert a <meta name="robots" content="noindex">
and/or X-Robots-Tag on responses), and ensure any canonical/og/twitter tags are
removed or updated so search engines and social previews won't treat this page
as live.

🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8095ef5c-4ba1-482a-acd6-233bf3641c04

📥 Commits

Reviewing files that changed from the base of the PR and between e67d6d7 and 9824dad.

⛔ Files ignored due to path filters (5)

• assets/fonts/Inter-Bold.woff2 is excluded by !**/*.woff2
• assets/fonts/Inter-Light.woff2 is excluded by !**/*.woff2
• assets/fonts/Inter-Medium.woff2 is excluded by !**/*.woff2
• assets/fonts/Inter-Regular.woff2 is excluded by !**/*.woff2
• assets/fonts/Inter-SemiBold.woff2 is excluded by !**/*.woff2

📒 Files selected for processing (8)

• .gitignore
• assets/css/main.css
• en/index.html
• index-new.html
• index-old-aiero.html
• index.html
• src/input.css
• stitch-reference.html

📜 Review details

🧰 Additional context used

🪛 Stylelint (17.6.0)

assets/css/main.css

[error] 2-2: Unexpected duplicate "-webkit-text-decoration" (declaration-block-no-duplicate-properties)

(declaration-block-no-duplicate-properties)

---

[error] 2-2: Unexpected duplicate "-webkit-text-decoration" (declaration-block-no-duplicate-properties)

(declaration-block-no-duplicate-properties)

---

[error] 2-2: Unexpected duplicate "-webkit-text-decoration-color" (declaration-block-no-duplicate-properties)

(declaration-block-no-duplicate-properties)

---

[error] 2-2: Expected "button" to be "auto" (declaration-property-value-keyword-no-deprecated)

(declaration-property-value-keyword-no-deprecated)

---

[error] 2-2: Expected "button" to be "auto" (declaration-property-value-keyword-no-deprecated)

(declaration-property-value-keyword-no-deprecated)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected "SFMono-Regular" to be "sfmono-regular" (value-keyword-case)

(value-keyword-case)

---

[error] 2-2: Expected "Menlo" to be "menlo" (value-keyword-case)

(value-keyword-case)

---

[error] 2-2: Expected "Monaco" to be "monaco" (value-keyword-case)

(value-keyword-case)

---

[error] 2-2: Expected "Consolas" to be "consolas" (value-keyword-case)

(value-keyword-case)

---

[error] 2-2: Expected "currentColor" to be "currentcolor" (value-keyword-case)

(value-keyword-case)

src/input.css

[error] 13-13: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 20-20: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 27-27: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 34-34: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 41-41: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 50-50: Unexpected quotes around "Sora" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 60-60: Unexpected quotes around "Sora" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 3-3: Unexpected unknown at-rule "@theme" (scss/at-rule-no-unknown)

(scss/at-rule-no-unknown)

🔇 Additional comments (1)

.gitignore (1)

23-24: Looks good — .gitmem/ is appropriately ignored.

This aligns with the existing ignore policy and keeps local environment/memory artifacts out of version control.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Make the skip link visible on focus.

The link stays at left:-9999px even when focused, so keyboard users can tab to it but cannot actually see or use the shortcut.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@en/index.html` at line 60, The skip link is permanently moved off-screen
(left:-9999px) so it remains invisible when focused; update the styling for the
element with class "skip-link" (the <a> anchor) to keep it visually hidden by
default but bring it into view when focused—add a :focus (and :active) CSS rule
that resets left/top/width/height or uses transform/clip to position it
on-screen (e.g., left/top to a visible offset, restore width/height/overflow) so
keyboard users can see and use the link when tabbing.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Make the skip link visible on focus.

The link stays at left:-9999px even when focused, so keyboard users can tab to it but cannot actually see or use the shortcut.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@index.html` at line 60, The skip link anchor (<a href="#main-content"
class="skip-link">) is visually hidden via an inline style left:-9999px even on
focus; add CSS to make .skip-link visible when focused (e.g., override the
off-screen positioning on :focus or :focus-visible to bring it into view,
restore width/height/left/top and any padding/background so keyboard users can
see and use it) and remove or adjust the inline positioning so the :focus rule
takes effect.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# Find the stitch-reference.html file
fd "stitch-reference.html" --type f

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 100

---

🏁 Script executed:

# Check for build/deployment configuration files
fd -e "package.json" -e "build.js" -e "vite.config" -e "webpack.config" -e "next.config" -e ".gitignore" -e "Makefile" --type f | head -20

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 61

---

🏁 Script executed:

# Look for index.html files
fd "index.html" --type f

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 103

---

🏁 Script executed:

# Check stitch-reference.html line count and read lines 1-20
wc -l stitch-reference.html && head -20 stitch-reference.html

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 1088

---

🏁 Script executed:

# Check index.html line count and read first 30 lines
wc -l index.html && head -30 index.html

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 1768

---

🏁 Script executed:

# Check for deployment/build config
find . -name ".gitignore" -o -name "package.json" -o -name ".github" -type d | head -5

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 101

---

🏁 Script executed:

# Read index.html to see CSS/font handling (around line 30-60)
sed -n '30,70p' index.html

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 2146

---

🏁 Script executed:

# Read en/index.html first 30 lines to see its approach
head -30 en/index.html

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 1761

---

🏁 Script executed:

# Check .gitignore for excluded files
cat .gitignore

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 258

---

🏁 Script executed:

# Check GitHub workflows for build/deploy config
find .github -type f -name "*.yml" -o -name "*.yaml" | xargs cat 2>/dev/null

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 1765

---

🏁 Script executed:

# Check if there are any other HTML files and their purpose
find . -name "*.html" -type f | sort

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 429

---

🏁 Script executed:

# Look for any README or documentation about stitch-reference.html
find . -name "README*" -o -name "*.md" | xargs grep -l "stitch-reference" 2>/dev/null

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 63

---

🏁 Script executed:

# Check git history to understand purpose of stitch-reference.html
git log --oneline -5 -- stitch-reference.html 2>/dev/null || echo "No git history available"

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 131

---

🏁 Script executed:

# Check if there's a build script or deploy config in package.json
cat package.json 2>/dev/null || echo "No package.json found"

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 100

---

🏁 Script executed:

# Look for any documentation or comments in stitch-reference.html about its purpose
head -50 stitch-reference.html | tail -30

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 893

---

🏁 Script executed:

# Check if there are any static site generator configs (Jekyll, Hugo, etc.)
find . -maxdepth 2 -name "_config.yml" -o -name "config.toml" -o -name "hugo.toml" 2>/dev/null

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 61

---

🏁 Script executed:

# Check assets/css directory to understand the built CSS approach
ls -la assets/css/ 2>/dev/null

Repository: CalmKernelTR/calmkerneltr.github.io

Length of output: 726

---

Exclude stitch-reference.html from the published site or align it with local CSS/fonts.

This file loads Tailwind from CDN plus Google Fonts and Material Symbols, and includes the Material Symbols stylesheet twice. Since it's tracked in git and not explicitly excluded from deployment, it will be served by GitHub Pages, which reintroduces the third-party requests and privacy concerns the rest of the PR eliminates. Either add it to .gitignore or update it to use the local assets/css/main.css and Font Awesome approach already in place for index.html and en/index.html.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@stitch-reference.html` around lines 7 - 10, stitch-reference.html currently
pulls Tailwind via the CDN and includes Google Fonts/Material Symbols (with
Material Symbols linked twice), which reintroduces third-party requests; either
remove it from publishing by adding stitch-reference.html to .gitignore (or your
deploy exclude list) OR update the file to use the same local assets as
index.html/en/index.html: replace the CDN <script> and external <link> tags with
the local assets/css/main.css and the Font Awesome/local icon approach, and
remove the duplicate Material Symbols <link> entry so only the local asset
references remain.

[coderabbitai]

Actionable comments posted: 1

♻️ Duplicate comments (1)

index.html (1)

16-16: ⚠️ Potential issue | 🟡 Minor

OG and Twitter titles are also English.

For consistent Turkish SEO/social sharing, these should match the translated title.

🌐 Suggested diff

-  <meta property="og:title" content="CalmKernel — Building the Future of Data Infrastructure"/>
+  <meta property="og:title" content="CalmKernel — Veri Altyapısının Geleceğini İnşa Ediyoruz"/>

Also apply to line 24:

-  <meta name="twitter:title" content="CalmKernel — Building the Future of Data Infrastructure"/>
+  <meta name="twitter:title" content="CalmKernel — Veri Altyapısının Geleceğini İnşa Ediyoruz"/>

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@index.html` at line 16, The Open Graph and Twitter title meta tags are still
English; update the content of the meta property="og:title" and the
corresponding meta name="twitter:title" tags to use the translated Turkish title
(the same text used for the page title translation) so social previews and SEO
reflect the Turkish title consistently.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@index.html`:
- Line 6: The page <title> is still in English while the document uses
lang="tr"; update the <title> element content from "CalmKernel — Building the
Future of Data Infrastructure" to the Turkish equivalent (for example
"CalmKernel — Veri Altyapısının Geleceğini İnşa Ediyoruz") so it matches the
Turkish hero text and improves localization/SEO.

---

Duplicate comments:
In `@index.html`:
- Line 16: The Open Graph and Twitter title meta tags are still English; update
the content of the meta property="og:title" and the corresponding meta
name="twitter:title" tags to use the translated Turkish title (the same text
used for the page title translation) so social previews and SEO reflect the
Turkish title consistently.

🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2b072ea5-d9e9-4716-a347-0e02302be90b

📥 Commits

Reviewing files that changed from the base of the PR and between 9824dad and c3f52f0.

📒 Files selected for processing (5)

• assets/css/cookie-consent.css
• assets/css/main.css
• en/index.html
• index.html
• src/input.css

✅ Files skipped from review due to trivial changes (1)

• assets/css/cookie-consent.css

📜 Review details

🧰 Additional context used

🪛 Stylelint (17.6.0)

assets/css/main.css

[error] 2-2: Unexpected duplicate "-webkit-text-decoration" (declaration-block-no-duplicate-properties)

(declaration-block-no-duplicate-properties)

---

[error] 2-2: Unexpected duplicate "-webkit-text-decoration" (declaration-block-no-duplicate-properties)

(declaration-block-no-duplicate-properties)

---

[error] 2-2: Unexpected duplicate "-webkit-text-decoration-color" (declaration-block-no-duplicate-properties)

(declaration-block-no-duplicate-properties)

---

[error] 2-2: Expected "button" to be "auto" (declaration-property-value-keyword-no-deprecated)

(declaration-property-value-keyword-no-deprecated)

---

[error] 2-2: Expected "button" to be "auto" (declaration-property-value-keyword-no-deprecated)

(declaration-property-value-keyword-no-deprecated)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected quotes around "url" function argument (function-url-quotes)

(function-url-quotes)

---

[error] 2-2: Expected "SFMono-Regular" to be "sfmono-regular" (value-keyword-case)

(value-keyword-case)

---

[error] 2-2: Expected "Menlo" to be "menlo" (value-keyword-case)

(value-keyword-case)

---

[error] 2-2: Expected "Monaco" to be "monaco" (value-keyword-case)

(value-keyword-case)

---

[error] 2-2: Expected "Consolas" to be "consolas" (value-keyword-case)

(value-keyword-case)

---

[error] 2-2: Expected "currentColor" to be "currentcolor" (value-keyword-case)

(value-keyword-case)

src/input.css

[error] 13-13: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 20-20: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 27-27: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 34-34: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 41-41: Unexpected quotes around "Inter" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 50-50: Unexpected quotes around "Sora" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 60-60: Unexpected quotes around "Sora" (font-family-name-quotes)

(font-family-name-quotes)

---

[error] 3-3: Unexpected unknown at-rule "@theme" (scss/at-rule-no-unknown)

(scss/at-rule-no-unknown)

🔇 Additional comments (9)

en/index.html (3)

60-60: Skip link remains invisible on focus — accessibility issue persists.

The skip link has left:-9999px in inline styles with no :focus override, so keyboard users cannot see it when tabbed to.

♿ Proposed fix: Add focus-visible styles

Add a <style> block in <head> or to your CSS file:

.skip-link:focus,
.skip-link:focus-visible {
  left: 0 !important;
  top: 0 !important;
  width: auto !important;
  height: auto !important;
  overflow: visible !important;
}

Or replace the inline style with a class that handles both hidden and focused states.

---

77-88: Mobile menu ARIA implementation looks correct.

The button correctly uses aria-expanded, aria-controls, and the menu uses aria-hidden. The script properly syncs these attributes on toggle and when links are clicked.

---

330-332: Cookie consent integration is properly included.

The KVKK cookie consent CSS and JS are correctly loaded, addressing the compliance requirement.

index.html (3)

60-60: Skip link remains invisible on focus — same issue as en/index.html.

The inline left:-9999px style has no focus override. Apply the same fix suggested for the English page.

---

335-337: Cookie consent is now properly integrated.

The KVKK cookie consent CSS and JS are correctly loaded, resolving the compliance concern from the previous review.

---

67-111: Turkish body content translation looks complete.

Navigation labels, hero headline, CTA buttons, and descriptive text are properly translated to Turkish.

src/input.css (2)

12-46: Font paths are now correct — LGTM.

The paths have been fixed from the previous ../assets/fonts/... to ../fonts/..., which correctly resolves from the compiled assets/css/main.css location to assets/fonts/.

---

3-9: Tailwind v4 theme configuration looks good.

The @theme directive is valid Tailwind CSS v4 syntax. The static analysis warning (scss/at-rule-no-unknown) is a false positive since the linter is applying SCSS rules to a Tailwind file.

assets/css/main.css (1)

1-2: Auto-generated Tailwind output — no action required.

This is compiled/minified output from Tailwind CSS v4.2.2. The static analysis warnings (duplicate properties, URL quotes, keyword casing) are artifacts of the minifier and standard CSS resets for cross-browser compatibility. These are not actionable.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Page title still in English on Turkish variant.

The <title> remains "CalmKernel — Building the Future of Data Infrastructure" despite lang="tr". For proper localization and SEO, consider translating to match the Turkish hero text (e.g., "CalmKernel — Veri Altyapısının Geleceğini İnşa Ediyoruz").

🌐 Suggested diff

-  <title>CalmKernel — Building the Future of Data Infrastructure</title>
+  <title>CalmKernel — Veri Altyapısının Geleceğini İnşa Ediyoruz</title>

📝 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

	<title>CalmKernel — Building the Future of Data Infrastructure</title>
	<title>CalmKernel — Veri Altyapısının Geleceğini İnşa Ediyoruz</title>

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@index.html` at line 6, The page <title> is still in English while the
document uses lang="tr"; update the <title> element content from "CalmKernel —
Building the Future of Data Infrastructure" to the Turkish equivalent (for
example "CalmKernel — Veri Altyapısının Geleceğini İnşa Ediyoruz") so it matches
the Turkish hero text and improves localization/SEO.

[blocksorg]

[Severity 7] External image URL compiles into production main.css

This Tailwind arbitrary class causes https://www.transparenttextures.com/patterns/carbon-fibre.png to be compiled into the shared assets/css/main.css (confirmed via build output). Even though this class is only in the reference file and not rendered on production pages, Tailwind v4 scans all HTML files during the build, so the utility gets emitted.

Impact:

• Every page that loads main.css sends a browser request to transparenttextures.com (if the class is matched in the browser's rendering path — at minimum the CSS rule is present in the stylesheet).
• This contradicts the PR's claim of "Zero external dependencies" and may conflict with the site's KVKK/GDPR stance (third-party domain = potential IP logging).

Fix options:

1. Remove this class from stitch-reference.html and replace with a local CSS custom class or inline style.
2. Exclude stitch-reference.html from the Tailwind content scan (add a /* tailwind-ignore */ comment or configure the scanner to skip it).
3. Move stitch-reference.html out of the repo root (e.g. to a _drafts/ or gitignored directory) so it isn't deployed or scanned.

[blocksorg]

Severity 8 — KVKK/GDPR violation: stitch-reference.html is publicly served with Google Fonts CDN calls and no noindex guard

This file is committed to the web root and is publicly accessible. It contains:

• <script src="https://cdn.tailwindcss.com?plugins=forms,container-queries"> — makes an external request leaking visitor IPs
• Two <link href="https://fonts.googleapis.com/..."> calls loading Sora/Inter
• A <link href="https://fonts.googleapis.com/..."> for Material Symbols

The PR's core justification is removing all Google Fonts CDN dependencies for KVKK/GDPR compliance ("Zero external font dependencies"). Having this file served publicly from the root directly contradicts that goal — any visitor who lands on this URL triggers external requests to Google's servers.

Additionally, the file carries live <title> and Open Graph metadata pointing to the production site, and there is no <meta name="robots" content="noindex"> to prevent crawler indexing.

Recommended fix: Either add <meta name="robots" content="noindex, nofollow"> to the <head> and strip or comment out the Google CDN <link>/<script> tags, or move the file out of the published web root (e.g., rename to _stitch-reference.html or add it to a non-served docs directory).

[blocksorg]

Severity 7 — External transparenttextures.com URL compiled into production CSS

The compiled main.css contains this utility class (generated because Tailwind scanned stitch-reference.html):

.bg-\[url\(\'https\:\/\/www\.transparenttextures\.com\/patterns\/carbon-fibre\.png\'\)\]{
  background-image: url(https://www.transparenttextures.com/patterns/carbon-fibre.png)
}

This class is not used in index.html or en/index.html, so the URL is not fetched at runtime currently. However:

1. Dead weight — increases CSS bundle size with a utility that serves no active page
2. Future risk — if the class is ever applied, it would make an external network request to a third-party domain, breaking the "zero external dependencies" contract and raising KVKK concerns
3. Root cause — Tailwind's content scanning is picking up stitch-reference.html, which uses bg-[url('https://www.transparenttextures.com/...')]

Recommended fix: Exclude stitch-reference.html from Tailwind's content scanning in your build config (e.g., via a tailwind.config.js content exclude pattern, or by moving the file outside the scan path), then rebuild main.css.

[blocksorg]

Severity 8 — Missing assets will cause silent UI breakage

Three assets referenced here do not exist in the repository:

1. /assets/js/cookie-consent.js (line 334) — the JS file is absent (assets/js/ directory does not exist). The KVKK cookie consent banner CSS is loaded but the banner logic never runs.
2. /assets/images/calmkernel-icon.svg (line 49) — favicon returns 404.
3. /assets/css/font-awesome.min.css (lines 55–56) — if this file is not present (it is not in the PR diff), all <i class="fas fa-..."> and <i class="fab fa-..."> icons render as invisible/broken text, collapsing the entire icon-heavy UI silently.

Please confirm these files exist on the deployment target (i.e., were committed separately), or add them to this PR. A missing Font Awesome CSS means every icon on the page — broom, chart-line, layer-group, shield-alt, globe-europe, etc. — will be invisible.

[blocksorg]

Severity 7 — aria-expanded state is inverted

var open = menu.classList.toggle('hidden');
btn.setAttribute('aria-expanded', !open);

classList.toggle('hidden') returns true when the class was added (menu is now hidden/closed) and false when it was removed (menu is now visible/open). Therefore !open evaluates to true when the menu is hidden — the opposite of what screen readers expect.

The correct logic is:

var isNowHidden = menu.classList.toggle('hidden');
btn.setAttribute('aria-expanded', String(!isNowHidden));
menu.setAttribute('aria-hidden', String(isNowHidden));

The same bug exists in en/index.html at the equivalent script block.

[blocksorg]

Severity 8 — Sora font files are missing from the repository

main.css references two Sora font files:

• url(../fonts/sora-latin.woff2)
• url(../fonts/sora-latin-ext.woff2)

However, assets/fonts/ only contains Inter variants (Inter-Bold.woff2, Inter-Light.woff2, Inter-Medium.woff2, Inter-Regular.woff2, Inter-SemiBold.woff2). The Sora files are not present in this PR's diff and do not exist in the repository.

font-headline (used on h1, h2, section titles, and the logo) will silently fall back to sans-serif. The headline font is a core part of the new visual identity — this needs to be committed alongside the CSS.

[devin-ai-integration]

Devin Review found 3 new potential issues.

View 7 additional findings in Devin Review.

[devin-ai-integration]

🔴 Missing cookie-consent.js breaks KVKK cookie consent functionality

Both index.html:334 and en/index.html:329 include <script src="/assets/js/cookie-consent.js" defer></script>, but the assets/js/ directory does not exist in the repository. The PR adds assets/css/cookie-consent.css (the styling) but omits the corresponding JavaScript file. The cookie consent banner (required for KVKK compliance, as noted in the HTML comment <!-- Cookie Consent (KVKK) -->) will render as styled HTML but have no functional behavior — users cannot accept cookies, and the banner cannot be dismissed.

(Refers to line 689)

Prompt for agents

Both index.html (line 689) and en/index.html (line 329) reference /assets/js/cookie-consent.js but this file does not exist. The assets/js/ directory is entirely missing from the repository. The cookie-consent.css was added to assets/css/ but the JS counterpart was not. A cookie-consent.js file needs to be created in assets/js/ that handles: (1) checking if the user has already consented (e.g. via a cookie or localStorage), (2) showing/hiding the #cookieConsent banner, (3) handling the #ccAccept button click to record consent and hide the banner. The CSS already defines #cookieConsent, .cc-hidden, .cc-inner, and #ccAccept selectors.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🔴 Missing font-awesome.min.css causes all icons to not render

Both index.html:410 and en/index.html:55 reference /assets/css/font-awesome.min.css (loaded async with media="print" onload="this.media='all'"), but this file does not exist in assets/css/ (which only contains main.css and cookie-consent.css). The site uses Font Awesome icons throughout — navigation hamburger (fa fa-bars), GitHub icons (fab fa-github), product section icons (fas fa-broom, fas fa-chart-line, fas fa-layer-group), about section icons (fas fa-globe-europe, fas fa-shield-alt, fas fa-code-branch, fas fa-robot), and social links (fab fa-linkedin-in). None of these icons will render, leaving blank spaces throughout the UI.

(Refers to lines 410-411)

Prompt for agents

Both index.html (lines 410-411) and en/index.html (lines 55-56) reference /assets/css/font-awesome.min.css but this file does not exist in the repository. The assets/css/ directory only contains main.css and cookie-consent.css. Font Awesome CSS (and its associated webfont files) need to be added to the assets directory. You can either: (1) download Font Awesome (free version) and place font-awesome.min.css in assets/css/ along with the webfonts directory, or (2) use a CDN link instead of a local file. The site uses both 'fas' (solid), 'fab' (brands), 'fa' (v4 compat), and 'far' (regular) icon prefixes, so Font Awesome 5+ Free is needed. Self-hosting is preferred given the project's GDPR/KVKK compliance goals.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🔴 Missing Sora font files cause headline font to not render

The compiled assets/css/main.css includes @font-face declarations referencing ../fonts/sora-latin.woff2 and ../fonts/sora-latin-ext.woff2, but neither file exists in assets/fonts/. The PR adds all five Inter font .woff2 files but omits the Sora files. Since font-headline is defined as "Sora", sans-serif (src/input.css:4) and used extensively in both index.html and en/index.html for headings (font-headline class), all headline text will fall back to generic sans-serif instead of the intended Sora typeface.

Prompt for agents

The src/input.css file (lines 49-68) defines two @font-face blocks for the Sora font family referencing ../fonts/sora-latin.woff2 and ../fonts/sora-latin-ext.woff2. These declarations are compiled into assets/css/main.css. However, the assets/fonts/ directory only contains Inter font files (Inter-Light.woff2, Inter-Regular.woff2, Inter-Medium.woff2, Inter-SemiBold.woff2, Inter-Bold.woff2). The two Sora .woff2 files need to be added to assets/fonts/ alongside the Inter files. These can be obtained from Google Fonts or a similar source and self-hosted for GDPR/KVKK compliance as intended by the project.

---

Was this helpful? React with 👍 or 👎 to provide feedback.