Human-Led, AI-Assisted Digital Services for Web, SEO, Reputation, Ads, and Growth.
GrowPep LLC is a human-led, AI-assisted digital service provider focused on web development, SEO, reputation management, paid advertising, social media management, and sustainable digital growth.
Markdown supported · ⌘↵ to post
One thing I kept coming back to: your "how will the system grow?" question assumes you can answer it. For an established business, sure. But for a brand-new project with no users yet, that's just a guess.
So maybe the earlier question isn't "which architecture fits my requirements" but "how much do I actually know about my requirements yet." If the answer is "not much," the simplest, cheapest-to-reverse option wins by default — not because it's technically better, but because you can't design for growth you haven't seen.
Curious if you think that's a real first step, or if it's actually fine to guess and adjust later.
Arqum Younus
the trade-offs list is the honest part, and “hosting for multiple systems” is easy to underestimate, since headless means a wordpress server plus a separate place for the front end. (cloudways team here, so biased) our launch announcement for velocity, our managed node.js hosting, mentions headless builds as one use: it supports next.js with git deploys, so an agency running wordpress with us can host the front end with the same vendor. it still adds moving parts, as you say. in your experience, is preview the hardest part to get right?