Get CMS requirements from OCWG

[athu-tran]

As the OCWG and Secretariat, we have a business requirement to have an easy to use Content Management System (CMS) to allow users to easily create and modify website content without having to learn code.

Requirements:

• Ability to post news, blog, & podcast article text with links, bulleted lists, subsection heads for longer articles, tables when needed, bolding, italics, image files + edit older articles
• Ability to post new events titles, descriptive text, and links + edit older events
• Ability to upload, delete, and replace files: images (jpg, png, svg, etc.); documents (PDF, Word, PPT, XLS, etc.); audio and video (mp3 and mp4)
• Ability to update the CNAs table including text and urls (until it's populated via a database, if that's still coming via services)
• Ability to upload, delete, and replace files, text, and links on Metrics page (until it's populated automatically via services)
• Ability to add or delete Board members, add/delete their photos, change their company affiliations, and reorder the page if a last name changes
• Ability to edit, add, or delete body text on ALL pages of website
• Ability to edit, add, or delete text, urls, and social media icons in the website footer
• Ability to edit, add, or delete section headers on ALL pages of website
• Ability to edit, add, or delete urls on ALL pages of website
• Ability to add entirely new pages and delete outdated pages if necessary
• Ability to add, delete, or update all menu items and their urls on the website
• Ability to track users, their edits, and the dates of their edits over time
• Ability to enter text for and turn on/off the site-wide notification banner message.
• Any authenticated user should be able to submit a content change request. Review by the OCWG and secretariat should be part of this workflow.

Done before #218
child of #135

[rroberge]

The OCWG co-chairs and OCWG website content sub-working group want to be sure that the OCWG is able to determine specifically who has access to the CMS to ensure the integrity of the website content for which the OCWG will be responsible. Therefore, per the OCWG, the group of individuals who will be authorized to access to the CMS will be on the small side, once they are identified by the OCWG website content sub-working group and the OCWG co-chairs.

OCWG’s CMS Requirements:

1. Ability to post news, blog, & podcast article text with links, bulleted lists, subsection heads for longer articles, tables when needed, bolding, italics, image files + edit older articles
2. Ability to post new events titles, descriptive text, and links + edit older events
3. Ability to upload, delete, and replace files: images (jpg, png, svg, etc.); documents (PDF, Word, PPT, XLS, etc.); audio and video (mp3 and mp4)
4. Ability to update the CNAs table including text and urls (until it's populated via a database, if that's still coming via services)
5. Ability to upload, delete, and replace files, text, and links on Metrics page (until it's populated automatically via services)
6. Ability to add or delete Board members, add/delete their photos, change their company affiliations, and reorder the page if a last name changes
7. Ability to edit, add, or delete body text on ALL pages of website
8. Ability to edit, add, or delete text, urls, and social media icons in the website footer
9. Ability to edit, add, or delete section headers on ALL pages of website
10. Ability to edit, add, or delete urls on ALL pages of website
11. Ability to add entirely new pages and delete outdated pages if necessary
12. Ability to add, delete, or update all menu items and their urls on the website
13. Ability to track users, their edits, and the dates of their edits over time
14. Ability to enter text for and turn on/off the site-wide notification banner message.

[david-waltermire]

Any authenticated user should be able to submit a content change request. This should be added as a requirement. Review by the OCWG and secretariat should be part of this workflow.

[david-waltermire]

I approve this user story.

[rroberge]

As requested, proposed text for new requirement #15:

15. Ability for authenticated users (i.e., authorized community members such as WG chairs and Board members) to be able to submit website content change suggestions/requests so that the requests may be reviewed by the OCWG and Secretariat and, if accepted, implemented by the Secretariat.

[athu-tran]

As requested, proposed text for new requirement #15:

1. Ability for authenticated users (i.e., authorized community members such as WG chairs and Board members) to be able to submit website content change suggestions/requests so that the requests may be reviewed by the OCWG and Secretariat and, if accepted, implemented by the Secretariat.

Seems like we can use the cve-website GitHub issue tracking feature for this.