Drupal Core – Highly Critical Public Service announcement

Re:Drupal Core – Highly Critical Public Service announcement by dreamfactory2 on Wednesday October 29, 2014 @07:27PM (#8530565)

Funnily enough Drupal already has this as a contributed module, would imagine Wordpress has similar. But it's not a massively popular approach as a) it can lead to considerable complexity as an update to an atom of content may need to propagate to many parts of a site, and b) the whole web is moving towards contextual dynamic delivery.

[ Parent | on HN ]

Re:Drupal Core – Highly Critical Public Service announcement by currysausage on Wednesday October 29, 2014 @07:43PM (#8530609)

> Funnily enough Drupal already has this as a contributed module, would imagine Wordpress has similar.

Sure, static export plug-ins do exist in plenty, but I don't think that core functionality like this should be implemented as a plug-in.

First, if it isn't enabled by default, most people won't bother to enable it. Second, who knows how long and how well the plug-in will be maintained? Third, if static export is an architectural afterthought, it will probably break unusual features and workflows.

> a) it can lead to considerable complexity as an update to an atom of content may need to propagate to many parts of a site

We shouldn't let perfect be the enemy of good. Even if some blog article from months ago won't get the updated shiny new sidebar, what's the matter? The New York Times still have content from the web stone age on their server [1] - it doesn't use the latest template, but isn't it more important that this content is still available? It probably wouldn't be had they used a dynamic CMS back in 2001.

> b) the whole web is moving towards contextual dynamic delivery.

I'm not talking about amazon.com. They can probably afford proper maintenance of their fully dynamic site.

[1] http://www.nytimes.com/learning/general/onthisday/big/1014.h...

[ Parent | on HN ]

Re:Drupal Core – Highly Critical Public Service announcement by nowarninglabel on Wednesday October 29, 2014 @09:58PM (#8530963)

As the creator of a static export module for Drupal, and a maintainer of another, I agree that in the end if it's not built into the core, it's not going to have much long-term viability. That said, D8 is built on services, which makes an interface for static export available basically out of the box.

[ Parent | on HN ]

Re:Drupal Core – Highly Critical Public Service announcement by eikenberry on Wednesday October 29, 2014 @11:50PM (#8531266)

> b) the whole web is moving towards contextual dynamic delivery.

But not using server side dynamism like Drupal provides. It is moving towards sites serving up static files consisting mostly of Javascript that then call data services, so called single page sites.

[ Parent | on HN ]

Re:Drupal Core – Highly Critical Public Service announcement by snowwrestler on Thursday October 30, 2014 @11:44AM (#8533623)

In so-called single page sites, the data services are the server side dynamism. The only difference is that you've moved the template engine client-side, and replaced one call to the server-side application with multiple calls.

SQL injection attacks are just as possible against those kinds of apps, although slightly tougher to configure because you need to read client-side JS to find the service URLs, tokens, etc.

Drupal is used to power client-side JS-based sites. The current Tonight Show website is a recent example.

[ Parent | on HN ]