campiaperti/documentazione
1
0
Fork 1
Code Issues Pull requests Releases Wiki Activity

disordini di navigazione

Browse source
This commit is contained in:
kiki 2018-12-17 16:25:12 +01:00
parent 5f89e83aca
commit e079c6198d
13 changed files with 126 additions and 725 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
_config.yml
View file

@ -36,7 +36,7 @@ exclude:
- .gitignore
# these are the files and directories that jekyll will exclude from the build
feedback_subject_line: Jekyll documentation theme
feedback_subject_line: Campi Aperti Documentazione
feedback_email: info@campiaperti.org
# used as a contact email for the Feedback link in the top navigation bar
@ -108,7 +108,7 @@ sidebars:
- product2_sidebar
- other
description: "Intended as a documentation theme based on Jekyll for technical writers documenting software and other technical products, this theme has all the elements you would need to handle multiple products with both multi-level sidebar navigation, tags, and other documentation features."
description: "Sito web con la documentazione della comunicazione interna ed esterna di Campi Aperti"
# the description is used in the feed.xml file
# needed for sitemap.xml file only

8
_data/sidebars/home_sidebar.yml
View file

@ -5,18 +5,18 @@ entries:
levels: one
folders:
- title: Products
- title: Argomenti
output: web
folderitems:
- title: News
url: /news.html
output: web
- title: Theme instructions
- title: Il server
url: /mydoc_introduction.html
output: web
- title: Product 1
- title: Prova 1
url: /p1_landing_page.html
output: web
- title: Product 2
- title: Prova 2
url: /p2_landing_page.html
output: web

259
_data/sidebars/mydoc_sidebar.yml
View file

@ -2,8 +2,8 @@
entries:
- title: sidebar
product: Jekyll Doc Theme
version: 6.0
product: Cosa bolle in pentola
version: 0.1
folders:
- title:
@ -19,16 +19,16 @@ entries:
output: pdf
type: frontmatter
- title: Overview
- title: Il server
output: web, pdf
folderitems:
- title: Get started
- title: Connettersi
url: /index.html
output: web, pdf
type: homepage
- title: Introduction
- title: Installare
url: /mydoc_introduction.html
output: web, pdf
@ -44,252 +44,3 @@ entries:
url: /mydoc_support.html
output: web, pdf
- title: Release Notes
output: web, pdf
folderitems:
- title: 6.0 Release notes
url: /mydoc_release_notes_60.html
output: web, pdf
- title: 5.0 Release notes
url: /mydoc_release_notes_50.html
output: web, pdf
- title: Installation
output: web, pdf
folderitems:
- title: About Ruby, Gems, Bundler, etc.
url: /mydoc_about_ruby_gems_etc.html
output: web, pdf
- title: Install Jekyll on Mac
url: /mydoc_install_jekyll_on_mac.html
output: web, pdf
- title: Install Jekyll on Windows
url: /mydoc_install_jekyll_on_windows.html
output: web, pdf
- title: Authoring
output: web, pdf
folderitems:
- title: Pages
url: /mydoc_pages.html
output: web, pdf
- title: Posts
url: /mydoc_posts.html
output: web, pdf
- title: Lists
url: /mydoc_lists.html
output: web, pdf
- title: Conditional logic
url: /mydoc_conditional_logic.html
output: web, pdf
- title: Content reuse
url: /mydoc_content_reuse.html
output: web, pdf
- title: Collections
url: /mydoc_collections.html
output: web, pdf
- title: WebStorm editor tips
url: /mydoc_webstorm_text_editor.html
output: web, pdf
- title: Atom editor tips
url: /mydoc_atom_text_editor.html
output: web, pdf
- title: Navigation
output: web, pdf
folderitems:
- title: Sidebar navigation
url: /mydoc_sidebar_navigation.html
output: web, pdf
- title: YAML tutorial in the context of Jekyll
url: /mydoc_yaml_tutorial.html
output: web, pdf
- title: Tags
url: /mydoc_tags.html
output: web, pdf
- title: Series
url: /mydoc_series.html
output: web, pdf
- title: Formatting
output: web, pdf
folderitems:
- title: Tooltips
url: /mydoc_adding_tooltips.html
output: web, pdf
- title: Alerts
url: /mydoc_alerts.html
output: web, pdf
- title: Icons
url: /mydoc_icons.html
output: web, pdf
- title: Images
url: /mydoc_images.html
output: web, pdf
- title: Code samples
url: /mydoc_code_samples.html
output: web, pdf
- title: Labels
url: /mydoc_labels.html
output: web, pdf
- title: Links
url: /mydoc_hyperlinks.html
output: web, pdf
- title: Navtabs
url: /mydoc_navtabs.html
output: web, pdf
- title: Tables
url: /mydoc_tables.html
output: web, pdf
- title: Syntax highlighting
url: /mydoc_syntax_highlighting.html
output: web, pdf
- title: Workflow maps
url: /mydoc_workflow_maps.html
output: web, pdf
- title: Handling reviews
output: web, pdf
folderitems:
- title: Commenting on files
url: /mydoc_commenting_on_files.html
output: web, pdf
# - title: Git collaboration
# url: /mydoc_git_collaboration
# output: web, pdf
- title: Publishing
output: web, pdf
folderitems:
- title: Build arguments
url: /mydoc_build_arguments.html
output: web, pdf
- title: Themes
url: /mydoc_themes.html
output: web, pdf
- title: Generating PDFs
url: /mydoc_generating_pdfs.html
output: web, pdf
- title: Help APIs and UI tooltips
url: /mydoc_help_api.html
output: web, pdf
- title: Search configuration
url: /mydoc_search_configuration.html
output: web, pdf
- title: iTerm profiles
url: /mydoc_iterm_profiles.html
output: web, pdf
- title: Pushing builds to server
url: /mydoc_push_build_to_server.html
output: web, pdf
- title: Publishing on Github Pages
url: /mydoc_publishing_github_pages.html
output: web, pdf
- title: Special layouts
output: web, pdf
folderitems:
- title: Knowledge-base layout
url: /mydoc_kb_layout.html
output: web, pdf
- title: Glossary layout
url: /mydoc_glossary.html
output: web, pdf
- title: FAQ layout
url: /mydoc_faq_layout.html
output: web, pdf
- title: Shuffle layout
url: /mydoc_shuffle.html
output: web, pdf
- title: Troubleshooting
output: web, pdf
folderitems:
- title: Troubleshooting
url: /mydoc_troubleshooting.html
output: web, pdf
- title: Tag archives
output: web
folderitems:
- title: Tag archives overview
url: /mydoc_tag_archives_overview.html
output: web
subfolders:
- title: Tag archive pages
output: web
subfolderitems:
- title: Formatting pages
url: /tag_formatting.html
output: web
- title: Navigation pages
url: /tag_navigation.html
output: web
- title: Content types pages
url: /tag_content_types.html
output: web
- title: Publishing pages
url: /tag_publishing.html
output: web
- title: Special layout pages
url: /tag_special_layouts.html
output: web
- title: Collaboration pages
url: /tag_collaboration.html
output: web
- title: Troubleshooting pages
url: /tag_troubleshooting.html
output: web

22
_data/topnav.yml
View file

@ -4,7 +4,7 @@ topnav:
- title: Topnav
items:
- title: Campi Aperti per l'autogestione alimentare
external_url: https://github.com/tomjoht/documentation-theme-jekyll
external_url: https://git.lattuga.net:campiaperti/documentazione.git
- title: News
url: /news
@ -12,21 +12,11 @@ topnav:
topnav_dropdowns:
- title: Topnav dropdowns
folders:
- title: Jekyll Help
- title: Argomenti
folderitems:
- title: Jekyll Talk
external_url: https://talk.jekyllrb.com
- title: Jekyll documentation
external_url: http://jekyllrb.com/docs/home/
- title: Jekyll on Stack Overflow
external_url: http://stackoverflow.com/questions/tagged/jekyll
- title: Jekyll on my blog
external_url: http://idratherbewriting.com/category-jekyll/
- title: Products
folderitems:
- title: Jekyll Documentation Theme
url: /mydoc_introduction.html
- title: Product 1
- title: Dispensa
url: /mydoc_server.html
- title: Prova 1
url: /p1_landing_page.html
- title: Product 2
- title: Prova 2
url: /p2_landing_page.html

10
_posts/2015-04-12-test-post-last-year.md
View file

@ -1,10 +0,0 @@
---
title: "Test post from last year"
categories: jekyll update
permalink: test-post-from-last-year.html
tags: [news]
---
This is just a test post from the previous year.
{% include links.html %}

19
_posts/2016-02-24-first-post.md
View file

@ -1,19 +0,0 @@
---
title: "Welcome to Jekyll!"
categories: jekyll update
permalink: myupdate.html
tags: [news]
---
Theme updates:
- Permalinks
- Kramdown
- URL specified in config file
- removed PDF output
- removed some of the alternative layouts
- added blog feature
- sidebars configurable per page
{% include links.html %}

17
_posts/2016-02-26-sample-post-jekyll.md
View file

@ -1,17 +0,0 @@
---
title: "Sample post"
published: true
permalink: samplepost.html
summary: "This is some summary frontmatter for my sample post."
tags: [news, getting_started]
---
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries
## Heading
but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries
{% include links.html %}

11
_posts/2018-12-17-inizio documentazione.md Normal file
View file

@ -0,0 +1,11 @@
---
title: "Scriviamo!"
permalink: scriviamo.html
tags: [news]
---
Visto i numerosi esperimenti di mezzi auto costruiti per comunicare, organizzarsi, distribuire video ed audio, farsi conoscere, archiviare, autocertificare la biologicità dei prodotti portati al mercato, ... siamo arrivate ad un punto in cui o le scriviamo tutte o impazziamo ed anche perchè a parte la comunicazione orale in cui eccelliamo :P le informazioni sono diventate così tanti e così obbligatoriamente puntuali, ovvero che non ci si può permettere di ricordare una cosa per un'altra.. che ci siamo convinte che sia giunto il momento di scriverel. Eccoci qui.
Con l'invito che chiunque legga sappia anche scrivere! :)
{% include links.html %}

411
index.md
View file

@ -1,410 +1,17 @@
---
title: "Getting started with the Documentation Theme for Jekyll"
keywords: sample homepage
tags: [getting_started]
sidebar: mydoc_sidebar
title: "Comunicazione Campi Aperti"
tags: [iniziare]
permalink: index.html
summary: These brief instructions will help you get started quickly with the theme. The other topics in this help provide additional information and detail about working with other aspects of this theme and Jekyll.
---
{% include note.html content="If you're cloning this theme, you're probably writing documentation of some kind. I have a blog on technical writing here called <a alt='technical writing blog' href='http://idratherbewriting.com'>I'd Rather Be Writing</a>. If you'd like to stay updated with the latest trends, best practices, and other methods for writing documentation, consider <a href='https://tinyletter.com/tomjoht'>subscribing</a>. I also have a site on <a href='http://idratherbewriting.com/learnapidoc'>writing API documentation</a>." %}
## Cosa c'è in campo.. comunicazione
## Build the Theme
Si parla di tecnologia e di come la usiamo per i nostri scopi: il mutualismo, la solidarietà e l'autogestione alimentare. Questa documentazione serve a condividerla e a far si che non ci divida per capacità tecniche ma anzi ci unisca nello scambio di conoscenze e nella distribuzione del potere dato da esse.
Follow these instructions to build the theme.
### 1. Download the theme
First, download or clone the theme from the [Github repo](https://github.com/tomjoht/documentation-theme-jekyll). Most likely you won't be pulling in updates once you start customizing the theme, so downloading the theme (instead of cloning it) probably makes the most sense. In Github, click the **Clone or download** button, and then click **Download ZIP**.
### 2. Install Jekyll
If you've never installed or run a Jekyll site locally on your computer, follow these instructions to install Jekyll:
* [Install Jekyll on Mac][mydoc_install_jekyll_on_mac]
* [Install Jekyll on Windows][mydoc_install_jekyll_on_windows]
### 3. Install Bundler
In case you haven't installed Bundler, install it:
```
gem install bundler
```
You'll want [Bundler](http://bundler.io/) to make sure all the Ruby gems needed work well with your project. Bundler sorts out dependencies and installs missing gems or matches up gems with the right versions based on gem dependencies.
### 4. Option 1: Build the Theme (*without* the github-pages gem) {#option1}
Use this option if you're not planning to publish your Jekyll site using [Github Pages](https://pages.github.com/).
Bundler's Gemfile specifies how project dependencies are managed. Although this project includes a Gemfile, this theme doesn't have any dependencies beyond core Jekyll. The Gemfile is used to list gems needed for publishing on Github Pages. **If you're not planning to have Github Pages build your Jekyll project, delete these two files from the theme's root directory:**
* Gemfile
* Gemfile.lock
If you've never run Jekyll on your computer (you can check with `jekyll --version`), you may need to install the jekyll gem:
```
gem install jekyll
```
Now run jekyll serve (first change directories (`cd`) to where you downloaded the project):
```
jekyll serve
```
### 4. Option 2: Build the Theme (*with* the github-pages gem) {#option2}
If you *are* in fact publishing on Github Pages, leave the Gemfile and Gemfile.lock files in the theme.The Gemfile tells Jekyll to use the github-pages gem. **However, note that you cannot use the normal `jekyll serve` command with this gem due to dependency conflicts between the latest version of Jekyll and Github Pages** (which are noted [briefly here](https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/)).
You need Bundler to resolve these dependency conflicts. Use Bundler to install all the needed Ruby gems:
```
bundle update
```
Then *always* use this command to build Jekyll:
```
bundle exec jekyll serve
```
If you want to shorten this long command, you can put this code in a file such as jekyll.sh (on a Mac) and then simply type `. jekyll.sh` to build Jekyll.
## Running the site in Docker
You can also use Docker to directly build and run the site on your local machine. Just clone the repo and run the following from your working dir:
```
docker-compose build --no-cache && docker-compose up
```
The site should now be running at [http://localhost:4000/](http://localhost:4000/).
This is perhaps the easiest way to see how your site would actually look.
## Configure the sidebar
There are several products in this theme. Each product uses a different sidebar. This is the essence of what makes this theme unique -- different sidebars for different product documentation. The idea is that when users are reading documentation for a specific product, the sidebar navigation should be specific to that product. (You can read more of my thoughts on why multiple sidebars are important in this [blog post](http://idratherbewriting.com/2016/03/23/release-of-documentation-theme-for-jekyll-50/).)
The top navigation usually remains the same, because it allows users to navigate across products. But the sidebar navigation adapts to the product.
In each page's frontmatter, you must specify the sidebar you want that page to use. Here's an example of the page frontmatter showing the sidebar property:
<pre>
---
title: Alerts
tags: [formatting]
keywords: notes, tips, cautions, warnings, admonitions
last_updated: July 3, 2016
summary: "You can insert notes, tips, warnings, and important alerts in your content. These notes are stored as shortcodes made available through the linksrefs.hmtl include."
<span class="red">sidebar: mydoc_sidebar</span>
permalink: mydoc_alerts
---
</pre>
The `sidebar: mydoc_sidebar` refers to the \_data/sidebars/mydoc_sidebar.yml file.
Note that your sidebar can only have 2 levels (expand the **Tag archives** option to see an example of the second level). Given that each product has its own sidebar, this depth should be sufficient (it's really like 3 levels). Deeper nesting goes against usability recommendations.
You can optionally turn off the sidebar on any page (e.g. landing pages). To turn off the sidebar for a page, you should set the page frontmatter tag as `hide_sidebar: true`.
If you don't declare a sidebar, the `home_sidebar` file gets used as the default because this is the default specified in the config file:
```yaml
-
scope:
path: ""
type: "pages"
values:
layout: "page"
comments: true
search: true
sidebar: home_sidebar
topnav: topnav
```
If you want to set different sidebar defaults based on different folders for your pages, specify your defaults like this:
```
-
scope:
path: "pages/mydoc"
type: "pages"
values:
layout: "page"
comments: true
search: true
sidebar: mydoc_sidebar
topnav: topnav
```
This would load the `mydoc_sidebar` for each file in **pages/mydoc**. You could set different defaults for different path scopes.
For more detail on the sidebar, see [Sidebar navigation][mydoc_sidebar_navigation].
## Top navigation
The top navigation works just like the sidebar. You can specify which topnav data file should load by adding a `topnav` property in your page, like this:
```yaml
topnav: topnav
```
Here the topnav refers to the `_data/topnav.yml` file.
Because most topnav options will be the same, the `_config.yml` file specifies the topnav file as a default:
```yaml
-
scope:
path: ""
type: "pages"
values:
layout: "page"
comments: true
search: true
sidebar: home_sidebar
topnav: topnav
```
## Sidebar syntax
The sidebar data file uses a specific YAML syntax that you must follow. Follow the sample pattern shown in the theme, specically looking at `mydoc_sidebar.yml` as an example: Here's a code sample showing all levels:
```yaml
entries:
- title: sidebar
product: Jekyll Doc Theme
version: 6.0
folders:
- title: Overview
output: web, pdf
folderitems:
- title: Get started
url: /index.html
output: web, pdf
type: homepage
- title: Introduction
url: /mydoc_introduction.html
output: web, pdf
- title: Release Notes
output: web, pdf
folderitems:
- title: 6.0 Release notes
url: /mydoc_release_notes_60.html
output: web, pdf
- title: 5.0 Release notes
url: /mydoc_release_notes_50.html
output: web, pdf
- title: Tag archives
output: web
folderitems:
- title: Tag archives overview
url: /mydoc_tag_archives_overview.html
output: web
subfolders:
- title: Tag archive pages
output: web
subfolderitems:
- title: Formatting pages
url: /tag_formatting.html
output: web
- title: Navigation pages
url: /tag_navigation.html
output: web
- title: Content types pages
url: /tag_content_types.html
output: web
```
Each `folder` or `subfolder` must contain a `title` and `output` property. Each `folderitem` or `subfolderitem` must contain a `title`, `url`, and `output` property.
The two outputs available are `web` and `pdf`. (Even if you aren't publishing PDF, you still need to specify `output: web`).
The YAML syntax depends on exact spacing, so make sure you follow the pattern shown in the sample sidebars. See my [YAML tutorial](mydoc_yaml_tutorial) for more details about how YAML works.
{% include note.html content="If you have just one character of spacing off, Jekyll won't build due to the YAML syntax error. You'll see an error message in your console that says \"Error ... did not find expected key while parsing a block mapping at line 22 column 5. Error: Run jekyll build --trace for more information.\" If you encounter this, it usually refers to incorrect indentation or spacing in the YAML file. See the example mydoc_sidebar.yml file to see where your formatting went wrong." %}
Each level must have at least one topic before the next level starts. You can't have a second level that contains multiple third levels without having at least one standalone topic in the second level. If you need a hierarchy that has a folder that contains other folders and no loose topics, use a blank `-` item like this:
```yaml
entries:
- title: sidebar
product: Jekyll Doc Theme
version: 6.0
folders:
- title: Overview
output: web, pdf
folderitems:
-
- title: Release Notes
output: web, pdf
folderitems:
- title: 6.0 Release notes
url: /mydoc_release_notes_60.html
output: web, pdf
- title: 5.0 Release notes
url: /mydoc_release_notes_50.html
output: web, pdf
- title: Installation
output: web, pdf
folderitems:
- title: About Ruby, Gems, Bundler, etc.
url: /mydoc_about_ruby_gems_etc.html
output: web, pdf
- title: Install Jekyll on Mac
url: /mydoc_install_jekyll_on_mac.html
output: web, pdf
- title: Install Jekyll on Windows
url: /mydoc_install_jekyll_on_windows.html
output: web, pdf
```
To accommodate the title page and table of contents in PDF outputs, each product sidebar must list these pages before any other:
```yaml
- title:
output: pdf
type: frontmatter
folderitems:
- title:
url: /titlepage
output: pdf
type: frontmatter
- title:
url: /tocpage
output: pdf
type: frontmatter
```
Leave the output as `output: pdf` for these frontmatter pages so that they don't appear in the web output.
For more detail on the sidebar, see [Sidebar navigation][mydoc_sidebar_navigation] and [YAML tutorial][mydoc_yaml_tutorial].
## Relative links and offline viewing
This theme uses relative links throughout so that you can view the site offline and not worry about which server or directory you're hosting it. It's common with tech docs to push content to an internal server for review prior to pushing the content to an external server for publication. Because of the need for seamless transferrence from one host to another, the site has to use relative links.
To view pages locally on your machine (without the Jekyll preview server), they need to have the `.html` extension. The `permalink` property in the page's frontmatter (without surrounding slashes) is what pushes the files into the root directory when the site builds.
## Page frontmatter
When you write pages, include these same frontmatter properties with each page:
```yaml
---
title: "Some title"
tags: [sample1, sample2]
keywords: keyword1, keyword2, keyword3
last_updated: Month day, year
summary: "optional summary here"
sidebar: sidebarname
permalink: filename.html
---
```
(You will customize the values for each of these properties, of course.)
For titles, surrounding the title in quotes is optional, but if you have a colon in the title, you must surround the title with quotation marks. If you have a quotation mark inside the title, escape it first with a backlash `\`.
Values for `keywords` get populated into the metadata of the page for SEO.
Values for `tags` must be defined in your \_data/tags.yml list. You also need a corresponding tag file inside the tags folder that follows the same pattern as the other tag files shown in the tags folder. (Jekyll won't auto-create these tag files.)
If you don't want the mini-TOC to show on a page (such as for the homepage or landing pages), add `toc: false` in the frontmatter.
The `permalink` value should be the same as your filename and include the ".html" file extension.
For more detail, see [Pages][mydoc_pages].
## Where to store your documentation topics
You can store your files for each product inside subfolders following the pattern shown in the theme. For example, product1, product2, etc, can be stored in their own subfolders inside the \_pages directory. Inside \_pages, you can store your topics inside sub-subfolders or sub-sub-folders to your heart's content. When Jekyll builds your site, it will pull the topics into the root directory and use the permalink for the URL.
Note that product1, product2, and mydoc are all just sample content to demonstrate how to add multiple products into the theme. You can freely delete that content.
For more information, see [Pages][mydoc_pages] and [Posts][mydoc_posts].
## Configure the top navigation
The top navigation bar's menu items are set through the \_data/topnav.yml file. Use the top navigation bar to provide links for navigating from one product to another, or to navigate to external resources.
For external URLs, use `external_url` in the item property, as shown in the example topnav.yml file. For internal links, use `url` the same was you do in the sidebar data files.
Note that the topnav has two sections: `topnav` and `topnav_dropdowns`. The topnav section contains single links, while the `topnav_dropdowns` section contains dropdown menus. The two sections are independent of each other.
## Generating PDF
If you want to generate PDF, you'll need a license for [Prince XML](http://www.princexml.com/). You will also need to [install Prince](http://www.princexml.com/doc/installing/). You can generate PDFs by product (but not for every product on the site combined together into one massive PDF). Prince will work even without a license, but it will imprint a small Prince image on the first page, and you're supposed to buy the license to use it.
If you're on Windows, install [Git Bash client](https://git-for-windows.github.io/) rather than using the default Windows command prompt.
Open up the css/printstyles.css file and customize the email address (`youremail@domain.com`) that is listed there. This email address appears in the bottom left footer of the PDF output. You'll also need to create a PDF configuration file following the examples shown in the pdfconfigs folder, and also customize some build scripts following the same pattern shown in the root: pdf-product1.sh
See the section on [Generating PDFs][mydoc_generating_pdfs] for more details about setting the theme up for this output.
## Blogs / News
For blog posts, create your markdown files in the \_posts folder following the sample formats. Post file names always begin with the date (YYYY-MM-DD-title).
The news/news.html file displays the posts, and the news_archive.html file shows a yearly history of posts. In documentation, you might use the news to highlight product features outside of your documentation, or to provide release notes and other updates.
See [Posts][mydoc_posts] for more information.
## Markdown
This theme uses [kramdown markdown](http://kramdown.gettalong.org/). kramdown is similar to Github-flavored Markdown, except that when you have text that intercepts list items, the spacing of the intercepting text must align with the spacing of the first character after the space of a numbered list item. Basically, with your list item numbering, use two spaces after the dot in the number, like this:
```
1. First item
2. Second item
3. Third item
```
When you want to insert paragraphs, notes, code snippets, or other matter in between the list items, use four spaces to indent. The four spaces will line up with the first letter of the list item (the <b>F</b>irst or <b>S</b>econd or <b>T</b>hird).
```
1. First item
```
alert("hello");
```
2. Second item
Some pig!
3. Third item
```
See the topics under "Formatting" in the sidebar for more information.
## Automated links
If you want to use an automated system for managing links, see [Automated Links][mydoc_hyperlinks.html#automatedlinks]. This approach automatically creates a list of Markdown references to simplify linking.
## Other instructions
The content here is just a getting started guide only. For other details in working with the theme, see the various sections in the sidebar.
* circa 7 persone dedicate, un tra i cento ed i duecento coinvolti quotidianamente
* 1 sito web
* circa 12 mailing list
* una rete wireless in Val Samoggia condivisa su 15 persone in 4 nodi
* 1 dispensa online condivisa (il nostro server)
{% include links.html %}

30
pages/mydoc/manutenzione/mydoc_about.md Normal file
View file

@ -0,0 +1,30 @@
---
title: Installazione del server di Campiaperti
sidebar: mydoc_sidebar
summary: "Installazione di una macchina per i dati della comunità - about"
permalink: mydoc_about.html
folder: mydoc
---
# Archivio Online
A che ci serve, appunto ad avere una dispensa online dove tenere le varie carte che ci servono e non impazzire.
Visto che alcune cose sono riservate dell'associazione abbiamo deciso in pieno stile Campi Aperti di non ricorrere a servizi commerciali ma di dare fiducia ad un esperimento di gestione collettiva di una macchina online.. appunto il server.
Abbiam deciso quindi di: cercare un gruppo etico di persone che si dedicano alle telecomunicazioni e che ci ospiti la macchina in un datacenter,
ovver un luogo con connettività ad internet ed elettricità e raffreddamento. E con poca umidità.
Su questa macchina virtuale gentilmente offerta da Tetaneutral, appunto un Gruppo di acquisto di banda internet, autogestito dalle persone.
Ci è sembrata la cosa più simile a noi in termini di idee di auto organizzazione.
Quindi a grandi linee le scelte progettuali e tecnologiche fatte sono:
* Sistema operativo Debian
* Docker
* Nextcloud
Seguiranno aggiornamenti :)
# Nel pratico
{% include links.html %}

3
pages/mydoc/mydoc_about.md
View file

@ -1,6 +1,7 @@
---
title: Installazione del server di Campiaperti
summary: "Installazione di una macchina per i dati della comunità"
sidebar: mydoc_sidebar
summary: "Installazione di una macchina per i dati della comunità - about"
permalink: mydoc_about.html
folder: mydoc
---

30
pages/mydoc/mydoc_installazione.md Normal file
View file

@ -0,0 +1,30 @@
---
title: Installazione
sidebar: mydoc_sidebar
permalink: mydoc_installazione.html
folder: mydoc
---
## Overview
This site provides documentation, training, and other notes for the Jekyll Documentation theme. There's a lot of information about how to do a variety of things here, and it's not all unique to this theme. But by and large, understanding how to do things in Jekyll depends on how your theme is coded. As a result, these additional details are provided.
The instructions here are geared towards technical writers working on documentation. You may have a team of one or more technical writers working on documentation for multiple projects. You can use this same theme to author all of your documentation for each of your products. The theme is built to accommodate documentation for multiple products on the same site.
## Survey of features
Some of the more prominent features of this theme include the following:
* Bootstrap framework
* [Navgoco multi-level sidebar](http://www.komposta.net/article/navgoco) for table of contents
* Ability to specify different sidebars for different products
* Top navigation bar with drop-down menus
* Notes, tips, and warning information notes
* Tags for alternative navigation
* Advanced landing page layouts from the [Modern Business theme](http://startbootstrap.com/template-overviews/modern-business/).
## Getting started
To get started, see [Getting Started][index].
{% include links.html %}

27
pages/mydoc/mydoc_server.md Normal file
View file

@ -0,0 +1,27 @@
---
title: Installazione del server di Campiaperti
sidebar: mydoc_sidebar
summary: "Installazione di una macchina per i dati della comunità - server"
permalink: mydoc_server.html
folder: mydoc
---
# Archivio Online
A che ci serve, appunto ad avere una dispensa online dove tenere le varie carte che ci servono e non impazzire.
Visto che alcune cose sono riservate dell'associazione abbiamo deciso in pieno stile Campi Aperti di non ricorrere a servizi commerciali ma di dare fiducia ad un esperimento di gestione collettiva di una macchina online.. appunto il server.
Abbiam deciso quindi di: cercare un gruppo etico di persone che si dedicano alle telecomunicazioni e che ci ospiti la macchina in un datacenter,
ovver un luogo con connettività ad internet ed elettricità e raffreddamento. E con poca umidità.
Su questa macchina virtuale gentilmente offerta da Tetaneutral, appunto un Gruppo di acquisto di banda internet, autogestito dalle persone.
Ci è sembrata la cosa più simile a noi in termini di idee di auto organizzazione.
Quindi a grandi linee le scelte progettuali e tecnologiche fatte sono:
* Sistema operativo Debian
* Docker
* Nextcloud
{% include links.html %}