• English日本語한국어
  • 로그인지금 시작하기

Create content for the preview docs site

The preview docs site hosts docs for upcoming features that we share with customers. Unlike the public docs site, the preview docs site isn't publicly editable and doesn't appear in search engine results. Users can't navigate from one preview doc to another, because the site isn't indexed.

Because the preview docs site is located in a different repository than the public docs site, contributing looks a little different. By the end of this doc, you'll be ready to create a new doc for the preview site.

Set up your local environment

If you've previously cloned the beta-docs-site repo on your computer, skip to step 3.

  1. Go to the beta-docs-site repo. If you do not have access, contact the #doc-eng-help Slack channel for help.
  2. Clone the beta-docs-site repo on your computer.
  3. Make sure you're working in the correct repo on Github Desktop.
  4. Create a branch off the main branch.

Create a new preview doc

Despite differences between the public and preview docs sites, the formatting and syntax of their content is largely the same. Once you're in your working branch:

  1. Using your text editor, create a new .mdx file or copy an existing preview doc for the frontmatter template.
  2. Save the file in /src/content/docs/.
  3. Write your content, making sure to include any info about signing up for and requesting access to the preview feature you're documenting.
  4. Commit your changes and create a pull request.
  5. Share the preview link with reviewers and implement any feedback.
  6. Merge the final PR.
  7. Create the official link by pasting the file path name after https://docs-preview.newrelic.com/docs/ (For example: https://docs-preview.newrelic.com/docs/new-feature-name)
  8. Provide reviewers the official link to share with customers.

Optional boilerplate text

When writing a doc for preview, you may want to include a callout with boilerplate text at the top of the doc. This text can be used to orient your reader, providing them with important information about the feature's availability and relevant contact information.

For example, boilerplate text for a preview doc might read:

Preview

This feature was released on January 1, 202X and is in preview. To get access to it, reach out to your account manager.

You might want to exclude boilerplate text if the information is too lengthy, included elsewhere on the page, or irrelevant to the doc.

Additional guidance for internal contributors

As an internal contributor looking to edit a preview doc, you'll need access to the beta-docs-site repo. If you don't have access, ask the #doc-eng-help Slack channel to add you as a contributor. Once you have access, create your own branch off the main branch and make your edits there.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.