# Starting pages It is good for your readers and for SEO to provide an overview of you documentation and separate sections. These overviews group the most useful and popular topics or those dedicated to a specific subject. You can also use it to provide a learning path for readers: where to begin, which topics are generic and which are more advanced or cover some specific subsystem. Consider using the starting page markup for the [home page](table-of-contents.html#define_the_home_page) and for any [group of related TOC elements](table-of-contents.html#topic_order_and_hierarchy). The home page of this help is a good example of an overview starting page: [Discover Writerside](discover-writerside.html). > **Note:** > Starting pages are not supported for documentation published on the [JetBrains Marketplace](https://plugins.jetbrains.com/). > **Note:** > If the [<section-starting-page>](semantic-markup-reference.html#section-starting-page) element is present in a topic, Writerside considers it a starting page topic and ignores all other content outside the starting page element. > > > > For this reason, the starting page markup is not allowed in Markdown topics. Use only XML topics for starting pages. For more information, see [Topic formats](topics.html#topic_formats). Procedure: Convert topic to starting page * Add the [<section-starting-page>](semantic-markup-reference.html#section-starting-page) element to the root [<topic>](semantic-markup-reference.html#topic) element. Procedure: Create new starting page * Select the Section starting page template when [creating a topic](add-a-topic.html#create-from-template). Here is an example of a starting page topic markup: ```XML Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed condimentum feugiat sagittis. ... ... ... ... ... ... ``` The [<section-starting-page>](semantic-markup-reference.html#section-starting-page) element has some predefined structure: * Use the [<spotlight>](semantic-markup-reference.html#spotlight) element for two of the most important topics. * Use the [<primary>](semantic-markup-reference.html#primary) and [<secondary>](semantic-markup-reference.html#secondary) elements for other important and useful topics. * If necessary, use the [<misc>](semantic-markup-reference.html#misc) element for additional relevant topics. Add groups of [<links>](semantic-markup-reference.html#links) and [<cards>](semantic-markup-reference.html#cards) . For links, use the [<group>](semantic-markup-reference.html#group) element to split them into groups of links. By default, additional miscellaneous groups are rendered in two columns. Add `narrow="true"` to a group if you want to render it in three narrow columns instead For every ``, you can add an icon, image, or badge: * Use the `icon` attribute to specify a custom image that will be rendered as a small icon on the card. * Use the `image` attribute to specify a custom image that will take up the whole top part of the card. * Use the `badge` attribute to specify one of the built-in badges included with Writerside. The following built-in badges are available: *  `academy` *  `account` *  `branch` *  `bug` *  `case` *  `check-list` *  `cloud` *  `community` *  `computer` *  `container` *  `creative` *  `cross-check` *  `cross-platform` *  `cup` *  `data` *  `development` *  `documents` *  `experiment` *  `file` *  `filtering` *  `folder` *  `idea` *  `install` *  `integration` *  `key` *  `keyboard` *  `learn` *  `library` *  `location` *  `lock` *  `mail` *  `mixed` *  `navigation` *  `network` *  `offer` *  `open-source` *  `presentation` *  `search` *  `server` *  `settings` *  `start` *  `support` *  `thumb-up` *  `tools` *  `top` *  `turn-on` *  `world`