4 ms·

Right now the leading open source new media publishing projects are driven by PHP communities. It's easy to see why, with a well-established and vibrant ecosyst

by mbesto 14y ago

Right now the leading open source new media publishing projects are driven by PHP communities. It's easy to see why, with a well-established and vibrant ecosystem, the PHP community is strong. But, it comes with its limitations, and recently other technologies have taken the lead on innovation.[1] Which limitations are that? I'm curious as to who their user is here. My grandmother or my friend who is a developer? For my grandmother, Wordpress suits perfectly. For my developer, Jekyll. I feel like this is solving a non-problem here. The UI looks great, but then why not just stick it on top of the Wordpress admin? [1] - http://blog.tryghost.org/ http://blog.tryghost.org/

phillmv 14y ago
For delivering a CMS, your server side is totally tech agnostic. The major innovations left are all client side. If anything, people's major complaint with Wordpress is that it's a horrible tangle of spaghetti. What's the state-of-the-art for Node.js web frameworks? There'd be a lot of irony in launching an aesthetically pleasing CMS admin panel overtop yet-another spaghetti engine that is hard to augment.
- Wintamute 14y ago
  I've got high hopes for this. The currently popular web framework for Node.JS is Express (built on top of Connect), which has built on the success of stuff like Sinatra and Rails, and (dare I say) improved on them in some areas. Express/Connect uses the concept of middleware which helps to make defining functionality extremely modular and encapsulated, so hopefully together with the active JS community, plus the excellent package manager npm, should make it really easy (and not too spaghetti-like) to work with a Node.JS based platform.
eksith 14y ago
I thought this was an odd thing to say too. A platform itself may have technical limitations, most of which can usually be worked around or improved on, but often the limitations of "accomplishment" are often in the developer's mind.
corresation 14y ago
For my grandmother, Wordpress suits perfectly. Indeed. Wordpress is a very easy product to use, and adding tech-community loves like markdown will do absolutely nothing in the general community (how can markdown be superior to a WYSIWYG toolbar-formatting model when dealing with generalists?). The project -- while looking good -- seems somewhat confused in focus, as it seems to strive to pander to the hacker community (node, express, etc), yet argues usability benefits that I don't think really hold water.

by mbesto 14y ago

phillmv 14y ago

For delivering a CMS, your server side is totally tech agnostic. The major innovations left are all client side. If anything, people's major complaint with Wordpress is that it's a horrible tangle of spaghetti. What's the state-of-the-art for Node.js web frameworks? There'd be a lot of irony in launching an aesthetically pleasing CMS admin panel overtop yet-another spaghetti engine that is hard to augment.

Wintamute 14y ago
I've got high hopes for this. The currently popular web framework for Node.JS is Express (built on top of Connect), which has built on the success of stuff like Sinatra and Rails, and (dare I say) improved on them in some areas. Express/Connect uses the concept of middleware which helps to make defining functionality extremely modular and encapsulated, so hopefully together with the active JS community, plus the excellent package manager npm, should make it really easy (and not too spaghetti-like) to work with a Node.JS based platform.

eksith 14y ago

I thought this was an odd thing to say too. A platform itself may have technical limitations, most of which can usually be worked around or improved on, but often the limitations of "accomplishment" are often in the developer's mind.

corresation 14y ago

For my grandmother, Wordpress suits perfectly. Indeed. Wordpress is a very easy product to use, and adding tech-community loves like markdown will do absolutely nothing in the general community (how can markdown be superior to a WYSIWYG toolbar-formatting model when dealing with generalists?). The project -- while looking good -- seems somewhat confused in focus, as it seems to strive to pander to the hacker community (node, express, etc), yet argues usability benefits that I don't think really hold water.