-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the FOSS-Artist-workflow-Guide wiki!
I'm just testing some stuff, so don't take anything you see here too seriously until it starts to look official..
title: Start with a present participle shortTitle: # Max 31 characters intro: 'Article intro. See tips for a great intro below.' product: "{{ optional product callout }}" type: how_to topics:
- # One or more from list of allowed topics: https://github.com/github/docs/blob/main/data/allowed-topics.js versions:
{% comment %} Follow the guidelines in https://docs.github.com/contributing/writing-for-github-docs/content-model#procedural to write this article.-- > Great intros give readers a quick understanding of what's in the article, so they can tell whether it's relevant to them before moving ahead. For more tips, see https://docs.github.com/contributing/writing-for-github-docs/content-model For product callout info, see https://github.com/github/docs/tree/main/content#product For product version instructions, see https://github.com/github/docs/tree/main/content#versioning Remove these comments from your article file when you're done writing {% endcomment %}
{% comment %} Include prerequisite information or specific permissions information here. Then write procedural steps following the instructions in https://docs.github.com/contributing/style-guide-and-content-model/style-guide#procedural-steps. Check if there's already a reusable string for the step you want to write in https://github.com/github/docs/tree/main/data/reusables. Look at the source file for a procedure located in the same area of the user interface to find reusables. {% endcomment %}
{% comment %} Keep adding procedures until you've finished writing your article. {% endcomment %}
{% comment %} Optionally, include a bulleted list of related articles the user can reference to extend the concepts covered in this article. Consider linking to procedural articles or tutorials that help the user use the information in your article. {% endcomment %}