Add standalone getting started guides structure. #4492
Merged
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.
Thoughts
We have been designing the new format for the docs being displayed in the webapp for source and destination setup as per this issue: #3879 and its children. We thought we could just create a directory for each source and destination right where they lived, but this would massively change the directory structure, causing us to need to change things in a lot of different places. I propose a less invasive solution:
getting-started
and place all getting-started guides here initially. Have the naming convention betype-name
e.g.source-facebook-marketing
to be identified and loaded by the backend onto the image.Main Changes