gradio/guides/CONTRIBUTING.md
pngwn 643442e1a5
generate docs json in ci, reimplement main vs release (#5092)
* fixup site

* fix docs versions

* test ci

* test ci some more

* test ci some more

* test ci some more

* asd

* asd

* asd

* asd

* asd

* asd

* asd

* asd

* asd

* test

* fix

* add changeset

* fix

* fix

* fix

* test ci

* test ci

* test ci

* test ci

* test ci

* test ci

* test ci

* test ci

* test ci

* notebook ci

* notebook ci

* more ci

* more ci

* update changeset

* update changeset

* update changeset

* fix site

* fix

* fix

* fix

* fix

* fix ci

* render mising pages

* remove changeset

* fix path

* fix workflows

* fix workflows

* fix workflows

* fix comment

* tweaks

* tweaks

---------

Co-authored-by: gradio-pr-bot <gradio-pr-bot@users.noreply.github.com>
2023-08-11 15:54:56 +01:00

2.0 KiB

Contributing a Guide

Want to help teach Gradio? Consider contributing a Guide! 🤗

Broadly speaking, there are two types of guides:

  • Use cases: guides that cover step-by-step how to build a particular type of machine learning demo or app using Gradio. Here's an example: Creating a Chatbot
  • Feature explanation: guides that describe in detail a particular feature of Gradio. Here's an example: Using Flagging

We encourage you to submit either type of Guide! (Looking for ideas? We may also have open issues where users have asked for guides on particular topics)

Guide Structure

As you can see with the previous examples, Guides are standard markdown documents. They usually:

  • start with an Introduction section describing the topic
  • include subheadings to make articles easy to navigate
  • include real code snippets that make it easy to follow along and implement the Guide
  • include embedded Gradio demos to make them more interactive and provide immediate demonstrations of the topic being discussed. These Gradio demos are hosted on Hugging Face Spaces and are embedded using the standard <iframe> tag.

How to Contribute a Guide

  1. Clone or fork this gradio repo
  2. Add a new markdown document with a descriptive title to the /guides folder
  3. Write your Guide in standard markdown! Embed Gradio demos wherever helpful
  4. Add a list of related_spaces at the top of the markdown document (see the previously linked Guides for how to do this)
  5. Add 3 tags at the top of the markdown document to help users find your guide (again, see the previously linked Guides for how to do this)
  6. Open a PR to have your guide reviewed

That's it! We're looking forward to reading your Guide 🥳