https://getpublii.com/ Yet, anyone?
While they have a Github repo, it is incredibly annoying how it's almost impossible to find any documentation around deployment/hosting. Unless I missing an obvious page
WordPress Is in Trouble
61–70 of 457 posts
Re: WordPress Is in Trouble
#62Earlier quoted context omitted.
Surely non-psychoactive wine is just grape juice?
right, let’s try again: Did he drink THAT psychoactive wine?
Eight ball yoda says… bad trip sitter he did seek, hmm?
Re: WordPress Is in Trouble
#63Earlier quoted context omitted.
It's just a reminder how much "right place at the right time" plays into the phenomenon of ubiquity, from Wordpress to Harry Potter to Zoom to Javascript. There are countless efforts to make the next Wordpress out there, yet no combination of Scheme and Rust is going to make up for the critical missing ingredient of "right place at the right time".
This is the right time. Strike while the iron is hot. People are angry and concerned. Someone just needs to come forward with an attractive way to capitalize on the situation.
Ex-Wordpress users are just going to diffuse into all the other decent options that already exist. Or stick with a Wordpress fork that caters to them. Though note that Wordpress isn't going away. How many Wordpress users even know who Mullenweg is?
The idea of cobbling together yet another blog platform that will somehow capture these users better than Wordpress plus all the decent incumbents is some good ol fashioned developer hubris. :P
Re: WordPress Is in Trouble
#64Re: WordPress Is in Trouble
#65WordPress is a very mature project with a long legacy but I'm surprised that there hasn't been a larger profile attempt to make a spiritual successor to it that can shake the baggage of being PHP and the long history of vulns that have come along with it. I'm imagining some very pluggable and template driven runtime that you can ship very declarative packages for. The spicy take would be to use a Scheme for the templ…
Processwire OTOH is fantastic in this regard. Super small and generic core with minimal, close to non-existent attack surface, and a programmatic API that lets you solve custom functionality with a few calls to the content API instead of another plugin.
Leads to practically maintenance free sites.
Almost the security of a static site, with the flexibility and dynamic features of a proper cms.
After having the nightmare of maintaining a dozen WP and Drupal sites in the past, I can now just let the sites chug along for years without intervention.
Re: WordPress Is in Trouble
#66Earlier quoted context omitted.
Soon enough AI will write most of blog/marketing HTML.
And then we can develop systems that save user prompts, automatically and dynamically regenerating page content as the AI models are updated.
Slap some workflow/approval process.
And you have a product!
Re: WordPress Is in Trouble
#67This move by Matt to pull out of development all but guarantees a fork. The biggest argument against was the work that Automattic was putting into WordPress would be very hard to replicate in a new project. But if the community is going to be expected to do ~all of the work anyway, there's no reason to do that work inside Matt's personal fiefdom.
Re: WordPress Is in Trouble
#68WordPress is a very mature project with a long legacy but I'm surprised that there hasn't been a larger profile attempt to make a spiritual successor to it that can shake the baggage of being PHP and the long history of vulns that have come along with it. I'm imagining some very pluggable and template driven runtime that you can ship very declarative packages for. The spicy take would be to use a Scheme for the templ…
Plenty of people have made better CMSes, Wordpress is big because it got big, and a lot of people depend on it. And since an enormous number of people are involved with it, your upstart system will never have the capability of Wordpress. Whatever capability you come up with, somebody will have already made a horrible module to install on Wordpress to do it that after 10 years has become almost alright, or at least all of the flaws have been posted on messageboards and everybody knows how to work around them.
Wordpress isn't wordpress because it's good, it's wordpress because it was good enough at the time, and its competition was Drupal and Joomla (or something not PHP.) PHP baggage? PHP isn't PHP because it's good, it's PHP because of mod_php, and cheap hosts. To repeat, your choices: Wordpress, Joomla, Drupal, or figuring out how to run another language on your cheap host, or having to pay to upgrade your hosting account. By far the best option for most people was Wordpress.
If you want to compete with Wordpress, first get a time machine, then go back to that time and write something better in PHP.
Re: WordPress Is in Trouble
#69The problem is that there's a bit of a black hole in CMSs right now where you need developers who want to work on the CMS and ordinary users who can host/create content on the CMS. Strapi was almost there, but alas, headless is not going to cut it for your average business trying to make a website.
Static site generators can be too limited and simple, Drupal is not particularly user friendly, and tons of other CMSs don't have enough plugins for marketers to cram into their sites.
Anyone considering e-commerce now will probably use Shopify instead of WooCommerce. Site builders like Squarespace and Wix are good for simpler sites but not for multi-author news type sites.
I feel like the only option is a fork at this point.
Re: WordPress Is in Trouble
#70From his perspective, after everything he has done, others are getting the financial gains and many in the community turned on him and his company. It must be a horrible feeling.
I like to think of this as a "reverse" faustian bargain. By sticking to some agreed upon "moral" agreement of this open contribution and communal governance, you create a huge market that you get to try and least capture a piece of. If you break that bargin, you risk the project. And it isn't like this is some theoretical bit... it has been shown again and again in different communities.
I fundamentally don't understand how you can spend so long in open-source and think that this agreement doesn't apply to you. That may seem "cruel" in that someone else can profit from you... but that was always part of the bargain that made your business exist in the first place.