Quo vadis? The port of the original [Material theme](https://github.com/squidfunk/mkdocs-material) has replicated nearly all of its features. A few are still missing but I've good news: the Hugo community is actively working on this issues. Maybe with the next release of Hugo we can abandon this list. Stay tuned.
## Localization
Currently, it is possible to collect all strings in a single place for easy customization. However, this only enables you to define all strings in a single language. This approach is quite limiting in terms of localization support. Therefore, I decided to wait for a native integration. This way we can avoid a second setup of all strings in your website.
Keep an eye on [#1734](https://github.com/spf13/hugo/issues/1734).
## Search
Beside third-party services, some hacky workarounds and Grunt-/Gulp-based scripts that only require unnecessary dependencies, future versions of Hugo will support the generation of a content index as a core feature.
This approach plays well with this theme since MkDocs does the same.
Keep an eye on [#1853](https://github.com/spf13/hugo/pull/1853).
## Contributing
Did you found an bug or you would like to suggest a new feature? I'm open for feedback. Please open a new [issue](https://github.com/digitalcraftsman/hugo-material-docs/issues) and let me know.
You're also welcome to contribute with [pull requests](https://github.com/digitalcraftsman/hugo-material-docs/pulls).
<h2id="welcome-to-aims-desktop">Welcome to AIMS Desktop</h2>
...
...
@@ -340,6 +344,7 @@ it up and running.</p>
<p>Furthermore, thanks to <ahref="https://gihub.com/spf13">Steve Francia</a> for creating Hugo and the <ahref="https://github.com/spf13/hugo/graphs/contributors">awesome community</a> around the project.</p>
<p>Quo vadis? The port of the original <a href="https://github.com/squidfunk/mkdocs-material">Material theme</a> has replicated nearly all of its features. A few are still missing but I&rsquo;ve good news: the Hugo community is actively working on this issues. Maybe with the next release of Hugo we can abandon this list. Stay tuned.</p>
<p>Currently, it is possible to collect all strings in a single place for easy customization. However, this only enables you to define all strings in a single language. This approach is quite limiting in terms of localization support. Therefore, I decided to wait for a native integration. This way we can avoid a second setup of all strings in your website.</p>
<p>Keep an eye on <a href="https://github.com/spf13/hugo/issues/1734">#1734</a>.</p>
<h2 id="search">Search</h2>
<p>Beside third-party services, some hacky workarounds and Grunt-/Gulp-based scripts that only require unnecessary dependencies, future versions of Hugo will support the generation of a content index as a core feature.</p>
<p>This approach plays well with this theme since MkDocs does the same.</p>
<p>Keep an eye on <a href="https://github.com/spf13/hugo/pull/1853">#1853</a>.</p>
<p>Did you found an bug or you would like to suggest a new feature? I&rsquo;m open for feedback. Please open a new <a href="https://github.com/digitalcraftsman/hugo-material-docs/issues">issue</a> and let me know.</p>
<p>You&rsquo;re also welcome to contribute with <a href="https://github.com/digitalcraftsman/hugo-material-docs/pulls">pull requests</a>.</p>
<p>Quo vadis? The port of the original <ahref="https://github.com/squidfunk/mkdocs-material">Material theme</a> has replicated nearly all of its features. A few are still missing but I’ve good news: the Hugo community is actively working on this issues. Maybe with the next release of Hugo we can abandon this list. Stay tuned.</p>
<h2id="localization">Localization</h2>
<p>Currently, it is possible to collect all strings in a single place for easy customization. However, this only enables you to define all strings in a single language. This approach is quite limiting in terms of localization support. Therefore, I decided to wait for a native integration. This way we can avoid a second setup of all strings in your website.</p>
<p>Keep an eye on <ahref="https://github.com/spf13/hugo/issues/1734">#1734</a>.</p>
<h2id="search">Search</h2>
<p>Beside third-party services, some hacky workarounds and Grunt-/Gulp-based scripts that only require unnecessary dependencies, future versions of Hugo will support the generation of a content index as a core feature.</p>
<p>This approach plays well with this theme since MkDocs does the same.</p>
<p>Keep an eye on <ahref="https://github.com/spf13/hugo/pull/1853">#1853</a>.</p>
<h2id="contributing">Contributing</h2>
<p>Did you found an bug or you would like to suggest a new feature? I’m open for feedback. Please open a new <ahref="https://github.com/digitalcraftsman/hugo-material-docs/issues">issue</a> and let me know.</p>
<p>You’re also welcome to contribute with <ahref="https://github.com/digitalcraftsman/hugo-material-docs/pulls">pull requests</a>.</p>
<p>Quo vadis? The port of the original <a href="https://github.com/squidfunk/mkdocs-material">Material theme</a> has replicated nearly all of its features. A few are still missing but I&rsquo;ve good news: the Hugo community is actively working on this issues. Maybe with the next release of Hugo we can abandon this list. Stay tuned.</p>
<p>Currently, it is possible to collect all strings in a single place for easy customization. However, this only enables you to define all strings in a single language. This approach is quite limiting in terms of localization support. Therefore, I decided to wait for a native integration. This way we can avoid a second setup of all strings in your website.</p>
<p>Keep an eye on <a href="https://github.com/spf13/hugo/issues/1734">#1734</a>.</p>
<h2 id="search">Search</h2>
<p>Beside third-party services, some hacky workarounds and Grunt-/Gulp-based scripts that only require unnecessary dependencies, future versions of Hugo will support the generation of a content index as a core feature.</p>
<p>This approach plays well with this theme since MkDocs does the same.</p>
<p>Keep an eye on <a href="https://github.com/spf13/hugo/pull/1853">#1853</a>.</p>
<p>Did you found an bug or you would like to suggest a new feature? I&rsquo;m open for feedback. Please open a new <a href="https://github.com/digitalcraftsman/hugo-material-docs/issues">issue</a> and let me know.</p>
<p>You&rsquo;re also welcome to contribute with <a href="https://github.com/digitalcraftsman/hugo-material-docs/pulls">pull requests</a>.</p>
