Rework blog into a modern personal one-page experience

[zerox80]

What changed

• rebuilt the homepage as a bold, responsive personal one-page blog
• introduced a modern first-person hero, topic marquee, filtered post grid, about section, and newsletter
• redesigned the header, mobile navigation, post cards, and footer around the new visual system
• kept CMS-driven content, edit controls, authentication links, and dynamic navigation intact
• replaced legacy portal copy and metadata with personal blog defaults while preserving custom CMS values
• added responsive typography, editorial grid details, motion preferences, and updated font/theme metadata
• split oversized Rust and React modules into smaller, focused files
• enforced a maximum of 500 lines per Rust/JavaScript file and 120 characters per line
• added an automated source-limit check to the npm scripts and CI workflow

Why

The previous UI spread the experience across a conventional knowledge-portal layout. This rework turns it into a
distinctive personal space for writing about changing interests, projects, and ideas. It keeps the main reading journey
on one cohesive page while preserving the existing CMS functionality. The source-size guard keeps the codebase within
the requested maintainability limits.

Impact

The frontend presentation changes substantially. The module splits preserve the existing behavior and no API contract
changes are intended. Existing article detail, admin, authentication, and tutorial routes continue to use the established
application structure.

Validation

• npm.cmd run check:file-limits — 189 files passed
• npm.cmd run lint
• npm.cmd run test -- --run — 40 tests passed
• npm.cmd run build
• cargo fmt --manifest-path backend/Cargo.toml -- --check
• cargo test --manifest-path backend/Cargo.toml -q — 105 tests passed, 3 ignored
• git diff --check
• browser QA of the final personal-blog copy, metadata, anchor structure, and horizontal overflow
• verified mobile menu, anchor navigation, responsive overflow, empty/error states, and header contrast on secondary routes

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
26984428	Triggered	Generic Password	f1ff694	backend/src/handlers/auth/tests.rs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}