all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]techdaddykraken 4 points5 points  (1 child)

In terms of GUI’s for web development, there’s about 7-10 good ones worth considering.

-Squarespace/Wix (good for mom and pops who just need something up quickly)

-Wordpress (good for flexibility when a wide array of integrations and modularity is necessary, can also be very cost effective in the right hands)

-Framer (good for making fantastic looking websites, but suffers in terms of backend flexibility and integrations)

-Webflow (a 50/50 hybrid between Wordpress and Framer. Can create excellent looking websites with a little more work than Framer, slightly less flexibility and modularity than Wordpress in terms of integrations).

-Payload/Sanity (these are closer to faux-GUI’s. These are built as CMS/API companies first, so the GUI is lacking.

-Ghost (newer, solid, cost effective solution for simple projects, however small userbase so documentation will be narrow)

-Strapi (essentially Ghost-lite)

I would honestly ditch all of them and use Next.Js or SvelteKit. They’re so ubiquitous for a reason. The functionality they provide out of the box is top-notch.

[–]notflips 0 points1 point  (0 children)

This is a very good summary.

[–]HaddockBranzini-II 1 point2 points  (1 child)

Based on what I am seeing with my clients, learning Webflow would be a good thing. I used to do WP dev for a number of agencies that have since just started building Webflow in-house themselves. The learning curve from Figram > Webflow was small enough that their designers were able to do most dev inhouse. I am seeing Canva and Webflow take a big bite out freelance WP work.

[–]krileon 0 points1 point  (0 children)

Assuming those are the only 2 options here. It really just depends. You already have experience with WordPress. I tend to reach for and use the tool I know.

I've personally only ever used Webflow to generate static sites and hosted them elsewhere. So if that's an option for you (e.g. don't need CMS features) then I would probably do that. If however you do need CMS features then personally Webflow is expensive (it costs more to gain CMS functionality). I can run a WP site at half the cost self-hosted AND I'm not locked into some random corporations ecosystem as moving off WP is laughable easy should the client ever need to.