Material is a theme for [Hugo](https://gohugo.io), a fast and flexible static site generator. It is built using Google's [material design](https://www.google.com/design/spec/material-design/introduction.html)
guidelines, fully responsive, optimized for touch and pointer devices as well
as all sorts of screen sizes.
AIMS Desktop is.... (collection of free software, math + science, debian based, etc)
Material is very lightweight – it is built from scratch using Javascript and
CSS that weighs less than 30kb (minified, gzipped and excluding Google Fonts
and Analytics). Yet, it is highly customizable and degrades gracefully in older
AIMS Desktop is free for anyone to use for educational, non-profit or commercial purposes. (See: Software Licences)
## Features
- Beautiful, readable and very user-friendly design based on Google's material
design guidelines, packed in a full responsive template with a well-defined
and [easily customizable color palette]({{<relref"getting-started/index.md#changing-the-color-palette">}}), great typography, as well as a
beautiful search interface and footer.
-
- Well-tested and optimized Javascript and CSS including a cross-browser
fixed/sticky header, a drawer that even works without Javascript using
the [checkbox hack](http://tutorialzine.com/2015/08/quick-tip-css-only-dropdowns-with-the-checkbox-hack/) with fallbacks, responsive tables that scroll when
the screen is too small and well-defined print styles.
-
- Extra configuration options like a [project logo]({{<relref"getting-started/index.md#adding-a-logo">}}), links to the authors
[GitHub and Twitter accounts]({{<relref"getting-started/index.md#adding-a-github-and-twitter-account">}}) and display of the amount of stars the
project has on GitHub.
-
- Web application capability on iOS – when the page is saved to the homescreen,
it behaves and looks like a native application.
-
See the [getting started guide]({{<relref"getting-started/index.md">}}) for instructions how to get
<ahref="mailto:aims-tech@aims.ac.za"title="Email of aims-tech@aims.ac.za">
Contact via email
</a>
</li>
</ul>
</div>
</div>
</div>
</nav>
</div>
<articleclass="article">
<divclass="wrapper">
<h1>Adding content </h1>
<h2id="hello-world">Hello world</h2>
<p>Let’s create our first content file for your documentation. Open a terminal and add the following command for each new file you want to add. Replace <code><section-name></code> with a general term that describes your document in detail.</p>
<pre><codeclass="language-sh">hugo new <section-name>/filename.md
</code></pre>
<p>Visitors of your website will find the final document under <code>www.example.com/<section-name>/filename/</code>.</p>
<p>Since it’s possible to have multiple content files in the same section I recommend to create at least one <code>index.md</code> file per section. This ensures that users will find an index page under <code>www.example.com/<section-name></code>.</p>
<h2id="homepage">Homepage</h2>
<p>To add content to the homepage you need to add a small indicator to the frontmatter of the content file:</p>
<pre><codeclass="language-toml">type: index
</code></pre>
<p>Otherwise the theme will not be able to find the corresponding content file.</p>
<h2id="table-of-contents">Table of contents</h2>
<p>You maybe noticed that the menu on the left contains a small table of contents of the current page. All <code><h2></code> tags (<code>## Headline</code> in Markdown) will be added automatically.</p>
<h2id="admonitions">Admonitions</h2>
<p>Admonition is a handy feature that adds block-styled side content to your documentation, for example hints, notes or warnings. It can be enabled by using the corresponding <ahref="http://gohugo.io/extras/shortcodes/">shortcodes</a> inside your content:</p>
<p>Let&rsquo;s create our first content file for your documentation. Open a terminal and add the following command for each new file you want to add. Replace <code>&lt;section-name&gt;</code> with a general term that describes your document in detail.</p>
<pre><code class="language-sh">hugo new &lt;section-name&gt;/filename.md
</code></pre>
<p>Visitors of your website will find the final document under <code>www.example.com/&lt;section-name&gt;/filename/</code>.</p>
<p>Since it&rsquo;s possible to have multiple content files in the same section I recommend to create at least one <code>index.md</code> file per section. This ensures that users will find an index page under <code>www.example.com/&lt;section-name&gt;</code>.</p>
