torecovers.blogg.se - New relic docs

#NEW RELIC DOCS HOW TO#
#NEW RELIC DOCS CODE#

Code, including sample code, contained in the docs-website repository is licensed under the Apache 2.0 license.

The content of New Relic product documentation in the docs-website repository is licensed under a CC-BY-NC-SA 4.0 license.

You may also be interested in the New Relic Developer website and Open Source website repos. If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at New Relic Developer and Open Source sites You only have to sign the CLA one time per project. Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. Please review our Contributors Guide prior to submitting any code. We welcome contributions to the New Relic Docs Site.

#NEW RELIC DOCS HOW TO#

If you'd like to go deeper with development, see our Contributors guide for information on how to fork our site, build it locally, and submit pull requests. Let us handle the little details for you. We're looking for your technical insight and knowhow. Reading the style guide is totally optional! Our writers are here to make sure everything is formatted and worded right. Additionally, our Style guide will give you some insight into how we think about writing and documentation, as well as our flavor of Markdown. If you'd like more information on how to edit our docs, read our processes to create and edit content. Finally, follow the prompts to create a pull request and submit your changes for review.įrom there our writers will check out your pull request, comment with any feedback, and merge your change.This will automatically create a fork in your GitHub account with the changes. Make your changes, then click Commit changes.Click it to access GitHub and the source file for that doc page. Every doc page on has an Edit page pencil button in the right sidebar and the footer.If you'd like to get more directly involved, you can edit the docs yourself! Here's how: You can also let us know about things you'd like to see. You can create an issue to let us know when you find an error or notice something missing. We'll review your issue and follow up with you if we have any questions. Issues are a quick way to give us feedback about our docs. On each page of our docs, you can create an issue or edit a page. We're here working every day to improve our docs and we'd love to hear from you. By making our docs open source, we hope to expand this conversation.

In a sense, it's documentation as conversation. We credit our technical accuracy and comprehensive documentation to this openness. Now, we're open sourcing our docs to invite input from anyone at all. We'd like your helpįrom the start, we've welcomed contributions from anyone at New Relic, not just writers. Read on to learn more about who we are and how you can contribute to the New Relic Docs site.

#NEW RELIC DOCS CODE#

This repo contains all the source code and Markdown source files we use to build our docs site.