This section contains guidelines on naming files, sections, documents and other document elements.

NOTE: Some of the items are marked as TODO which will be documented later.

The HotFix branch name will be in the below pattern:

https://gitlab.syncfusion.com/content/blazor-docs/tree/hotfix/hotfix-v{last major release version}

For example the latest HotFix branch is: https://gitlab.syncfusion.com/content/blazor-docs/tree/hotfix/hotfix-v19.2.0.55

For Daily UG publishing to live

HotFix branch has been created for blazor-docs repository. hereafter use this HotFix branch to commit your daily changes as like ES.

https://gitlab.synthofusion.com/content/blazor-docs/tree/hotfix/hotfix-v19.2.0.55

We will merge the changes from HotFix to Master and publish to live from Master branch hereafter.

For release UG publishing (Main\SP)

You can use the development branch to commit the changes for Main\SP release.

We will merge development branch to Master during release time as like other ES platforms and publish to live from Master branch and create HotFix for next version

1. Staging

2. Live

All the md files in the documentation must contain the FrontMatter. FrontMatter must be given with following fields.

---
layout: post
title: Aggregates in Blazor DataGrid Component | Syncfusion
description: Learn here all about aggregates in Syncfusion Blazor DataGrid component and more.
platform: Blazor
control: DataGrid
documentation: ug
---

Refer the below guidelines for adding description, title and h1 tags.

Format+of+meta+elements+for+UG+pages

Also refer the below link for common validation errors and solution for this errors in below.

Front+Matter+validation+-+Guide

For Notes, warning, information syntax refer the below table

Refer the below guidelines to resolve spelling errors in the documentation.

Spelling - https://syncfusion.sharepoint.com/sites/DOCINFRA/SitePages/Spell%20Checker%20Automation%20-%20Guide.aspx

File name - https://syncfusion.sharepoint.com/sites/DOCINFRA/SitePages/File%20Path%20Validation%20%20Guidelines.aspx

• All files should have .md extension.
• Separate words in file names should be hyphenated
• File names of the documents should have one or two-word names that describe the material covered in the document.
• The full title of the document should be in the file name.
• Phrase title and description in a way that users can determine what questions the text will answer, and material that will be addressed, without reading the content. This eases the time spent looking for answers, and improvises search/scanning, and possibly SEO.
• Provide titles and headers in the form of “Using foo” over “How to Foo.”

For example, at the top section of each MD file,

Title : Getting started with Chart widget for Syncfusion Essential JS

Description : How to create a chart, add series, enable tooltip and other functionalities.

• Follow the syntax mentioned in this link for most of the elements. There are some elements which need special styling or additional settings to do. Those have been described in the below topics.

• Do not bold the words unnecessarily.
• Use inline code style wherever it is possible to highlight the keywords, variables or one line code examples that come within the paragraph.

• Link within the page (if you have a title with space, use hyphen (-))

Syntax: [Link name](#title-name)

Example: [How to best read this user guide] (#how-to-best-read-this-user-guide)

• Link to the other page within the same platform documentation (using relative path). Tooltip text is optional.

Syntax: [Link name](relative path "Tooltip text")

Example: [Barcode](/js/Barcode/Getting-Started "Barcode Getting Started")

• Use the kramdown syntax for creating the tables.
• Advanced tables: If you want to create an advanced tables with row span or column span or with code snippets, you can go with the standard html table syntax as described below.

1. start with <table> tag. Tag should be left indented and should have empty space in left side.

2. Provide TH tag for table headers.

3. Code snippet can include within <td> [code snippet] </td>. Follow the same pattern like code snippet.

• Do not provide table captions.
• You should use the below markdown syntax if you want to use markdown syntax within the html tags.

{{'' | markdownify }}

Example:

{{'[syncfusion](http://cdn.syncfusion.com/js/assets/external/jquery-1.10.2.min.js)'| markdownify }}

• Make sure image is not resized or blurred.

• Caption is not necessary to provide for all images except for the case where we will have displayed more than one image.

• Adding Image : General markdown syntax will work.

Syntax: 

Example: 

• Adding image with caption:

Syntax: {% include image.html url="image path" caption="caption text"%}

Example: {% include image.html url="/js/DatePicker/Appearance-and-Styling_images/Appearance-and-Styling_img2.png" caption="caption text"%}

• Maximum width of the image should be 750 PX
• Maximum height of the image should be 550 PX
• Image format should be either .jpeg or .png format
• Size of the image should not exceed 20 to 40 KB
• If you are including the image to show an output of a code block, make sure the exact output can see the user also when he executes the same code snippet.

• Refer this page for Code block syntax and supported languages.
• Align the code snippets using following free formatters: JS , HTML
• Remove extra lines added within the code block.
• Make sure the given code block runs without any issues.
• JSRender template syntax can be rendered by the following syntax :

{{"{{"}} code block here {{}}}}

• Refer the below page to know more about committing a code snippet file in the repository and syntax for using the code snippet file in the MD files.
• https://syncfusion.sharepoint.com/sites/Install/SitePages/Support%20for%20loading%20code%20snippet%20from%20a%20file.aspx

• For embedding the Youtube video link use the following pattern.

• Syntax: {% youtube "Link" %}

• Example: {% youtube "https://www.youtube.com/watch?9YF9HnFY5Ew" %}

• For Using the Razor code in the code snippet

• Syntax: {% highlight razor %} [CODE] {% endhighlight %}

• Example: {% highlight razor %}

@using Syncfusion.Blazor.Grids

<SfGrid DataSource="@Orders" AllowSorting="true" AllowPaging="true" AllowExcelExport="true" AllowPdfExport="true" ContextMenuItems="@(new List() { "AutoFit", "AutoFitAll", "SortAscending", "SortDescending","Copy", "Edit", "Delete", "Save", "Cancel","PdfExport", "ExcelExport", "CsvExport", "FirstPage", "PrevPage","LastPage", "NextPage"})"> . . .

@code{ . . . }

{% endhighlight %}

• Refer the syntax provided in the Kramdown site.
• Do not provide a line gap between the bullet points.

• To add the different type of predefined blockqoute use the below syntax. Since we will insert the title or relevant icon for this block of content, do not add the "Title".

Information or Notes

Syntax: I> [Content]

Example: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis volutpat, elit eget iaculis venenatis

Warning

Syntax: W> [Content]

Example: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis volutpat, elit eget iaculis venenatis

Errors

Syntax: E> [Content]

Example: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis volutpat, elit eget iaculis venenatis

Tips

Syntax: T> [Content]

Example: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis volutpat, elit eget iaculis venenatis

• Use the BR tag between the content to enable multiple paragraph style.

Tips

Syntax: T> [Content]

Example: Lorem ipsum dolor sit amet, consectetur adipiscing elit. **
**Duis volutpat, elit eget iaculis venenatis

• See also section can be added at the bottom of the page using the below syntax

Syntax: {% seealso %} [Content] {% endseealso %}

Example: {% seealso %} See the Cross Reference section {% endseealso %}

• Todo -> How to link the JS Playground link on top of the each code blocks?

• Enclose the each keys with <kbd> tag to display the keys with different styling. For ex, Ctrl+A .

• To add the version number in the documentation, use the below variables that replace the corresponding release version number while publishing. So that, always your content will contains the latest release version number.

• Use the JS API naming standards mentioned in the following page - API Naming Standards

Style Guide