[Discussion] Revisiting the commit flow across editors

In GitLab we have different editing experiences. Each of these editing experiences have a different interface when saving changes.

Wiki Static site Single file Pipeline editor Web IDE
Commit type gitlab.com_mle_ramen_-wikis_home_edit__2 gitlab.com_gitlab-com_www-gitlab-com_-_sse_master_2Fsites_2Fhandbook_2Fsource_2Fhandbook_2Fengineering_2Fdevelopment_2Fdev_2Fcreate-editor_2Findex.html.md.erb gitlab.com_mle_ramen_-edit_dev_README.md__1 image gitlab.com_-ide_project_mle_ramen_merge_requests_4_target_project___24

This issue is meant to capture the differences in the saving changes flow and ask the questions:

  • Should these experiences be different?
  • How might these experiences be improved so that there is familiarity when moving from one area to another?

The reason we are talking about this now is that these editing experiences are sitting on top of a git framework when saving or committing changes. We don't want users to re-learn an interface everytime they are in a different part of GitLab. We may adjust what we show by default in the different product areas but the full power of the commit flow should be accessible at all stages.

  • @mle Capture saving flows of each of the editors
  • Attach issues related to improvments/feature requests for the commit flow
  • Discuss as a group the themes/areas we should improve on based on current information
  • Discuss as a group on which areas of the flow we should prioritize on improving for next few milestones
  • Identify areas where there needs more research to clarify problem areas.
Edited by Michael Le