2019-Q2 Recommendations for Release: Deploy to Gitlab Pages
Part 1: JTBD
Part 2: Experience Recommendations
-
After completing the Experience Baseline for a JTBD, create a “{{YYYY}}{{Quarter}} Recommendations for…” issue for each JTBD and include them in the Part 2: Experience Recommendations sub-epic. -
Brainstorm opportunities to fix or improve areas of the experience. -
Use the findings from the Emotional Grading scale to determine areas of immediate focus. For example, if parts of the experience received a “Negative” Emotional Grade, consider addressing those first. -
Create an issue for each recommendation and link them to the corresponding JTBD recommendations issue. -
Think iteratively, and create dependencies where appropriate, remembering that sometimes the order of what we release is just as important as what we release. -
If you need to break recommendations into phases or over multiple milestones, create multiple epics and use the Category Maturity Definitions in the title of each epic: Minimal, Viable, Complete, or Lovable.
Recomendations
Add a link to page setting on the project details page
Similar to Set up CI/CD
or Add CHANGELOG
quick links, this would provide a jumping-off point to improve the discoverability of the page settings. This could be static, but preferably dynamic based first on if it is a page capable project, and also if change text once pages are set up.
https://gitlab.com/gitlab-org/gitlab-ce/issues/65359
Provide in UI documentation
On the settings page, we can give a brief description of the setup process and then link to the general documentation. This could replace the current Configure pages
section.
https://gitlab.com/gitlab-org/gitlab-ce/issues/65360
Reorganize the documentation
Prioritize the setup process to be at the top of the document. Separate out the process for adding pages to a project vs starting a from a template. Section out general information and support information.
https://gitlab.com/gitlab-org/gitlab-ce/issues/65527
Link to yaml file
Provide a connection between the setting page and the yaml file. If one has not been created it can link to the jumping-off point to create one, similar to the Set CI/CD
quick link. We could provide a dropdown to select preferred SSG and then prepopulate once linked.
https://gitlab.com/gitlab-org/gitlab-ce/issues/65403
Include templates for major SSG
In the yaml template dropdown, add the template for Vuepress. Investigate if there are other popular static site generators we do not have templates listed for.
https://gitlab.com/gitlab-org/gitlab-ce/issues/65408
Label and group templates as pages templates
In the yaml template dropdown, label and group all the pages templates together. Example Hugo -> Pages - Hugo
Option to add url to the project description
Add an option that would allow the url to be appended to the project description. This will cause it to show up on the project detail page as well as the project list view. We need to consider multiple url's.
https://gitlab.com/gitlab-org/gitlab-ce/issues/65520
Add 30 min delay messaging.
Add messaging indicating potential 30 min delay on the first deploy. This could be a static message, or ideally dynamic based on if the page has deployed.
https://gitlab.com/gitlab-org/gitlab-ce/issues/65304
Links jobs/pipelines that deploy
For jobs and pipelines that result in a deployment to pages, include information including a link to the deployed page.
https://gitlab.com/gitlab-org/gitlab-ce/issues/65523
Redesign page settings page
Provide a new layout to accomplish:
- Reduce the visual impact of remove pages section
- Better connection between
New domain
and the domain list - Reduce confusion of the
Save
button - Provide an area for in UI documentation