Pages are rendered on the server at request time, so it always has the latest data
Includes all texts in all available translations
Automatic internationalisation based on your browsers preferred language
Fast and powerful “instant search” from the same API .net uses (which includes dictionaries)
Handles redirects for text URLs with the wrong translators name (this can be improved more though)
Home page loads 8.5x faster, DN 1 loads 5.8x faster, and search results 4.3x faster compared to .net[1] (but in some ways faster than .express too)
1,000% improved developer experience
Has a real favicon
This basically shares the experience of .express with everyone—whether you use the English translations on .net or not—but with zero additional key strokes
This uses Largest Contentful Paint as the metric, as its usually the most user perceivable indication of page load performance, and was measured via https://pagespeed.web.dev for desktop on 22/01/2026. See detailed stats here↩︎
Really great work! It’s quickly getting close to matching the functionality of the existing site. I notice the “editions” pages are missing, and all the various “methodology” etc pages, but those are easy enough to add.
Is there anything that the main site is doing that Astro couldn’t support?
i doubt it! astro is the gold-standard of modern static site dev
edit: and i dont see anything on the main site that would not only require it not being a static site, but would actually not be improved by it not being a static site
i think that sentence is my first quadruple negative
yes pali and chinese root-word lookups are missing, as are all the references/segmentation links other than the “main” ones. i think that is all thats missing from the text pages
great question! just thinking quickly, .now would break entirely if .net APIs ever went down, but .express is frozen in time forever and once built it only depends on its self. personally i like the offline archives it easily allows as well. i haven’t done either yet, but im pretty sure I can make the root word lookups on .express work the same as .net and have a negligible impact on performance without using any client js (because its all rendered before hand) but not sure how well that would fly on .now because its rendered on demand. express also has a cooler url
hm ive never seen this before. which browser and OS is this? the site colours look weird. have you tried the same links that do this in another browser/device? this looks like a text/sutta page yeah? but does this happen in any links you try to other pages? are you using the “suttacentral redirect” browser extension to redirect when you open links or are these direct links to .now? can you please share the links and what exact URLs do this? what if you navigate around the site does it still happen or only if you follow a link from somewhere else? if you can you send a video of opening a link and showing the behaviour, thats usually very helpful
That being said, I wanted to mention that the site’s performance is impressive; it’s super fast, and I really appreciate the multilingual support beyond just English. It’s a very well-executed site, and I like the favicon very much.
i really dont know whats going on here. i can’t reproduce on my mac in firefox, brave or safari, or on ios safari, those are not the site colours in either color scheme (is this really what it looks like on windows?!) and i dont know what in the code would be putting the /search-filter page below the footer like that, and especially causing it scroll to the bottom automatically.
how does it work in different browsers on the same machine? or even just an incognito window without any extensions running?
nonetheless, i did a redeploy of the site just for you just now (with the same code… can’t hurt) and it looks like youre using the english site, so i’d just use .express if this keeps happening, as all the english texts are on there
okay i just realised chrome 109 is ridiculously old (it hasn’t had official support even from google since 2023, which is a long time in tech) and doesnt have HTML popover support, which this site needs for basic functionality, so that would be it, probably among other now-standard things it doesn’t support. i suggest updating your browser if possible!
note that .express will have similar issues as it also depends on HTML popover
I also noticed that they are on Windows 7. Which, honestly I didn’t think was possible.
It kind of clashes with your HTML/CSS only ethos, but considering the target audience (monastics with ancient tech, global low resource communities) it might be a kindness to add in some kind of fall back. Perhaps you could even just do something that wasn’t a full replacement for browsers that don’t support it, just not quite so broken.
¯\_(ツ)_/¯