I need help. I have a WordPress website that needs an overhaul, and I have many things/features that I'm trying to create/manage. Do I:
- Commit to WordPress, lean into ACF, post types, etc
- Use WordPress for blogs/links, but use static for other stuff
- Migrate away from WordPress altogether
- Commit to WordPress, lean into ACF, post types, etc
- Use WordPress for blogs/links, but use static for other stuff
- Migrate away from WordPress altogether
Comments
https://github.com/lonekorean/wordpress-export-to-markdown
Without Gutenberg, obvs
Unrelated disclosure I do work at WooCommerce (WP ecomm software).
- It's already in place
- I like my workflow; it's proven to meet my needs generally
- Likely needs modernized/extended
- Some things/features (like book reviews) could be weaved into other post types (like blog posts)
- Leaves WordPress good parts in place
- Provides better flexibility for accomplishing other things/features
- Provides better design control
- But requires managing things across a splintered ecosystem
- Fresh start!
- Total control and reinvention
- WordPress is old
- Currently controversial
- BUT.
- Huge effort.
- Worried about things slipping through cracks (esp URLs)
- Lose current (good!) workflow; start anew
- Is new way better than the old?
That being said, if it ain’t broke…
#WordPress isn't going anywhere. Although there's nothing wrong in expanding knowledge but shifts can be a big undertaking. Keeping it at least some of your universe for 2025 seems logical. In the end it's about what time you have, your passion, and priorities. Good list though! 👍🏻
Do what sounds fun to you. Keep an archive of the WordPress site in case you decide it’s not fun later, but yeah. Do what sounds fun.
Otherwise, you’re *really* not going to want to do it. And, if you’re like me, you’ll keep putting it off.
Zero regrets.
Worth watching @bell.bz about overhauling his site:
https://www.youtube.com/watch?v=mGCN_n9qFj0&t=1250s
You’ll be surprised how easy it is to migrate your current content, and how easy it is to add new features, content types, micro sites, etc.
Everything else is 11ty powered
There's a plethora of articles from other CMS/users about easy ways to migrate after the whole controversy started.
Maybe try option number 3 on a less important, less complicated site. That way you get the fun and adventure of trying something new, without risk to your primary property.
Are the static things custom experiments?
Honestly all you needs is ACF and that fancy custom post type ui plugin
Add Timber to the mix to smooth out the rough edges working with page templates
https://upstatement.com/timber
- It pulls in data from multiple WP sites to aggregate
- Projects are a custom post type with ACF
- Astro, Tailwind, TS
https://github.com/adamfortuna/adamfortuna-astro
https://expressionengine.com
If it works for you, it'll be hard to beat - but I'll never use it again. The DB model, security holes, hosting, speed == deal breakers
Anyway- I moved on and love what I'm doing now. Svelte w/ scoped styles made writing CSS fun again.
I can embed components into the posts and it just works. I can jump around the project and work the way I want. Also, the git based work flow / deployment is too good.
Astro might be the best bet if you're blogging since it is markdown based- but I love my sveltekit for my blog :)
/rant