Live data from Hacker News

The Next WordPress

wsvincent.com

31–40 of 43 posts

Re: The Next WordPress

#31
> Lektor is file-based by default, so updating content does not require a cloud server at all but merely access to the root file itself, which can be stored on a service like Dropbox or Google Drive. A developer can use a local server to generate dynamic content and a full-featured site, but the CMS, which is currently a simple Mac app, simply updates the original file.

This. This would be something phenomenal. The problem with WordPress and services like it, is that they take your content, package them into something they can understand and hides them under their pillows.

Inverting the control, like what the OP says -- where the user owns the content, that can be plugged into layers like WordPress, looks like the path towards the future.

I made http://hexopress.com with a similar vision. It is not yet a full blown shape of what I have in mind, but it cuts the concept well.

Re: The Next WordPress

#32
post #26

First of all, Wordpress is known to fix security issues quickly and platforms with many developers have more eyes on the code so it's only natural that they have a LOT of reported vulnerabilities. This does not mean that it's "inherently" insecure. A static site can't enable... - User management (Members) - On-site-comments (That Search engines can find) - Voting (Polls & Ratings are very popular on Wordpress!) - Car…

> This does not mean that it's "inherently" insecure. It's a pretty strong indicator though.

This is completely wrong. The more eyes you have on something, the more hackers attacking something combined with more pen testers and coders working on it, the more secure it is.

You know what is insecure and makes for a great target..software developed by few people, updated infrequently by people who don't care. The exact opposite of WordPress.

Re: The Next WordPress

#33
Wordpress isn't just a thing that people use. It's a gravity well of humanity's non-technical web authoring aspirations; matter keeps accreting there in the form of plugins and feature additions. Escaping it at this point is going to be difficult for most people, similar to how sending satellites into orbit is infeasible for most small businesses.

Re: The Next WordPress

#34
I generally disagree with most of the arguments here, but the last part of this article makes a good point that the business owner (person buying website) usually doesn't make the decisions about the technology that gets used. This is especially true for SMBs (I'm excluding the DIY/hacker-types here).

I built a WordPress plugin inside of HubSpot called Leadin (it's now their HubSpot Marketing Free product). The idea was to build light weight marketing automation for Very Small Businesses. We started on WordPress because most small businesses use it. We incorrectly assumed in the beginning the business owners would be the decision makers on whether or not to use our product. We quickly found out it was usually the web development agency/consultant they worked with who would install it for them, then explain the value of the product. We eventually shifted our marketing to focus heavily on agencies which became our main acquisition source.

Agencies like to use WordPress because it's customizable enough to easily build what their clients need, is the same interface across every site and has a huge ecosystem of the add-ons that their clients what. Until you can replicate the WordPress 3rd party developer ecosystem it will remain the dominant player. Also, static sites can't do all the things WordPress does, like polling, comments, shopping carts, etc. you'd have to rely on a third party for those components and when you add up all those, I'd think that would be more than $100/year in subscriptions. It's easier and cheaper to have it all centralized in WordPress which is why agencies choose to use it. If you can charge a retainer too, the holy grail for agencies because it's reoccurring, predictable revenue, you're essentially getting paid to just keep things updated and make sure they don't break or get hacked.

Re: The Next WordPress

#36
post #26

First of all, Wordpress is known to fix security issues quickly and platforms with many developers have more eyes on the code so it's only natural that they have a LOT of reported vulnerabilities. This does not mean that it's "inherently" insecure. A static site can't enable... - User management (Members) - On-site-comments (That Search engines can find) - Voting (Polls & Ratings are very popular on Wordpress!) - Car…

> This does not mean that it's "inherently" insecure. It's a pretty strong indicator though.

Not really. Sometimes you hear about the WordPress security vulnerabilities that are patched, but still exploited, and this is mostly a problem with people not keeping an eye on security updates.

Combine that with the popularity that WordPress has drawing in people who know enough to program themes and plugins, but not enough to program said themes and plugins securely (avoiding simple SQLi and XSS) and you get the perception of an insecure system that WordPress has.

Re: The Next WordPress

#37

I would love to maintain our websites with a static site generator and manage updates via pull requests to our version control system. I don't have a single user who would understand that sentence. That's why we use WordPress.

Totally agree. Wordpress is approachable to most users who want to have a web site for their business, but not super tech savvy.

I still think we can improve the status quo by adopting performance and security benefits that comes with static sites. If you are interested, I wrote elaborative post introducing the solution I'm building www.laktek.com/2016/11/29/introducing-pragma/

Re: The Next WordPress

#38

I was recently considering creating an IDE specifically for WordPress with built-in completion, tips and mapping for people who are skilled at programming but new to WP development. Would anyone use it?

Have you tried Pinegrow?

Re: The Next WordPress

#39
post #28
post #13

Earlier quoted context omitted.

What makes you think that? The word "blog" is nowhere in the article. It's clear to me they're talking about WP the platform.

wonder how one does a static e-commerce site.

Author here. Snipcart is one option for e-commerce for static sites.

https://snipcart.com/

Re: The Next WordPress

#40

The most uninformative article I've ever read that was on the home page of HN. It's full of misconceptions and assumptions (that every WP based site can be be replicated with static site generators, that 'WP is inherently insecure' and so on).

It smells like a thinly veiled piece of advertising for Lektor, to be honest.
Post reply on HN