SuttaCentral... Now!

Meta
1

So I made https://suttacentral.now–another fast and minimal alternative frontend to SuttaCentral.net

It’s like SuttaCentral Express, except

  • 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 :smiling_face_with_sunglasses:

  1. 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 ↩︎

11 Likes
2

This is some seriously amazing work! :slight_smile:

This is extraordinary, and it seems to work splendidly.

That there’s a root-translation side by side, the only thing missing from the main website is the on-click Pāli dictionary it seems?

There’s some work arounds to that — one is using DPD downloaded, though it doesn’t work for mobile.

Much merit for doing this work, thank you! :slight_smile:

4 Likes
3

Thank you so much, it’s so fast. Sadhu Sadhu Sadhu

2 Likes
4

I particularly like that one! :heart:

4 Likes
5

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?

4 Likes
6

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 :trophy:

1 Like
7

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

1 Like
8

Other than including all the translations, can you give a reason why someone would choose .now over .express as an end user?

Or perhaps the better question is, why would someone want express over now?

9

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 :joy:

1 Like
10

it always has up-to-date data (exact same as .net) because it fetches it on every page load

2 Likes
11

it would be “easy” to implement a yomutan like plugin to the website to allow custom dbs to be used for on clivk word lookup?

maybe even a dictionary for English so finally? :smiley:

12

I think you meant: “I don’t see anything on the main site that wouldn’t be improved by static rendering.”

If so: yes, I agree. Right tool for the right job :slight_smile:

13

dont take my negatives from me!

1 Like
15

too late! :wink: