Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Whitehouse.gov Chooses WordPress, Again

pagely.com

Post reply on HN
Print view View original

181–190 of 371 posts

Re: Whitehouse.gov Chooses WordPress, Again

#181

Post by vxNsr »

centimeter wrote: post #162
imwally wrote: post #62

I was curious after seeing the accessibility statement what the previous administration's had. https://www.whitehouse.gov/accessibility/ https://obamawhitehouse.archives.gov/accessibility https://georgewbush-whitehouse.archives.gov/accessibility.ht... https://trumpwhitehouse.archives.gov/accessibility With that last one not being surprising at all.

What is the point of this page besides signaling? It seems completely useless from an informational standpoint.

Ah but to a certain audience that’s all that matters. Follow through and actions are meaningless, it’s what someone appears to say that matters.

Re: Whitehouse.gov Chooses WordPress, Again

#182

Post by ksenzee »

Angostura wrote: post #16
steviedotboston wrote: post #3

> Political affiliations aside, I think we can all breathe a bit easier today knowing they didn’t choose Drupal. Strongly disagree. Drupal is a great CMS and there's a reason the government uses it so extensively.

I'm pretty sure the Obama administration used Drupal 6. Current Drupal is rather a different beast

The Obama-era whitehouse.gov was Drupal 7.

Re: Whitehouse.gov Chooses WordPress, Again

#183

Post by wvenable »

jaza wrote: post #115
steviedotboston wrote: post #3

> Political affiliations aside, I think we can all breathe a bit easier today knowing they didn’t choose Drupal. Strongly disagree. Drupal is a great CMS and there's a reason the government uses it so extensively.

I was a Drupal dev for ~10 years. Once upon a time, I built many sites with it, and I recommended it to many folks. Despite its flaws (and it always had flaws), it was a great piece of software in its heyday, and it had (and still has?) an amazing community. I'd still choose it over WordPress any day. But the days when I'd recommend either of them (or indeed anything in PHP) are long gone. Your best bet now is probab…

Does no one else ever have users want to setup content to go live at specific dates and times?

Static site generators are great for truly static content but that's extremely rare anywhere where content is frequently edited.

Re: Whitehouse.gov Chooses WordPress, Again

#184

Post by [deleted] »

imwally wrote: post #62

I was curious after seeing the accessibility statement what the previous administration's had. https://www.whitehouse.gov/accessibility/ https://obamawhitehouse.archives.gov/accessibility https://georgewbush-whitehouse.archives.gov/accessibility.ht... https://trumpwhitehouse.archives.gov/accessibility With that last one not being surprising at all.

[deleted]

Re: Whitehouse.gov Chooses WordPress, Again

#185

Post by ozorOzora »

hardwaresofton wrote: post #127
julianlam wrote: post #2

In this age where the trend is JAM stack, it is refreshing to see that something battle-tested like WordPress was chosen. There's a reason WP has withstood the test of time. (WordPress developers being a dime a dozen also help make the case)

I think if WP ever finds a way to do two things: - continuously serialize WP to static files - Make it easier to work with Wordpress as a CRM (No Code or at the very least don't force developers to touch PHP) JAM stack would near instantly cease to make any business sense (though developers would still love using it of course). A lot of the issues with Wordpress are sort of long-tail -- combinations of plugins exposi…

Or you can just roll with JAMstack as it's literally about what you're asking for.

Re: Whitehouse.gov Chooses WordPress, Again

#186

Post by nsomaru »

trog wrote: post #176
kijin wrote: post #122

Earlier quoted context omitted.

Hopefully the White House has access to someone who knows how to set up WordPress without shooting themselves in the foot. The fact that WordPress.com doens't get hacked all the time means that there are definitely people who know how to do it.

> The fact that WordPress.com doens't get hacked all the time means that there are definitely people who know how to do it. Regular reminder that wordpress.com is a different software product to wordpress.org :) wordpress.com runs their (relatively) newer JavaScript-based stack; wordpress.org (which is what we're talking about here, unless I misread the article referenced here completely) is the LAMP stack version.

Unless the new Wordpress is written in node, comparing the new “JavaScript” stack with the old “LAMP” stack makes no sense to me. Those technologies do not serve the same purpose.

Re: Whitehouse.gov Chooses WordPress, Again

#187

Post by ozorOzora »

wvenable wrote: post #183
jaza wrote: post #115

Earlier quoted context omitted.

I was a Drupal dev for ~10 years. Once upon a time, I built many sites with it, and I recommended it to many folks. Despite its flaws (and it always had flaws), it was a great piece of software in its heyday, and it had (and still has?) an amazing community. I'd still choose it over WordPress any day. But the days when I'd recommend either of them (or indeed anything in PHP) are long gone. Your best bet now is probab…

Does no one else ever have users want to setup content to go live at specific dates and times? Static site generators are great for truly static content but that's extremely rare anywhere where content is frequently edited.

IMO this is the single most relevant issue with static generators. Hopefully it will be adressed soon.

Re: Whitehouse.gov Chooses WordPress, Again

#188

Post by modernerd »

monoideism wrote: post #89

The one thing great about WordPress is the massive number of themes available (and plugins, if you're not a programmer). I wish very much that there were 10% as many attractive themes available for static sites. Yes, you can port them, but it's a pain. And yes, you can design them, but it takes more time and most programmers don't have the design chops to pull it off.

Do you think there’s a market for high quality paid themes for static site generators like Hugo?

Re: Whitehouse.gov Chooses WordPress, Again

#190

Post by daniellarusso »

trog wrote: post #101
splatzone wrote: post #79

Earlier quoted context omitted.

WordPress is not without its design flaws, some of which make sense from the point of view of helping non-techies run their own sites (such as making updates easy.) But as someone who has built 100s of sites with WordPress I feel the need to defend it on a few points here: > You have to let it modify its install. Security-fucking-nightmare. You don't have to do this, you can set up sane permissions and use the wp cli…

> You don't have to do this, you can set up sane permissions and use the wp cli[0] tool to install updates manually. I prefer to version sites with git and install updates locally, then git pull down on to the live server. Curious as to how you manage WP with git, particularly around when new files are added by core/plugin updates, which I've always found a bit of a hassle to deal with?

Check out the roots.io project for some software development ‘best practices’ as applied to Wordpress for development and deployment.
Post reply on HN