I can't over-emphasize this enough for folks at the earliest stage of building your SaaS. Put the application on a subdomain like app.your-product[dot]com and have your main .com be an easy to use CMS marketing site like Wordpress or Webflow. So annoying to unwind after the fact.
-
-
After scratchwriting a CMS for my first software business I told clients "Every software company should have their own CMS; it's just too useful not to do, and once you have it you can bolt everything in." 80% of the effort wasted... but that last 20% could be half the business.
-
Webflow might 80/20 this now
End of conversation
New conversation -
-
-
WordPress can already be used in headless mode. Use it for admin, then use the API to generate a static site and deploy to
@Netlify. This is how@OurWorldInData does it, works pretty well -
I have a site that's processing 250k/mo in orders and it's main data source is Airtable
End of conversation
New conversation -
-
-
I finally saw benefit of a subdomain too late (this week!!), and just yesterday built automation to “render-the-content” exported from Webflow (+upload static files). “git push” still required for now (+URL map for new pages) but no other “coding”. Experiment—TBD if this is wise!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
WP has a json api.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We just did this using Sanity on our new company site. Custom components let us build cool stuff, but anyone can add pages in the CMS
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.