Our Docs site is made up of different content types and templates. Most of the time, the default page content type and the basic template will have everything you'll need.
Read on for more information about our page types.
Thr top of every doc begins with a set of metadata. Read on for more information about this metadata content:
Meta content field
Whenever possible, provide an action-oriented or task-oriented title; for example, "AJAX page: Identify time-consuming calls." In general, use sentence case. Capitalize only the first word. Do not capitalize any other word in the title unless it's a proper noun, such as a specific product name, or it follows a colon (:).
The title is also shown in the sidebar. Try to keep your titles as short as possible.
The title will automatically be converted to a file name, lower case, punctuation removed, with dashes between words.
For the basicDoc template, use page.
The template determines the basic layout and style of a page. Use basicDoc for more pages.
Keywords related to your doc. Start each topic with a
A topic can include multiple words separated by spaces.
The URL to the Japanese language version of the doc. Leave this blank if there isn't a Japanese version.
We use watermarks for things like beta content or to show that something is an internal New Relic doc. Commonly used watermarks are: BETA, Legacy, Deprecated, NR ONLY, etc.
Watermarks look like large, faded text behind the doc's content.
The document body is where you edit the page content. Use the GitHub Markdown format when you write content.
For most situations, use the basicDoc page template. Read on for information about our other page templates.
A standard HTML webpage without special fields. This content type is used for the majority of content on the site.
This format is for defining attributes and event types. These definitions are shared with the UI via the data dictionary service. For more information, see Work with attribute definition content type.
This format is for a more user-friendly and readable landing page, which replaces the standard taxonomy list views. For more information, see Working with landing pages.
This format includes specific fields for release notes.
This format is for troubleshooting docs in a Problem-Solution-Cause format. For more information, see Troubleshooting docs guide.