Frontend of a headless csm for null translation website. Contains all translation from LLM and editing from users.
Go to file
2025-03-12 00:58:47 -04:00
public Ads.txt file 2025-03-11 18:53:20 -04:00
src Added ad-walled support, with counters and changed a lot of the current pages look to see funnel people toward that path 2025-03-12 00:58:47 -04:00
.gitignore Initial commit from Create Next App 2025-01-10 12:57:02 -05:00
eslint.config.mjs Initial commit from Create Next App 2025-01-10 12:57:02 -05:00
global.d.ts Added google anal 2025-01-17 19:52:56 -05:00
next.config.ts Initial commit from Create Next App 2025-01-10 12:57:02 -05:00
package-lock.json Announcement Page retooling, make it look better. 2025-01-23 01:43:36 -05:00
package.json Announcement Page retooling, make it look better. 2025-01-23 01:43:36 -05:00
postcss.config.mjs Initial commit from Create Next App 2025-01-10 12:57:02 -05:00
README.md Added releases changed the way apis work underneath to give more room for caching, i.e remove unneeded crap when it is unneeded 2025-01-21 00:43:14 -05:00
tailwind.config.ts Linting RULES AGAIN, and removing warning error for tailwind 2025-01-12 22:51:20 -05:00
tsconfig.json Initial commit from Create Next App 2025-01-10 12:57:02 -05:00

Put my baby in a docker and let it rip

Frontend of a headless CMS running Strapi in the back.

Will host all LLM translation and editing for Foreign Language Novels.

Check the main site: NullTranslation

Support us on Patreon: Null Translation Group

TODO

  • ADD MORE NOVEL SUPPORT
  • STANDARDIZE THE ERROR LOGS (it will be here till the end of days)
  • ADD ADS LATER (Added Analytics for ads and user tracking)
  • SCHEDULE POSTS FOR PATREON READAHEAD (Lets be real a chron is a real chron in the booty)
  • Releases Page for recent releases and schedule for releases (Needed so badly needed)
  • Annoucement page for announcements (Gotta tell the 5 users apparently we support audio soon ?)
  • AUDIO TM? TTS! TTS!! TTS!!! (I am not paying right ?)
  • NextJS data cache, DID SOMEONE SAY PAGINATION ?

Books Currently Supporting

  • 对弈江山 by 染夕遥 = "Fight of the Throne" by Ran Xiyao
  • 医手遮天 by 慕璎珞 = "Godly Talented Doctor" by Mu Yingluo
  • MANY MORE

This project acts as a learning experience for:

  • Dynamic Routing: Using NEXT.js dynamic router.
  • SSR vs CSR : Interesting experiment
  • SPA vs MPA : Also kindda fund tomess with.
  • Frontend for a Headless CMS: Powered by Strapi, at first kindda rough, now very easy to understand why CMS exists.
  • NEXTJS DATA CACHE: 2mb ? what i that for ants ? pagination here we come

Conclusion

Somehow, dealing with Java Spring Boot nightmares feels easier than this. In the end, using the API directly for uploading data seemed more efficient for my needs, rather than relying on the CMS interface.

Perhaps CMS is more useful for building websites for customers with little to no CS experience. For personal use, however, it currently feels unnecessary.

That said, CMS might become more useful later if the project grows. Features like shopping tiers and authentication could be easier to implement using a CMS framework.

Okay, CMS is god—we believe in CMS now.

Polish for the site will come when/if any of the novels gain significant traffic. For now, we'll keep iterating!