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

The CMS Is Broken.

labs.talkingpointsmemo.com

Post reply on HN
Print view View original

51–57 of 57 posts

Re: The CMS Is Broken.

#51

Post by thomasfl »

bergie wrote: post #50
thomasfl wrote: post #49

Earlier quoted context omitted.

Yes it probably would. The API is also accessible from client side javascript. So you could create admin pages in 100% javascript like in HiFi.

Admin pages are one thing, but with VIE you can make content also editable right where it is. See for example what we did with Midgard: http://bergie.iki.fi/blog/introducing_the_midgard_create_use...

I really like the constraints you set on your project: "Build a CMS, no forms allowed". Aloha and other wysiwyg editors can hide the CMS almost totally. Using RDFa to store content is not a bad idea.

Re: The CMS Is Broken.

#52

Post by bergie »

thomasfl wrote: post #51
bergie wrote: post #50

Earlier quoted context omitted.

Admin pages are one thing, but with VIE you can make content also editable right where it is. See for example what we did with Midgard: http://bergie.iki.fi/blog/introducing_the_midgard_create_use...

I really like the constraints you set on your project: "Build a CMS, no forms allowed". Aloha and other wysiwyg editors can hide the CMS almost totally. Using RDFa to store content is not a bad idea.

If you're interested in integrating VIE into that system, then the EU-funded IKS Project might be able to help you with that: http://www.iks-project.eu/get-involved

Re: The CMS Is Broken.

#53

Post by vertice »

bergie wrote: post #43
ejames wrote: post #3

I find this interesting because TPM's solutions reminds me of the classic UNIX "pipes and filters" strategy - a series of small components with well-defined inputs and outputs that can be strung together to produce a sophisticated result. (Of course, "small", "well-defined", and "sophisticated" could be relative terms.) The pipes and filters "API" was plain text transmitted through stdout. It also strikes me as an ex…

I think the natural next step of "UNIX pipes and filters" is Flow-Based Programming ( http://en.wikipedia.org/wiki/Flow-based_programming ). Processes can have multiple named input and output ports, and data flowing between them can be objects and other data formats. In currently building an Open Source FBP tool called "NoFlo" on top of Node.js, and at least the initial results of building websites with it are promis…

This is definitely the direction i see things going.

Node.js is also perfectly suited for it, and I recall hearing that it's also on the core team's mind.

Re: The CMS Is Broken.

#54

Post by kermitthehermit »

lojack wrote: post #39
crikli wrote: post #4

"Drupal, Wordpress and Joomla use PHP. — the plugin model aches at scale: popular plugins become abandoned plugins, energies move elsewhere. Plugin A works great, plugin B too. However, they weren’t designed to know about each other, thus leading you down a rabbit hole of forking and mending. A few years of use later, you are left with an unmaintainable tangle of ad hoc code written by an all-but-unknown cast of prog…

I was once tasked with upgrading a Drupal instance and while I surely don't have the experience you do I have opposing feelings about this. Some of Drupal's more popular plugins are certainly well maintained, but for this case (and I imaging somewhat commonly in the industry) they used numerous obscure plugins, some of which were only in "beta" stage. In checking the repo logs of these plugins it seemed as though som…

It's also common sense to pick the right plugins for the job.

There are a lot of modules which have been deprecated or which are no longer maintained, sure. However, this doesn't mean that Drupal is in any way bad.

Re: The CMS Is Broken.

#55

Post by kermitthehermit »

hippich wrote: post #23
crikli wrote: post #4

"Drupal, Wordpress and Joomla use PHP. — the plugin model aches at scale: popular plugins become abandoned plugins, energies move elsewhere. Plugin A works great, plugin B too. However, they weren’t designed to know about each other, thus leading you down a rabbit hole of forking and mending. A few years of use later, you are left with an unmaintainable tangle of ad hoc code written by an all-but-unknown cast of prog…

I am actively contribute to Drupal and I will say just what you said - OP did not invest enough time to claim what he claimed regarding Drupal. + Community which is not just open source, but just open. Which tends to make their modules to work with others. And it is pleasure to contribute to community like this.

The person who wrote that article doesn't seem to have such great technical skills. He came off as the classic blogger who feels he has to share his opinion about everything without having taken the time to actually write some PHP code, to build a site with Drupal or otherwise.

Re: The CMS Is Broken.

#56

Post by bergie »

vertice wrote: post #53
bergie wrote: post #43

Earlier quoted context omitted.

I think the natural next step of "UNIX pipes and filters" is Flow-Based Programming ( http://en.wikipedia.org/wiki/Flow-based_programming ). Processes can have multiple named input and output ports, and data flowing between them can be objects and other data formats. In currently building an Open Source FBP tool called "NoFlo" on top of Node.js, and at least the initial results of building websites with it are promis…

This is definitely the direction i see things going. Node.js is also perfectly suited for it, and I recall hearing that it's also on the core team's mind.

Here's my project: https://github.com/bergie/noflo

Re: The CMS Is Broken.

#57

Post by bergie »

Periodic wrote: post #8

It sounds like Separation of Concerns[1] applied on a larger scale. Software is easier to manage and more flexible if each piece does one thing and does it well, with as little overlap with other components as possible. This is what makes OOP a good system for designing large programs. I helps people separate out the various components so that maintenance is of many small pieces with clearly defined boundaries instea…

Exactly the approach I'm pitching to CMSs in here: http://bergie.iki.fi/blog/decoupling_content_management/
Post reply on HN