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

Improve the documentation by splitting apart the readme sections into separate files #259

Merged
merged 1 commit into from Nov 30, 2015

Conversation

kattrali
Copy link
Contributor

The readme file has gotten fairly long and hard to follow. This pull request breaks it up into separate files, categorizing "readme stuff" as the basics which users need to get started, find support, and contribute, and moving the other stuff into the docs/ directory. Hopefully the format can then be reused by other notifier libraries for consistency.

The remaining readme content is largely the same, just reorganized into the installation -> basic usage -> support flow.

New files

  • docs/README.md: Index of the documentation directory
  • docs/Configuration.md: All configuration options
  • docs/Notification Options.md: notification-specific options as well as custom handling for various frameworks and non-fatal exceptions

Other concerns

The readme is linked from the bugsnag.com documentation, are there any problems presented by splitting the file?

/cc @snmaynard

* Create documentation directory
* Move configuration into docs file
* Move notification options into docs file
* Reorganize readme into a reusable pattern
kattrali added a commit that referenced this pull request Nov 30, 2015
Improve the documentation by splitting apart the readme sections into separate files
@kattrali kattrali merged commit e296936 into master Nov 30, 2015
@kattrali kattrali deleted the kattrali/enhance-documentation branch November 30, 2015 19:36
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.

None yet

1 participant