Make the Static Site Editor available to all pages in the GitLab Handbook
The GitLab Handbook is a perfect candidate for using the Static Site Editor to encourage contributions across departments and personas. Using the Static Site Editor to make changes to pages within the handbook will serve as an opportunity to get valuable feedback for our new feature and streamline contributions made to individual pages.
This issue is for the full implementation of the Static Site Editor as described in item 4 below.
- First, we need to ensure that the existing pages can work in the Static Site Editor. The GitLab handbook content is not exclusively written in Markdown and the editor needs to be prepared to parse that content. #216836
- Next, we'll configure the project to use the Static Site Editor but leave the page templates themselves untouched. This way, we can test any page we want by manually passing the URL into the Static Site Editor before we have 1,300 people jumping in to use it. #221252
- Once it's configured, we'll add a link on all pages within the
/productsection of the Handbook. Product managers (and those contributing to Product pages) represent a key persona and a small enough group that the feedback will be manageable and actionable. #221253
- Finally, after we address any critical feedback, we'll make the Static Site Editor available on all supported handbook pages by adding a link in the page template.