Changelog

After an unexpected GitHub account suspension and a month long downtime, the platform has been rebuilt from the ground up:

• Template Model & Framework Shift: Returned to an SSG template model powered by Astro and customized heavily to remove friction and keep the focus entirely on writing.
• Obfuscated Route Architecture: Deployed short scrambled route paths across the site for Writing (/t8x2k9q), Archive (/f4k3m8s), Keys (/z3v9x4p), Lekhathawn (/l8x9k2p), and Kei (/w5r2y8p).
• Navigation & Brand Identity: Distributed header navigation tabs evenly across the container width, added active brand-orange underline indicators (after:bg-primary), and applied bolder font-bold tracking-tight typography.
• Post Page Layout & Card Framing: Framed article prose inside styled card panels (rounded-xl border border-neutral-800/80 bg-neutral-900/30), redesigned redacted post notices to a single sleek card with a lock icon, and removed underlines from “filed under” tag chips.
• Feed & Redaction System: Lowercased pagination controls without arrow symbols, added dual-state title hover states, and introduced contextual redaction notices (this letter has been redacted. vs this post has been redacted.).
• Typography & Drop Cap Control: Added dropCap: false frontmatter control to disable initial letters on short entries and all Lekhathawn letters.
• Footer & Legal Overhaul: Redesigned footer navigation with container-scoped gradient dividers and synced the global annotation quote (“Curating memories and un-sent letters.”).
• Content & Archive Synchronization: Synchronized 10 archive post file paths with clean slugified titles and published the new letter “The Need for Digitizing the Hmar Language”.

A major architectural shift focusing on minimalism, static content, and a new support ecosystem.

🏛 Architecture & Design↗

• Simplified to Static Journal: Removed complex dynamic components in favor of a clean, content-first static experience.
• New Header Design: Implemented a fixed, floating “pill” header with backdrop blur and responsive mobile menu overlay.
• Enhanced Footer: Redesigned footer with modular navigation columns, social integration, and improved typography.
• Manifesto Shell Integration: Refactored /about and /rules to use the immersive, isolated “Manifesto Shell” for focused reading.
• Tailwind v4 Upgrade: Fully integrated Tailwind CSS v4 for modern styling and better build performance.

💳 Support Ecosystem (Thangpuina)↗

• Razorpay Integration: Added a complete donation system allowing supporters to contribute via Razorpay.
• Supabase Backend: Integrated Supabase for tracking donations and managing supporter data.
• Edge Functions: Deployed custom Supabase Edge Functions for secure order creation and payment verification.
• Supporters Wall (Planned): Added the foundational /supporters route and logic; public listing to be enabled in a future update.

📝 Content & Organization↗

• New Blog Entries: Added “Man-made Constructs” and a detailed guide on creating a custom link-tree.
• Course Metadata Groundwork: Added a type field to blog frontmatter so posts can be marked as either regular journal entries or future course material.
• First Course Draft: Reclassified the website-building guide as type: "course" and made it publicly readable while the broader course experience is still being refined.
• Taxonomy Refinement: Moved categories and tags under the /blog route for better URL structure.
• Privacy First: Simplified data collection and removed user accounts.

🛠 Technical Improvements↗

• Framework Pinning: Locked Astro to v5.4.2 and Vite to v6.2.0 for long-term stability.
• Automated Workflows: Added scripts for managing Supabase secrets and image normalization.
• Search Logic: Prepared Pagefind integration (currently hidden for refinement).
• Course Navigation Prototype: Added a floating course table-of-contents component and blog layout hooks, but kept the desktop sidebar disabled until the interaction bugs are resolved.
• Course UI Containment: Removed inactive course UI wiring from the live blog renderer so course-marked entries continue to behave like standard journal posts until the sidebar is ready.
• Analytics Hook: Added the Umami tracking script to the shared layout for lightweight site analytics.
• 404 Refinement: Updated the not-found page with clearer navigation choices, safer Back behavior, and a more consistent editorial visual treatment.
• Documentation Refresh: Replaced the upstream theme README with BatchNode-specific project notes and updated agent guidance for course metadata and recovery-page UX.

Significant evolution of the platform’s core features and design standards:

• Retired Projects Feature: Formally removed the `/projects` collection and associated UI components to focus the platform entirely on the Journal experience. Existing project articles have been safely archived.
• Secure Redacted System: Implemented a new secure isolation system for private or redacted posts. These entries remain in the journal history and are clickable, but their content is physically excluded from the build output, rendering a premium “Restricted Access” UI with a blurred lock instead.
• Hero Body Image Spec: Established a new editorial standard for top-of-article images (1000x630, left-aligned, premium shadows/corners).
• Responsive Image Overhaul: Standardized all body images to a left-aligned, stacked layout. Fixed major mobile issues where images appeared “crushed” or inconsistently sized across different monitor resolutions.
• Unified Review Aesthetics: Migrated film review posters to the YAML header system for a consistent, floated side-column look on PCs.
• New Contact System: Launched a dedicated Contact page (`/contact`) featuring an AJAX-powered form (Formspree) with premium inline feedback and automated state management.
• Shop Button Placeholder: Added a perfectly aligned “Shop” action button to the landing page, complete with a blurred “Coming Soon” interaction.
• Documentation Update: Refreshed `AGENTS.md` to reflect the new architecture, privacy protocols, and image specifications.

Implemented a new “Ground Rules” page at /rules containing seven foundational protocols for self-actualization.

Aligned the “About” page with a new “Manifesto Shell” aesthetic—an immersive, minimalist, and isolated UI experience that bypasses standard site navigation. Both pages now feature a unified design with large typography, background watermarks, and a simplified “Back” navigation system. Added a dedicated “RULES” action button to the landing page.

Refined the site’s shared UI systems and content taxonomy:

• Shared Page Structure: Consolidated non-landing page headers into a reusable PageHeader component so page intros, breadcrumbs, and section navigation stay visually aligned.
• Archive UI Pass: Introduced a reusable ArchiveEntry pattern for blog, categories, projects, and tag archives, replacing several drifting list layouts with one more deliberate editorial row style.
• Category Writing System: Added a canonical category metadata map with summaries and descriptions, then used it to give both /categories and each category archive page more intentional language.
• Tag Normalization: Unified tag routing and frontmatter toward lowercase canonical tags, reducing duplicate archives caused by casing drift across blog posts and projects.
• Project Gallery Upgrade: Extended the projects schema to support imageCollections, then updated the project detail renderer so grouped galleries behave like the blog galleries, including horizontal navigation controls.
• Footer and Navigation Polish: Tightened header/footer alignment and improved navigation state styling to make the shell feel more consistent across the journal.

Formalized the Reviews category and transitioned the animation engine:

• Reviews Implementation: Added a specialized score field to the content schema, allowing for structured ratings (0-10) in reviews. Updated existing reviews (Maudie and Lars and the Real Girl) to use this system.
• Animation Engine Migration: Replaced GSAP with Anime.js V4 for more precise control over UI interactions and page reveals.
• Homepage Refinement: Removed the experimental Three.js 3D model from the homepage and reverted to a high-quality static image for better performance and aesthetic consistency.
• Refined Hover Interactions: Implemented subtle, minimalist hover effects for blog posts and social icons, prioritizing a grounded aesthetic over flashy movements.
• Technical Stability: Resolved a critical scope error in the 3D model component (AngelHero.astro) that was causing build failures.

Significant technical refinement and structural organization:

• Folder-Based Asset Management: Migrated all blog images from a flat root folder to slug-specific directories (e.g., /assets/images/blog/[slug]/). This improves codebase maintainability and prevents file naming collisions.
• Unified Tagging System: Overhauled the tagging logic for blog posts.
• Content Migration & Structure: Formally structured and imported raw Markdown entries into the production collection.

Major visual and structural updates to the landing and blog experience:

• 3D Integration: Added a high-fidelity 3D model of the Angel of Grief sculpture to the homepage using Three.js. Note: Currently disabled on mobile and tablets for performance; plan to optimize for touch devices in the future.
• Side-Column Images: Implemented a new structural feature allowing multiple images to be stacked in a dedicated right-side column on desktop views.
• Mobile Gallery: Optimized the image layout for mobile and tablets; multiple side-images now render as a smooth horizontal-scroll gallery with scroll snapping, rather than a vertical list.
• Enhanced Image Support: Added support for floated inline images within post bodies for more dynamic content layouts.
• Performance: Enforced WebP format for all new image assets to ensure fast loading times.

Added Pagefind for search and Breadcrumbs for better navigation.

I’ve updated the theme of my website to a more “journal” like aesthetic. I’ve also added a projects section, where I’ll be sharing some of the things I’ve been working on. I’m also planning on adding a tags section soon, but I’m still working on that.

I’ve updated my website again, but this time I’m using Astro. I finally felt that Jekyll was a bit too limiting for what I wanted to achieve, and I wanted to try something new. I’m really liking Astro so far, and I’m excited to see where this goes.

Changed the theme to “dark” and edited the scss for it and changed the background of codebox to darker.

I’ve enabled Categories and removed Guests. I’ve also added a button on one of my posts Journal Entry 12-01-2025. The idea is to enable switching between English, Mizo, and Hmar.

I’ve set my homepage to just display a :), which acts as a minimalistic entry point to the website. Clicking on it leads to the main menu located at /main/. This approach helps keep the journal and its contents from being too exposed, maintaining an element of subtlety and exclusivity for those who explore further.

I’ve updated all my blog posts to follow the title format Journal Entry d/m/y. I made this change because I believe it gives the website a more structured and expressive identity as a journal, editorial, opinion blog, or something in between—even if it doesn’t always sound like a traditional journal.

Additionally, I’ve added a guests section. While I don’t expect anyone to post there, I’ve created it to separate content like reviews, humor, commentaries, and general posts from entries meant to be more self-reflective. I think this distinction will help clarify the nature of the entries and make the site more organized.

When testing the website on the Mi Browser, I noticed it displays the site with a dark background, even though the default is a light background. I believe this is controlled by the browser’s system theme setting since I haven’t implemented any logic for this.

Regardless, I think adding a dark mode toggle would be a good idea for a future update. However, before that, I need to figure out a better way to organize my posts with categories and tags. So, while the dark mode feature is interesting, it will likely be a lower priority for now.

I’ve updated my GitHub website and I’m now using Jekyll. I originally started off building my own custom website, but I got stuck trying to create a posts page.

Although I really wanted (and tried) to build and maintain my own website with custom HTML, I realized I might spend too much time trying to define and maintain the website itself. It detracts from the purpose I started documenting my thoughts and putting myself out there, and also, I fear it might interfere with my main projects.

The website, though still under construction, is functional, and I suppose it’s just a matter of time before I figure out how to customize this to my own liking better.

I’ve moved to a new platform! I’ve created my own website hosted on GitHub, and I’m excited to continue my journey there. Thank you to everyone who has supported me so far, and I hope this new chapter brings more opportunities to share my story and thoughts.

This was my first post, originally shared on Blogger on September 24, 2024. I recently decided to move to WordPress, but I didn’t want to leave my posts behind, so I’ve reposted it here as they were.

Hi, I decided to start this blog as a means for me to stay honest, transparent, and share my story, my thoughts, and my journey through life. I’m not sure how much I should share because this is different from a private journal, so I guess I’ll have to figure that out. I’m not certain if I can keep this up in the long run or if the benefits outweigh the disadvantages, but I promise to try my best and to always be honest and transparent.

I will be using AI to correct my English grammar because I’m not a native English speaker, but I’ll do my best to keep the content my own creation. I’ll probably use ChatGPT to help structure the format of these posts, as I’m still not sure if I need a consistent structure or about the frequency of posts. I know nothing.

But I guess this is it for the first post. To anyone who stumbles into this blog and reads this post, I hope you know that you are blessed, you are loved, and you deserve to love yourself as much as you can.