Focusing on "Getting Started" #93
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jordanstephens
force-pushed
the
jordan/shorter-getting-started
branch
7 times, most recently
from
84b5229 to
4c33e18
Compare
jordanstephens
force-pushed
the
jordan/shorter-getting-started
branch
from
4c33e18 to
bc12a3d
Compare
My primary goal here is to make this doc as short as possible while still getting the user their first win using defang.
jordanstephens
force-pushed
the
jordan/shorter-getting-started
branch
from
bc12a3d to
f5d69fa
Compare
Co-authored-by: Jordan Stephens <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rethinking the "Getting Started" doc to be as short as possible while still giving the user their first "win" using Defang.
I've pushed the "Monitor services" and "Update services" sections off the first page and into the "Next steps" section. I think we can better handle those topics in separate docs.
Keeping these docs short makes them more easily navigable, searchable, and focused. It minimizes page scanning, and assures the user that they can tackle the next step!