11–20 of 76 posts
I was always under the impression that they're Django/Python. Can anyone confirm?
We use a pretty normal ("boring") Java stack with Spring, Hibernate and Jersey. Some of the older components use Struts + JSPs whereas the newer components use Backbone (and related libraries).
The CMS is in a renaissance period with Wordpress, Joomla, Drupal and the like falling out of favor. I believe the CMS is bifurcating into two specialized directions. Several online publishers are coming out and describing their new, home-grown custom CMS. The features are rich and provide robust, innovative tools across the long-form content lifecycle: writing, editing, and publication. There is special attention to…
I think Wordpress is still going to stay in the game. It still has a road ahead of it. I do think that the big newsrooms are going to expand past it's limiting multiple-people collaboration features into a new CMS, but most blogs will want to use WP.
The CMS is in a renaissance period with Wordpress, Joomla, Drupal and the like falling out of favor. I believe the CMS is bifurcating into two specialized directions. Several online publishers are coming out and describing their new, home-grown custom CMS. The features are rich and provide robust, innovative tools across the long-form content lifecycle: writing, editing, and publication. There is special attention to…
Developing a custom CMS makes sense for exactly one type of company: a publisher whose entire business depends on their CMS. For companies in that situation, developing a custom CMS is a capital investment in their core product.
Everyone else will save time, money, and security headaches by building on a popular open source platform. Heck even Twitter uses Drupal to power their developer site.
The CMS is in a renaissance period with Wordpress, Joomla, Drupal and the like falling out of favor. I believe the CMS is bifurcating into two specialized directions. Several online publishers are coming out and describing their new, home-grown custom CMS. The features are rich and provide robust, innovative tools across the long-form content lifecycle: writing, editing, and publication. There is special attention to…
SSGs are hugely popular among nerds and practically unknown among everybody else. The result is a kind of distortion where, to nerds, it looks like SSGs are about to take over the world -- "all my friends use them!" But step outside that tight network of people and they are more or less completely off the radar.
I was always under the impression that they're Django/Python. Can anyone confirm?
The CMS is in a renaissance period with Wordpress, Joomla, Drupal and the like falling out of favor. I believe the CMS is bifurcating into two specialized directions. Several online publishers are coming out and describing their new, home-grown custom CMS. The features are rich and provide robust, innovative tools across the long-form content lifecycle: writing, editing, and publication. There is special attention to…
I don't know about Joomla but Wordpress and Drupal are hardly falling out of favor; they're actually both growing quite rapidly. Developing a custom CMS makes sense for exactly one type of company: a publisher whose entire business depends on their CMS. For companies in that situation, developing a custom CMS is a capital investment in their core product. Everyone else will save time, money, and security headaches by…
My point is that the traditional CMS is falling out of favor as the default solution for content on the Web. Need a blog? Wordpress is increasingly NOT the solution. As developers, we are trending away from the one-size-fits-all CMS and into specialized categories of CMS.
The CMS renaissance is due to two factors:
1) A proliferation of great tools emerging into a toolchain ecosystems. Node's Grunt and Gulp are fine examples. This is largely different than the traditional CMS because...
2) Developers are increasingly wanting to gain more control over our craft.
The CMS is in a renaissance period with Wordpress, Joomla, Drupal and the like falling out of favor. I believe the CMS is bifurcating into two specialized directions. Several online publishers are coming out and describing their new, home-grown custom CMS. The features are rich and provide robust, innovative tools across the long-form content lifecycle: writing, editing, and publication. There is special attention to…
I would humbly suggest that static site generators are not nearly as popular as you might think if you only view the CMS market through the eyes of the HN crowd. SSGs are hugely popular among nerds and practically unknown among everybody else. The result is a kind of distortion where, to nerds, it looks like SSGs are about to take over the world -- "all my friends use them!" But step outside that tight network of peo…
The CMS is in a renaissance period with Wordpress, Joomla, Drupal and the like falling out of favor. I believe the CMS is bifurcating into two specialized directions. Several online publishers are coming out and describing their new, home-grown custom CMS. The features are rich and provide robust, innovative tools across the long-form content lifecycle: writing, editing, and publication. There is special attention to…
I would humbly suggest that static site generators are not nearly as popular as you might think if you only view the CMS market through the eyes of the HN crowd. SSGs are hugely popular among nerds and practically unknown among everybody else. The result is a kind of distortion where, to nerds, it looks like SSGs are about to take over the world -- "all my friends use them!" But step outside that tight network of peo…
Just to be clear, I'm not knocking any of this. The fact that people have put their own time and effort into building SSGs and then generously open sourced them is pretty awesome.
In my view, the audience for SSGs, whether intentional or not, is mostly other programmers. What would it take to make an SSG appeal to a broader set of users?
Earlier quoted context omitted.
I don't know about Joomla but Wordpress and Drupal are hardly falling out of favor; they're actually both growing quite rapidly. Developing a custom CMS makes sense for exactly one type of company: a publisher whose entire business depends on their CMS. For companies in that situation, developing a custom CMS is a capital investment in their core product. Everyone else will save time, money, and security headaches by…
Ironically, I've heard the argument that, for the malleable website case, most people will save time, money, and security headaches by avoiding the traditional CMS. My point is that the traditional CMS is falling out of favor as the default solution for content on the Web. Need a blog? Wordpress is increasingly NOT the solution. As developers, we are trending away from the one-size-fits-all CMS and into specialized c…
> As developers, we are trending away from the one-size-fits-all CMS and into specialized categories of CMS.
Most of the sites which would typically get built on Drupal (and especially Wordpress) aren't owned by developers. Further, these owners probably don't even have a developer on staff or even on a maintenance retainer. Many of these sites are setup by relatively non-technical users. Many of these sites are setup by a developer the owner has paid and then that developer is out of the picture to be run by the owner.
Even if you are a start-up building your own web app, it still often doesn't make sense to build your own blogging system. Rather, you would get your first version out the door ASAP, throw your blog up on a sub-domain running Wordpress and then maybe down the road figure out something different.
Do what you want for your own site. But when you are doing something for clients who don't have a tech staff, it's not about what the developer wants.