Issue 16102

Articles under /infrastructure could be moved to CMS

Reporter: bko
Type: Improvement
Summary: Articles under /infrastructure could be moved to CMS
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2014-07-10 14:21:25.002
Updated: 2017-10-09 17:14:56.485
Resolved: 2017-10-09 17:14:56.459
Description: While putting Markus' article under infrastructure/data-processing, it reveals that the whole section under infrastructure is served by JavaWeb therefore adding this article with a menu item would need:

1. Varnish vcl update;
2. Template change of menu tabs on the JaveWeb;

Since it's expected that these textual contents will be reorganised, to lower the frequency of the template change and varnish update, and consider it is what CMS is designed for, I propose we move contents under /infrastructure to be managed by Drupal.

Then we can have more flexibility when placing a piece of content and less work from the dev team.

The only thing I see required from my end is to allow full width of the template.]]>

Created: 2014-07-10 14:32:44.879
Updated: 2014-07-10 14:32:44.879
The problem is that Drupal is terribly painful to document in through a browser, whereas HTML is much easier.
This needs some discussion.

Other alternatives for example could be:
- Explore Markdown files - maybe there is a Drupal plugin allowing people to document in markdown
- Move to HTML files that live in the Drupal github
  - we are almost at continuous deployment for Drupal


Created: 2014-07-10 14:42:53.823
Updated: 2014-07-10 14:42:53.823
Good point, Tim. There indeed is Markdown plug-in and solutions on Drupal to do that. After some discussion and if it's agreed that's the workflow we want, I can proceed to specs and implementation.

[], since this would need some discussion, hence time needed, I guess you still want to show that page asap?

Created: 2014-07-10 15:18:29.486
Updated: 2014-07-10 15:18:29.486
if possible yes, Burke. We can pass this specific page thru to drupal. But menu also needs a change, right?
Id love to edit in markdown to be honest...

Created: 2014-07-10 15:29:34.612
Updated: 2014-07-10 15:29:34.612
Yes only /infrastructure/data-processing. And the Java side also need a menu tab for "Data Processing". I've just created an issue specifically for this POR-2312.

Markdown looks like a quite mature solution on Drupal. I like the simplicity of that, too, which saves lots of clicks on the editor.

Created: 2014-07-30 10:48:29.793
Updated: 2014-07-30 10:48:29.793
The menu becomes available as /infrastructure/dataprocessing as we do not use dashes in urls so far at least. Needs to be discussed in the future:


Created: 2014-07-30 11:28:03.133
Updated: 2014-07-30 11:28:03.133
Until we move the entire infrastructure section to drupal I will add the data processing page to java web too as its much simpler.
Actually even authoring the content is MUCH simpler than using the current drupal forms, so before moving the infrastructure pages to Drupal I would suggest to use a new way of authoring first, e.g. via markdown files