Regardless of what is being said, I’m being a realist and moving forward on the basis that standalone Stacks is not going to happen anytime in the far-off future. I realise many will disagree and tell me otherwise, but there comes a time when you have to accept what is actually happening, not what is being said.
So, time to find an alternative. Elements is an obvious move, but… I dunno, track-history is not great there. Who knows what twists and turns it’ll take over the next decade? And while I don’t expect cheap, it’s pretty pricey for something in a diminishing sector (website builders in general).
I could go all-in with AI, but I’m really not sure how much real control you have over things. I’ve built a few really nice scripts with it now; an ecommerce solution, a blogging platform and a comments system. But I’m not really sure it’s yet the answer to a full-blown website where i have total design control. Love to hear from anyone using it for this, though… Prove me wrong!
And so I land at Pinegrow’s door. Tav made me buy a copy and try it out about five years ago (well, OK, maybe not “made me”). I got on OK with it, but got lazy and went back to RW. But it certainly seems to be the best option around now.
Anyone using it?
I’m thinking to stick with Bootstrap 5, and make full use of the off-the-shelf components you get with it, plus make new ones for my particular requirements using AI.
The only thing I’m finding it hard to comprehend not having access to is Poster 2. @Jannis gonna make a version of it that’ll work with Pinegrow?
Anyway, enough, waffle… In short, anyone moved from RW to Pinegrow? If so, how you getting on?
These were tests, and they worked very well. The import with TCMS 3 was smooth, and the documentation integrated into TCMS 3 allowed me to automate the integration between the Pinegrow template and TCMS 3 using Cursor, which saved me a long day of editing Twig.
I think that, in fact, you can absolutely achieve the same result with other tools besides Pinegrow using TCMS 3. I’m not sure if I’m answering the question you were asking.
Not sure if this is for me, but I have my own CMS solution.
Nah, that’s definitely not a route I want to go. Thanks though.
It’s not a deal breaker for me. Just going back to writing text as code, not a biggie. Besides, a lot of the text content will be added using my CMS solution, and that supports markdown, so it’s still there if I want to make the content editable in the browser.
