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

WordPress 5.0: A Gutenberg FAQ

ma.tt

Post reply on HN
Print view View original

131–140 of 146 posts

Re: WordPress 5.0: A Gutenberg FAQ

#131

Post by chiefalchemist »

chc wrote: post #51
pmlnr wrote: post #16

Earlier quoted context omitted.

There's a difference when there are multiple contributors, as such with the linux kernel; in that case, the power is not with one single entity.

WordPress also has multiple contributors — it's just mostly under the control of Automattic, just like React is Facebook, TypeScript is Microsoft, and Go is Google.

I think the difference is the latter three had internal projects the OSS'ed them. On the other hand, WordPress was built on the back of a "community." There is a lot of distrust, and rightfully so, from how Automattic put itself first and the WP community a distant third.

Re: WordPress 5.0: A Gutenberg FAQ

#132

Post by chiefalchemist »

photomatt wrote: post #33
dpau wrote: post #22

Earlier quoted context omitted.

I used to help artists with setting up Wordpress portfolio sites. But the constant maintenance required (updating Wordpress & plugins, making sure that all plugins are secure and maintained, and checking after each update to make sure nothing was broken), as well as the rise of platforms like Squarespace, Wix & Weebly, means that I no longer recommend Wordpress for those types of clients. Artists just want to show an…

Check out Jetpack, it can auto-update all your plugins, and has a "Rewind" feature with real-time backups so you can one-click take your site back to a previous state if anything didn't work.

Hi Matt. Maybe not assume everyone here knows who you are? And instead at some point make note of the bias in your recommendation?

HN =/= WordCamp etc.

Tia :)

Re: WordPress 5.0: A Gutenberg FAQ

#133

Post by sxp62000 »

dpau wrote: post #22
joekrill wrote: post #15

Earlier quoted context omitted.

You're absolutely right. The big issue (for me, at least), is that it's a security nightmare. At least last I used it. It seemed there were security exploits popping up every day. Either from the core codebase, or from some random plugin everyone seemed to be using. I think that was just the nature of how their plugin system works? I'm not sure if anything's changed, but _maintaining_ a WordPress install is not fun a…

I used to help artists with setting up Wordpress portfolio sites. But the constant maintenance required (updating Wordpress & plugins, making sure that all plugins are secure and maintained, and checking after each update to make sure nothing was broken), as well as the rise of platforms like Squarespace, Wix & Weebly, means that I no longer recommend Wordpress for those types of clients. Artists just want to show an…

The only way to ensure your wordpress sites don't break is to reduce reliance on plugins. A decent host like DigitalOcean doesn't hurt either. Squarespace is ok for simple sites, but once clients start requesting additional features it becomes a nightmare.

Re: WordPress 5.0: A Gutenberg FAQ

#134

Post by skrowl »

tonyb wrote: post #128
joekrill wrote: post #15

Earlier quoted context omitted.

You're absolutely right. The big issue (for me, at least), is that it's a security nightmare. At least last I used it. It seemed there were security exploits popping up every day. Either from the core codebase, or from some random plugin everyone seemed to be using. I think that was just the nature of how their plugin system works? I'm not sure if anything's changed, but _maintaining_ a WordPress install is not fun a…

I used to do sysadmin work as a web hosting company and security nightmare is exactly the phrase I think of when I think of WordPress. Many mom and pop type businesses find the lowest cost web designer they can find to build them a WordPress site then get upset with the hosting company when "the server gets hacked" and their site is redirecting to a malicious site. WordPress is certainly a powerful platform but the f…

Don't forget about the 'low cost web design' market. If you're buying a web design for south of $500, you're PROBABLY getting a WordPress next next finish install with a default template and some minor tweaking.

I've screened / interviewed so many jr web "developers" who don't actually know how to develop a web app and they claim that installing WordPress plugins is development experience.

Re: WordPress 5.0: A Gutenberg FAQ

#135

Post by usaphp »

knowsmorsecode wrote: post #100
usaphp wrote: post #63

Earlier quoted context omitted.

Have you tried managing it using https://managewp.com ? I was in your shoes and it saved me a lot of headache

So you allow managewp to login to your sites?

It uses official WordPress Rest API: https://developer.wordpress.org/rest-api/

Re: WordPress 5.0: A Gutenberg FAQ

#136

Post by adevx »

andybak wrote: post #115
adevx wrote: post #27

I know this is not for everyone, but sometimes it makes sense to jump off the CMS bandwagon and build a custom site. First I used Drupal but got tired of rewriting the site on every major release and jumped on WordPress. Then on WordPress I realized I could not create the user experience I was after without committing massive amounts of time and resources in custom plugins/themes. Leaving me too dependent on a moving…

Apples and oranges. If you needed a comprehensive client accessible CMS then how did you replicate that side of things in Node etc? If you didn't need a CMS then I'm not sure why you were using Drupal/Wordpress in the first place. The only reason I can think to use them is if you want to hand off content editing to a non-developer.

I agree that I did not replicate the theme and plugin system of WordPress. But the beauty is that you probably don't have to. WordPress has to cater to all, which is probably the source of all the issues people face.

But neither is my website a simple brochure site. Members create their own content, upload photos, enter their location on a map, enter available dates, have the ability to chat with other members. When I tried to do al this with custom and available plugins, it never felt as a coherent experience. Then there is a lot of automation in the background, notifying members of unanswered messages, expiring profiles, notifying members of expiring memberships. Getting all this properly done with the CMS provided API's is more work then writing it from scratch yourself. With the benefit of not having to worry about CMS API deprecation.

Re: WordPress 5.0: A Gutenberg FAQ

#137

Post by tasuki »

lucideer wrote: post #86
GeneralMaximus wrote: post #14

I know a lot of people dislike PHP and WordPress, but I haven't found _anything_ that comes close to it in terms of sheer extensibility and plugin ecosystem. There's a plugin for pretty much anything you might want to do with a platform. I even moved my personal Jekyll-powered blog to WordPress a few years ago. My favorite thing about WordPress is that it's a known quantity. There's an easy to follow tutorial teachin…

> I know a lot of people dislike PHP and WordPress, but I haven't found _anything_ that comes close to it in terms of sheer extensibility and plugin ecosystem You're right about everything there except one word: "extensibility". Wordpress has a comprehensive hooks system that makes it seem like it's very extensible, but that's only there to make up for the godawful mess that is the codebase itself. PHP (which is a fi…

> PHP (which is a fine language

No it isn't. The language itself is awful. The PHP ecosystem is great though: easy deployments, good dependency management, healthy community, and the most pleasant framework I've ever worked with - Symfony.

Re: WordPress 5.0: A Gutenberg FAQ

#138

Post by indysigners »

leonk wrote: post #41

No mention here about Gutenberg's lack of support for accessibility standards. They pretty much went full steam ahead and left the accessibility team behind. See: https://rianrietveld.com/2018/10/09/i-have-resigned-the-word...

I also found it pretty shocking to learn (https://www.smashingmagazine.com/2018/12/gutenberg-accessibi...) that @photomat did hold a potential professional engagement hostage over Marcy Sutton’s personal blog decision... although he seemingly did reverse that, but still, the whole attitude is fairly disturbing in doesn’t help where there already are lots of emotions involved.

Re: WordPress 5.0: A Gutenberg FAQ

#139

Post by fujipadam »

AustinG08 wrote: post #29
joekrill wrote: post #15

Earlier quoted context omitted.

You're absolutely right. The big issue (for me, at least), is that it's a security nightmare. At least last I used it. It seemed there were security exploits popping up every day. Either from the core codebase, or from some random plugin everyone seemed to be using. I think that was just the nature of how their plugin system works? I'm not sure if anything's changed, but _maintaining_ a WordPress install is not fun a…

My answer to this problem has been the plugin Wordfence. It's primary feature is a WAF whose rules update continuously and intercepts every request. Having worked at several agencies I've seen and inherited many hacked sites. I have never had a site be infected with a clean install using Wordfence. knocks on wood

I use Wordfence and always thought it was good. But good to know that a lot of others find value in it too. Btw, looks like wordfence is getting killed with all the traffic from HN. Hopefully the increased sales will make it up to them :)

Re: WordPress 5.0: A Gutenberg FAQ

#140

Post by dpkonofa »

sparkzilla wrote: post #101
dpkonofa wrote: post #78

Earlier quoted context omitted.

I hate to start this off this way but this comment makes me feel like you're either a very novice WP user or simply a designer that likes to advertise themselves as a dev but doesn't actually do a lot of coding. Divi and Visual Composer are both absolute messes from every aspect except for ease of use and they're incredibly bloated even for simple page layouts. Everything ends up as an inline style, the actual load t…

The whole point of WordPress is that you don't need to do much coding, so that point is moot. The vast majority of WordPress developers are designers or non-technical people who either don't know how to code, or who can hack a bit of code now and then. When I make a site for a client I have to balance many options 1) how fast can I do it 2) including how many bits and bobs do I have to add in to even make it work 3)…

>The vast majority of WordPress developers are designers or non-technical people who either don't know how to code, or who can hack a bit of code now and then.

That's what I thought. There's a reason why WordPress has a reputation for being insanely insecure and a terrible platform and it mostly has to do with the fact that it's made things easy for people who have no idea what they're doing. Existing page builders allow you to make something easily while completely ignoring the affect of page load times, proper syntactic code, and quality. They're meant for people who don't invest the time to actually learn what they're doing so they can throw crap together that they can charge clients who don't know any better.

Post reply on HN