![]() I used to renew my Pinegrow subscription, but stopped, becasue I found it to be not as productive and quick to create a site, as using Stacks with Source (CSS Grid). Most Weavers would be stumped with it and not be prepared to invest enough time in it, IMHO. There are several regular users here who would highly recommend Pinegrow, but only for those with the abillity to use and understand it. Do you have a link to share what you created? I’m happy not to have to faff with managing stacks and knowing I have a fixed annual cost without needing to shell out for other frameworks and features, although I appreciate that this would be necessary if I needed a CMS.Ĭongratulations. Pinegrow is similarly priced to the new RW pricing, but comes with everything you need to build professional sites. I’m very happy with the result and am now in the process of converting all my sites. I can also create my own reusable components. You can build the whole site without the need to code, although coding knowledge (html/css) is helpful. The bootstrap components and blocks are drag and drop pretty much like stacks. Pinegrow’s interface takes a bit of getting used to but allows you to change just about anything. The site is extremely fast loading and comes through clean with the html validator which none of my RW stacks sites do. I’ve managed to build the complete site with Bootstrap in Pinegrow. ![]() Now that I have successfully converted my first site from RW to Pinegrow, I thought I’d share my experience in case anyone else is thinking of making the move. I decided to move to Pinegrow when all this kicked off. So for now, you can still use RW and stacks and continue to built/update your sites and decide later if you continue with RW classic, use the new Stacks App or use RW Elements. This version works with all stacks and will be a competitor to RW. Isaiah will offer a complete independent app based around Stacks sometime later. The new forum is available at: RapidWeaver Forum | Learn How To Build Better Websites | RapidWeaver Forum What you see in the App store is not an upgrade price, but the price for the latest version if you buy it new. So you can still use this one with Stacks. This version will be supported in the future as well. ![]() So it looks like this upcoming version of RW will not support Stacks or Stacks will not support this upcoming version of RW.įor all the Stacks users, there is version of RW which does work with the stacks plugin. Of course this is a competition to Stacks. A drag and drop interface for elements like images, etc. ![]() This leads to a RW version which will support Elements. RW decided they need a more user friendly way of creating websites. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |