Did it work?
Thank you all for the work on Solution Explorer:
Short cut to the user
They express how we want a cluster to work (collect user stories tues/wed)
SOPs are walkthroughs on a QE cluster (get an example SOP)
Day in the life workshops
Instead of writing, you can find existing files that suit your purpose.
Find an AsciiDoc file:
Copy the source file.
For example: Basic Walkthrough for OSD
Navigate to https://github.com/pwright/curly-garbanzo
Click Use Template.
/walkthroughs/empty/walkthrough.adoc file to add your content from step one.
Rename the directory from
empty to reflect purpose of your Solution Pattern.
Commit and push your changes.
This presentation is a Solution Pattern
See repo and the node setup docs.
Edit the file to add some generic content:
menu on right
Did it work?
Try the steps again. If it’s still not working contact your administrator.
There’s a CCS initiative to make docs modular, meaning that in the future you’ll need to assembly your Solution Pattern
Pro: you can assembly cross product Solution Patterns
Con: you must assembly a Solution Pattern, you won’t find ready-made Solution Patterns in docs
Browse the available modules, eg https://github.com/openshift/openshift-docs/tree/master/modules
Grab the files you want
Put them into a directory
Create an assembly, eg:
Unresolved directive in walkthrough.adoc - include::<file>
Create the walkthrough.adoc
./bin/assemble.sh walkthroughs/modules/assemby.adoc walkthroughs/modules/walkthrough.adoc
Writing clarifies thinking - https://hbr.org/2016/09/bad-writing-is-destroying-your-companys-productivity