Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation #3

Merged
merged 7 commits into from
Jul 30, 2021
Merged

Add documentation #3

merged 7 commits into from
Jul 30, 2021

Conversation

github-learning-lab[bot]
Copy link
Contributor

Step 4: Create user documentation

Well written user documentation is the key to a great user experience. Experts say, "if a user can't figure out how to use your project in less than an hour, they will move on." It pays to attract a few technical writers to your project. 😉

Where to create your documentation

Where to create documentation

Your user documentation should be easy for your users to find. Some prefer to keep it on an externally facing website while others will use a docs folder in their project or the repository wiki.

Getting organized

As an open source project becomes more popular and more sophisticated, some maintainers find it is easier to move their open source project into an a GitHub organization. This allows you to create separate repositories for your project's promotional website, documentation, source code, etc.


What to include

Documentation needs for open source projects will vary, but at a minimum you should include:

  • Installation instructions
  • Completing essential tasks
  • Customizing and configuring

Will you help Mona ensure the documentation covers these minimum topics?

⌨️ Activity: Creating user documentation

You can follow the manual steps below, or accept the suggested change in the following comment.

  1. Edit docs/getting-started.md on this branch, or manually edit it in the Files Changed tab.
  2. Find the placeholder text marked CONFIGS PLACEHOLDER.
  3. Replace the placeholder with some example welcome messages that may be helpful to new users.
  4. After editing the docs/getting-started.md file, scroll down and click the Commit changes button.

I'll respond when I detect a commit on this branch.

@github-learning-lab github-learning-lab bot mentioned this pull request Jul 30, 2021
Co-authored-by: github-learning-lab[bot] <37936606+github-learning-lab[bot]@users.noreply.github.com>
@github-learning-lab
Copy link
Contributor Author

Step 5: Merge the user documentation

This Getting Started guide is going to be a great resource for new users. Let's go ahead and merge it - we can always iterate.

⌨️ Activity: Approve the pull request

  1. Clicking on this quicklink
  2. Select Approve
  3. Click Submit review.

You can also approve by clicking on Files changed, clicking on Review changes, selecting Approve and then Submit review.


I'll respond when you've approved this pull request.

Copy link
Owner

@luisifern luisifern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

@github-learning-lab github-learning-lab bot merged commit d406a13 into main Jul 30, 2021
@github-learning-lab
Copy link
Contributor Author

You have been a huge help to Mona in preparing the repository for new users. Next, let's shift our focus to Mona's future contributors. Mona has been busy putting some thoughts together and is ready for your eyes. 👀


Check out the next issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants