Create Automated Event Creation Tutorial #15
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.
This PR adds the first draft of a step-by-step tutorial for creating event content using github issue automation. The guide includes screenshots for each stage of the flow.
Files
content/tutorials/automated_events.mdcontent/_static/tutorials/issue-automation/Open questions & proposal
Separate tutorials for Events vs News?
I'd suggest having different pages, as:
Tutorials structure
Which tutorial categories will we host beyond website content, and how should we organize them? Should we keep separate subfolders for each category?
For the current tutorial, an example path could be
tutorials/website/automated-content/.Notes on screenshots & examples
Current screenshots use example data. Once new content is uploaded, we might replace them with real screenshots.