content management system

[only1chunts]

Content Management System

The curators require the ability to update text on any of the static pages of the gigadb.org website without the need to ask a developer to do it.

User story

As a site administrator I want a content management system So that we can update static content

Acceptance criteria

Each of the following story tickets should be completed for this Epic:

• [ ] #592
• [ ] #593
• [ ] #595
• [ ] #596
• [x] #615
• [ ] #618
• [ ] #620
• [ ] #422
• [ ] #710
• [ ] #716
• [ ] #274
• [ ] #954
• [ ] #955
• [ ] #956
• [ ] #957
• [ ] #971
• [ ] #972
• [ ] #973
• [ ] #974
• [ ] #975

Additional information

Anytime a page is updated there should be a time stamp added to the updated page to say this page was "last updated DD-MM-YYYY"

Nice to have feature:

• Someway for us to keep track of any changes made would be nice to have, with the potential of a roll-back feature to return to the previous version of a page.
• Different levels of users, e.g. all curators should be able to update FAQs, submission guidelines and checklists, but only a manager level user should be able to update other pages like the advisory board, terms and conditions etc.

There is a dependency/overlap with:

• Github item #422 the controlled vocabularies pages (http://gigadb.org/site/help#vocabulary) should be auto-updated from the database
• This product is required to enable some of the other items in the product backlog, see github project 9 https://github.com/gigascience/gigadb-website/projects/9

Benefits:

Reduces workload and time pressures on the tech team by enabling the curators to accomplish updates to the content of the GigaDB pages. Enables us to keep user guides and documentation upto date more easily.

Risks/blocks:

This item reduces the risk of having out-of-date documentation on the public website. A potential risk is that changes are made by individuals without proper consideration or authorisation

• enabling some sort of sign-off procedure either within the system or as part of the SOP for using the system can mitigate this risk.
• Adding a rollback feature would also allow for rapid undo-ing of mistaken updates The encoding needs to be considered, i.e. and interface using the WYSIWYG philosophy may be required as the expected users may not be proficient in MarkDown or HTML.

Spec and Design doc:

https://docs.google.com/document/d/1knHXt-r6_HOWPU4SaR1lkuFshh_vS-AQc_oa6fqbkLM/edit?usp=sharing

[rija]

As a site administrator I want a content management system So that we can update static content