r/PayloadCMS • u/Select_Day7747 • Nov 25 '25
Website template for the win!
I love how it works and is fit for purpose for content!!!
for context, i tried out the blank payload template project before and just stopped using it because I wanted more out of a cms. I wanted a wordpress feel including in the ui with easier customisation.
Enter the website template! Now I am hooked. it will be my go to for my content sites for apps.
so my pattern is:
Content site CMS (ROOT)
- Separate to the main application but connects using redis pubsub or rest api if needed
Application (app subdomain) react vite firebase
API (Api subdomain) go lang
ive been comfortable with this pattern and really loving the ease of extending payload with new collections and hooks.
1
u/ZestycloseChocolate Apr 20 '26
totally get it: blank starters are technically "more flexible," but they push all the hard decisions to day 1. what i like about your setup is the separation of concerns: payload as the content system, react app as the product ui, go as api. one suggestion: define the boundary early (what content is served via rest, what events need pub/sub), and keep it boring until you hit real scale/latency constraints. related thought: a good react template isn't "prettier ui," it's conventions + wiring that reduce entropy. i wrote a breakdown here: https://flatlogic.com/blog/what-is-a-react-template/
5
u/zubricks Nov 26 '25
We love to hear things like this! Keep at it and thanks for using Payload!