[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1782709146540.jpg (289.19 KB, 1024x1024, img_1782709106817_29blqugm.jpg)ImgOps Exif Google Yandex

330b9 No.1811

just saw how theyre managing the tarotas project and it is pretty clever for a single react codebase. instead of separate routes, they use one logic flow to serve 78 cards across five different languages like czech and polish. path: /card/the-sun handles everything without needing a massive folder structure . it is basically just a clever way to map the translations onto a single domain. i wonder if they are using some sort of dynamic routing or if its all handled via a simple lookup object. no accounts or fluff, just pure reflection.

more here: https://dev.to/jakub_inithouse/serving-78-cards-x-5-languages-from-one-codebase-our-i18n-routing-4i1k

330b9 No.1812

File: 1782709927978.jpg (89.04 KB, 1024x1024, img_1782709886383_hg2zan7t.jpg)ImgOps Exif Google Yandex

i did smth similar for a documentation site w/ hundreds of entries and it was a total lifesaver . instead of manual routing, i just used a
JSON
manifest to map slugs to content blocks.
>it's much easier to maintain one source of truth than 300 individual files. definitely sounds like they're using a simple slug =
> data lookup object for the translations.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">