Publii: Open-source local WYSIWYG static site CMS

1

Zim Wiki

#WiKi #Note Taking #Task Management 115 social mentions

2

Sitecake

I think that user experience of website builders with wysiwyg and drag and drop UX won over time. Then, as time passed by, website builders become bloated and complex. Once again you needed a professional to maintain your site in site builder. So now simple solutions, static HTML, free or one-time fee CMSs are sexy again. (economy is not good, who wants another subscription?) I know because 14 years ago we have created static, drag and drop CMS that people still buy today. People value basic features. And it's hard to make a complex software that's easy to use. Basic features are still enough, after 14 years. https://sitecake.com.

#CMS #Blogging Platform #Blogging 5 social mentions

3

Pinegrow

I always preferred it that way myself. Used netobjects Fusion for years and many sites. From what I remember, the push for html5 and super lean / clean / and 'validating code' for google search results made it difficult for the older tools to stay in favor. Also the move to mobile.. And not just "m.site" - making so javacript / bootstrap type things came to be favored for a while (lack of grid / flex in browsers at the time) - which mostly required text editors instead of wysiwyg. The business models for investing in software were shaping cloud things around that time (some say for better, I say for worse) - so webflow, wordpress, adobe cloud everything, and similar had a chance to do the things that stand alone download and own software could of been doing. Faster internet being more prevalent and such of course helped with these things. I've been itching to spend a couple hours testing pinegrow site building ( https://pinegrow.com ) to see if it is reminiscent of the netobjects days.. And now that wordpress is getting increasingly painful to use and maintain, I'll likely get to that sooner than later.

#Website Design #CMS #Website Builder 24 social mentions