https://github.com/munin-monitoring/munin-monitoring.github.io

New website for the munin project.
https://github.com/munin-monitoring/munin-monitoring.github.io

Last synced: about 1 month ago
JSON representation

New website for the munin project.

• Host: GitHub
• URL: https://github.com/munin-monitoring/munin-monitoring.github.io
• Owner: munin-monitoring
• Created: 2016-09-26T12:43:09.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2023-12-31T16:36:04.000Z (12 months ago)
• Last Synced: 2024-03-26T10:15:11.945Z (9 months ago)
• Language: HTML
• Homepage: https://munin-monitoring.org
• Size: 1.04 MB
• Stars: 1
• Watchers: 8
• Forks: 6
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# munin-www

Munin's new website is built using Jekyll. Here are some side notes for contributors/curious:

## Local development environment

To install dependencies, please read [GitHub's documentation](https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/#requirements).

Once done, you'll be able to locally run this project using `bundle exec jekyll serve`. You can then open your favorite browser

& navigate to http://127.0.0.1:4000.

## Pages: page.md vs pages/index.html

For real basic pages, we use a page.md file. It allows to write its content in Markdown.

For more complex pages - the download page for example, the content is directly written in HTML.

In both cases, we use the `permalink` option to set its public address:

	permalink: /download/

## Writing pages

Here are some rules to writing pages:

- Titles should go from `
` to `
`. The `
` tag is reserved to page title and header logo.

- Do not start your page with `# My page title`. Page titles are already displayed by the `markdown-page` template.

- Assets (images or other related files) must be put in `/assets/{page_name}/`


### Table of Content

To insert a TOC at the top of a page, just use the following snippet:

	* TOC

    {:toc .pull-right}

## 301 Redirects

To avoid a lot of 404 errors due to external links pointing to legacy URLs, we have to setup some 301 redirect rules.

Since we're hosting this site on GitHub Pages, we cannot use a .htaccess file. See `redirect_from` directives in pages such as [`_pages/community.md`](/_pages/community.md).