Deployment Direction Feedback and Improvement
Why is this change being made?
Hey all, most of the content I had in my head are now in the deployment direction page.
Below is a checklist of things I know I need help with:
-
Review and provide edits for readability. Add links where appropriate. -
Review vision, strategy, challenges, opportunities, key capabilities. Challenge my assumptions, projections. -
What questions did we not answer that we should answer? -
Can we communicate any concepts better with a visual representation? -
Fill in the User Persona section -
In the competitive landscape section, I think we should analyze Jenkins X for deployment. We should also research Weave.works more deeply -
I copied Orit's competitive landscape from the continuous delivery direction page. A lot of it is repeated. We should probably share one source of truth between those two pages
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what -
Assign this change to the correct DRI - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
-
If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping(this requirement has been removed pending identification of a new DRI for the handbook)@gl-static-site-editor
in a comment for a review and merge. For example changes to.gitlab-ci.yml
, JavaScript/CSS/Ruby code or the layout files.
Edited by Kenny Johnston