Posts

Building Test Static School Website: Next.js (No RSC, No APIs) vs Plain React, Using ThemeWagon SI-Education Next.js Template

Quick Info Live mainly static test school website: https://ravisiyer.github.io/testschoolwspub/ Private GitHub source repo:  https://github.com/ravisiyer/testschoolws Si – Free Tailwind CSS Educational Website Template https://themewagon.com/themes/si-education/ MIT license Next.js template used for above test school website Seems to avoid using React Server Components(RSC). All the components that I examined had "use client" at the top. Has a virtually empty API file and so effectively does not use Next.js APIs Uses Tailwind CSS and TypeScript To deploy si-education project to GitHub Pages As my GitHub project source code is private, I needed a separate public GitHub project for deployment (hosting the exported static output). In next.config.ts, basePath had to be set to the public GitHub Pages repository name to ensure correct asset paths for JS, CSS, and images; without this, multiple 404 errors occurred: const basePath = '/testschoolwspub'; .nojekyll empty file ha...

Design of mainly static school website with free hosting that can evolve into dynamic full-stack web application (paid hosting)

Summary To summarize (and to validate your conclusion): Next.js + modern template gives you: current, industry-standard frontend practices Tailwind, TypeScript, auth scaffolding for future use good SEO and performance when statically built GitHub Pages (free tier) is a solid fit for: a mainly static rural school site long-term zero hosting cost easy custom-domain mapping when the school is ready Blogger or GHP-hosted JSON as a pseudo-headless backend provides: dynamic content where needed (notices, announcements, updates) zero backend hosting cost a usable authoring experience for non-technical users React / Next.js SSG keeps you in your strongest ecosystem: no need to fall back to plain JS easy hybrid model (prebuilt core pages + client-fetched dynamic sections) smooth upgrade path to paid hosting, APIs, or a full backend later Governance and ownership are handled cleanly: separate GitHub account for the school reversible email and access transfer no lock-in to you personally Ove...

Gita JSON files API Initial Version Done; Inviting Second Chunk Sponsorship for Remaining Work

The first chunk of work, sponsored by the first donor/sponsor, was done from 06-Jan-2026 to 14-Jan-2026 with total work time of 23 hours 35 minutes. Many thanks to the first sponsor for sponsoring this first chunk of work. As part of first chunk of work, initial version of Gita Static JSON files API was developed and hosted on GitHub Pages. To test this API, Gita frontend app version was modified to use this API, with limited functionality of only Swami Sivananda translation and commentary, and which is live at: https://gita-test.vercel.app/ . As of 15 Jan. 2026, the project work is paused awaiting sponsporship from interested persons. If there are persons who are interesed in sponsoring the second chunk of work (done by me at deeply discounted rates), they may please mail me at riyer02@gmail.com. But dear reader, please don't feel obliged in any way to sponsor such work. Sponsor(s) should contact me in this regard, only if they are really interested in patronizing such service to ...

Status of Project: Development of Gita Static JSON files API hosted on GitHub Pages and Modifying Gita Frontend App to Use it

Project Overview This project consist of two parts: Development of Gita Static JSON files API hosted on GitHub Pages Associated gita-data GitHub project:  https://github.com/ravisiyer/gita-data  gita-data Its  README  is the key documentation page for the hosted JSON APIs It follows the design provided in section of my blog post: Summary of best option for generous free-tier Gita API implementation . Modifying Gita Next.js frontend app (production live app in main branch) to use above gita-data JSON API Associated gita GitHub project:  https://github.com/ravisiyer/gita . As of now, this project has three parallelly maintained branches: datajson branch  has a test version that uses above JSON API. It is functional but has limited functionality of only one translator and commentator's text being shown. Here's  its README  and here's the deployed live app . main branch is not working as its GraphQL backend service is not available. datarest branch ...