I’m sure there are enough qualified people available to help, but it’s Yourhead who makes the decision on who to ask, how to help and what to do (and how/what not). I don’t know his plan or roadmap, nor level of delegation while feeling comfortable with it. Plus it requires quite some organization. Usually companies grow into it, organically. This too is an iron triangle… The current situation is quite disruptive or better said—when taking control: creative destruction.
1 Like
Exactly.
Understood @Konfuzzious and @Jannis I
that it’s Yourhead’s decision how to run their business and I’ll keep my opinions and observations to myself in future.
No, that wasn’t my intention. Sorry if I sounded offensive. Keep your feedback coming please.
I just wanted to say that we developers are trying to help Isaiah already, but it’s his decision how we are actually integrated in his plans.
We already suggested to create a marketplace, but we aren’t there yet…
2 Likes
Not my intention either, Paul. It’s more some kind of my conclusion on where we stand and what I believe to be possible actions to take.
1 Like
@Konfuzzious and @Jannis, my apologies, I took it the original comment the wrong way.
Sorry not a good day.
2 Likes
I totally respect the opinions shared here. Really. However, I’m really not interested in a Blocs review on a Stacks Pro website.
I started this thread because I am concerned that a piece of technology that has been around for a long time may become irreparably harmed. I have been using Stacks since a late release of Version 1. A really long time. Last spring was a very sad season. I really don’t want that to happen to Stacks.
I’m simply pointing out what I consider to be the obvious. I am powerless to do anything about it at this point as I am no longer an integral part of the community. I am hoping those that are will step up with support for those floundering. I have confidence that when StacksPro is ready to be released it will be. Until then I just don’t want the pieces to fall apart.
4 Likes
I get it. :-) Could I ask you to start a new thread on that topic?
My hope is that somewhere down the thread we will see some good solutions for support showing up. I would rather people not have to read through reviews for a competitor to get there. It’s nothing against Blocs, Pinegrow, Wordpress or any of the rest.
Let’s hope that 2023 brings some answers and stability.
5 Likes
Good news. Isaiah posted the following on the Stacks Discord channel yesterday:
Happy new year everyone!
Can you believe it’s 2023 already?
I just wanted to drop a little message here and tell everyone in the Stacks community that 2023 is going to be a big year for us. We have so much fun stuff planned.
I know I’ve been a bit quiet here lately, because after releasing that last update to the Stacks plug-in I’ve been head-down in development mode working on Stacks Pro again.
Things are looking good for a new developer release soon and then it’s full steam ahead to Stacks Pro.
Of course, I’m always thinking 3 steps ahead too – so Stacks Pro isn’t the only thing I have in the works – there will be new APIs for developers to play with, new websites for more info, and lots more goodies too.
So get ready, this is probably going to be the biggest Stacks year ever.
Isaiah
17 Likes
Novelty?
I wouldn’t want to start a new project in RW and then redo all the work in Stacks Pro.
Stacks Pro wiill open RW project files so no worries there.
I’m only concerned about the code, the js that I add by hand in the pages, the settings, the upload…
let’s hope that already from the first versions it converts everything well.
I’m pretty confident that all will work OK.
There is nothing to stop you working in whatever version of RW that you are using now. It is only the yet to be released Rapidweaver Elements that is planned not to work with Stacks from Yourhead.
RW 8, RW Classic and RW Classic 9 will I believe continue to work with Stacks. It just depends on if you have a subscription model and continue to pay that subscription for updates.
I will continue to use RW 8.9.3 until the Stacks App is released, then I’ll give the App a go,
1 Like
Nearly 6 months on is there a Stacks App update?
Work in progress. No rush really, as all current versions of RW are still working OK. It will be well worth the wait.
1 Like
I disagree. An update is overdue. Even as just a courtesy to the community. When the split happen Isaiah got a lot of public support. Given the amount of time that has elapsed I think it’s only fair that those supporters get even the tiniest of updates, opposed to total radio silence.
Of course, there might have been news on his discord thing, but I’m over 14 years old, so don’t use it ;-)
11 Likes
I can understand the concern but I’m very happy to wait. I’d rather be sure that Stacks Pro is fully compatible with current stacks, and current RW/Stacks documents, than have something glitchy early. A long and thorough beta programme works for me (but please make sure all stacks developers are in the beta, so that we can test our products).
You are confusing the request for an update, with the release of the product. Or at least that’s how your comment reads to me.
We don’t even know if it’s still in development. For all most people know, it’s not. I suspect most outside the more “hardcore” RW community have long since forgotton about it, and are eagerly awaiting RW Elements.
2 Likes
So that 90% of your stacks in your project no longer work 🤣