Thanks for taking the time to contribute!🎉 You can find a list of issues you can work on here. Feel free to create new ones.
In general, the contribution workflow looks like this:
-
Fork the repo.
-
Create a new feature branch based off the
masterbranch.
Branch name examples:
feature/materialsfeature/algolia-search
- Submit a pull request, referencing any issues it addresses.
To create commit messages use general commits convention
Please try to keep your pull request focused in scope and avoid including unrelated commits.
You can read more about contributing here.
All materials are stored in the directory src/pages.
Site Navigation = structure in this directory (If correctly describe files with materials)
There are some options to configure page:
- title
- templateKey
- order
- isNavRoot
- navTitle
---
title: Комментарии
templateKey: 'article-page'
order: 10
---Required
Page Title. Also used as Page main Header
Required
The Template that is used to render the page.
Generally you have to use article-page temlate - template of simple article
Also there are section-page and contents-page templates.
Optional
Title of a navigation Link to the Page.
If not defined, used title
Optional
The number in order the page link should be displayed in navigation.
You have to define this option if order is important
Optional
Defines root of navigation for all child links.
When navigation bar is being rendering on some page, it finds the closest parent link with isNavroot: true and shows navogation starting with it.
Navigation starts from /dictionaries. Not from /
If you add an internal site link to materials (for example, link to another materials on the site), DON`T use simple link as
[linkTitle](https://...)It is rendered as simple tag <a> and disable static navigation (page reloads when you follow that link)
Use the following construct instead:
<gatsby-link to="/[some relative path]">link title</gatsby-link>