We welcome your contributions, whether you are a New Relic employee or a New Relic user! And we don't want you to worry about style. When you edit a file, tech writers on our team review it for style, grammar, and formatting. That said, if you're curious about our style guidelines, you're welcome (but not obligated) to take a look.
If you see a minor problem in our documentation that you want to quickly fix, you can use GitHub to edit the file and submit your pull request. A member of the Docs team will review your edit and publish your changes. We'll follow up with you if we have any questions.
To edit existing content without building the site locally:
- On the docs site, navigate to the doc you'd like to edit.
- Click Edit page on the top corner of the right nav.
- A GitHub page will open with the source of the doc. Click the pencil icon in the top right.
- Make your edits (don't worry too much about formatting or grammar, we're happy to take care of that).
- At the bottom of the page, enter acommit message that describes your change, then click Commit changes.
- Follow the prompts to submit your pull request.
A member of the Docs team will review your pull request and comment with any feedback. Once we've merged your pull request into the Develop branch, your changes will go live with our next deploy (usually within a few hours).
- Clone the repo on your computer.
/src/content/docs/, find a good location for your doc.
- Using your text editor, create a new
.mdxfile or copy an existing doc.
- Write your content.
- Optional: Add your doc to the right nav
.ymlfile. The navigation files can be a bit hard to work with, so feel free to leave this step for a Docs writer to handle when they review your pull request.
- Commit your changes and create a pull request.
The Tech Docs team has two heroes watching for new pull requests. We'll help you get the content finalized and make sure that it's in the right place.
Once you've cloned the
docs-website repository, use your text editor to copy an existing doc. Rename and edit the copy and then save it as a new doc. Your cloned doc automatically inherits the original doc's frontmatter content. Make sure to change that, too.
If you want your cloned doc to be translated, follow standard procedures to request translation.
If you're making larger changes like adding a whole new doc or editing many existing docs, it can be helpful to run the site locally. For instructions, see Tech writer workflow.
If you are comfortable with deleting the page yourself, go for it. If not, ask us by:
- File an issue in the docs-website repo, or contact the @hero in the #documentation channel if you're a New Relic employee.
- We'll take a look at your issue and help out.
If you need to stage content for a private beta or limited release, contact the docs hero in the #documentation Slack channel.
If your draft needs to be released on a specific date or within a specific timeframe (for example, right before a release), contact the Tech Docs @hero in the #documentation Slack channel. If you're not a New Relic employee, please create a GitHub issue.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.