Earlier quoted context omitted.
Yes, but there are also a lot of people who don’t. I still use an RSS reader and basically every six months, a blog that I followed 5 years back and went dark will get taken over by spammers because no one was paying attention to it anymore.
I can’t imagine what this has to do with the White House’s website.
Whitehouse.gov Chooses WordPress, Again
321–330 of 371 posts
Re: Whitehouse.gov Chooses WordPress, Again
#322Earlier quoted context omitted.
> it does not work with a git centric development flow, which any modern dev will insist on. Yes, it does. Just use Trellis and Bedrock.
I am not familiar with them, but a quick Google seems to suggest they won’t work with WPEngine, Wordpress.com, etc. In any event, they’re bolt on solutions, but the core of Wordpress is still a mess of configuration split between files on disk and the database. There is nothing so valuable about Wordpress that you couldn’t just get a more reliable solution from scratch than by bolting more stuff onto WP. I’ve heard p…
I don't think even the admin UI is well organised or consistent though. Most users just know how to create and edit posts. Once you start installing a few required plugins too, the UI becomes even more a mess of controls that users are scared to touch.
Re: Whitehouse.gov Chooses WordPress, Again
#323Earlier quoted context omitted.
50RPS must be tuned or cached in some way, as the memory load for 50 requests to the full app should overwhelm the 1GB server and ~50-100ms is typical and the $5 instance has one core.
No tuning. I just installed WP, nginx, and MariaDB. Here are the numbers from when I was testing how much comment threads impacts load time: http://imgur.com/gallery/IQk2kun
Re: Whitehouse.gov Chooses WordPress, Again
#324What are the best alternatives these days to WordPress for non-technical people? I know of Squarespace and Webflow. Any others?
For non-technical people, Wordpress is a mess as it relies on clumsy plugins for WISIWIGish editing. From my research, it seems like there are three top CMS for non-techies: Squarespace, Wix and Weebly. I compared Wix and Squarespace primarily and went with Wix because Squarespace has no backup/restore capability. I'd consider backup to be essential for non tech users.
At all? Even if you contact support because you accidentally deleted a lot of stuff?
Re: Whitehouse.gov Chooses WordPress, Again
#325I hope we again see the value of using systems like Wordpress for it’s simplicity in getting a blog/website setup and easily modify content. Lately most of the modern marketing websites I see is built using gatsby and next.js. Having been talking to different content/marketing teams, they hate it so much because of the complexity it brings. Editing content? Sign in to this headless CRM app, want a form? Go sign in to…
Simplicity? Perhaps in its use, but not the code. The code and hosting requirements are, frankly, Frankenstein's monster levels of frightening. ~~You have to~~ WP expect you to install it such that it can modify its install folders - all of them. Security-fucking-nightmare. It will use incoming requests to trigger "cron" jobs (which can include self-upgrades), via a non-loopback HTTP request. It falls apart under any…
However that is not fault of the tool itself. There is nothing preventing a competent dev or small team to set up staging and qa environments, a ci pipeline if they are so inclined, write proper tests, be discriminating in the plugins they install and the quality of code they write. And the start threshold for the system is incredibly low, the fact that so much boilerplate functionality is _already there_ saves a lot on development costs and allows you to focus on functionality that really matters.
TL;DR if your wp installation is bad, it's not wordpress, it's you.
Re: Whitehouse.gov Chooses WordPress, Again
#326What are the best alternatives these days to WordPress for non-technical people? I know of Squarespace and Webflow. Any others?
The development experience means I love it too. I never did find a simple Wordpress workflow for managing staging and live sites in git. With Wagtail/Django keeping the configuration in code, a git workflow works.
Edit: Apologies if you were actually asking about a solution to allow non-technical people to create a site, rather than manage it.
Re: Whitehouse.gov Chooses WordPress, Again
#327Earlier quoted context omitted.
> just a single file zipped up or scp'd And now your page displays a white page. Error in the log is an exception with no stacktrace/location. This was my experience in production a few times. It's a fun system if it works, but without a testing pipeline and a staging environment it's a lottery with a possible mystery breakage on every update/change.
If your log only shows an exception without any kind of stack trace or location, I’m sorry but Wordpress is not the problem.
Re: Whitehouse.gov Chooses WordPress, Again
#328Earlier quoted context omitted.
I was surprised that the accessibility widget on the current website has a feature called “high contrast mode” that does not significantly increase the contrast ratio between the primary text and the background. It also significantly lowers the contrast between the secondary text and the background, sometimes as low as 2.1 (7 is the recommended minimum). Given the icon they chose, it seems like “dark mode” would be a…
A data point to support your claim: The main body text becomes white on dark grey with a contrast ratio of 14.22, compared to the original dark blue text on white background with a contrast ratio of 14.93.
Re: Whitehouse.gov Chooses WordPress, Again
#329Earlier quoted context omitted.
The NFS requirement for multiple Wordpress hosts are an instant deal breaker for me when discussing CMS on the cloud. Wordpress made sense when the web was a collection of independent servers. However in today’s cloud-orientated hosting landscape there are a thousand better ways to provide said content. Both at the beginner level and at the enterprise.
There are plenty of ways of doing it without NFS.
Often the “loads of ways” on WP require changing its normal behaviour and thus breaks ones ability to use the admin console. Or use some other kludge that might suit some subset of people some of the time. But ultimately it keeps coming back to kludges or other workarounds that introduce as many caveats as they solve.
Re: Whitehouse.gov Chooses WordPress, Again
#330Earlier quoted context omitted.
The NFS requirement for multiple Wordpress hosts are an instant deal breaker for me when discussing CMS on the cloud. Wordpress made sense when the web was a collection of independent servers. However in today’s cloud-orientated hosting landscape there are a thousand better ways to provide said content. Both at the beginner level and at the enterprise.
NFS for sharing uploads folder? shift the media to a CDN when it’s uploaded and serve it from there. There are multiple plugins that do this.