Skip to content

violadelbono/documentation

 
 

Repository files navigation

iCub Tech Docs

🌐 Browse our online documentation.

⚠ This is an attempt to make available to the community useful information that are not present or easily accessible through our official documentation. Thus, at the time being, it is intended to be an ever-growing container that supports and integrates with the official resources.

📝 Importantly, you can contribute to these docs by fixing typos and proposing new additions (see below).

Contributing

Check out our CONTRIBUTING guidelines.

☁ Cloud Workflow

You can leverage on the following Cloud IDE's to quickly get a testing platform where to try out how the documentation is rendered.

First off, sign up for Gitpod using your GitHub credentials. You'll have 50 hours/month of free usage on public repositories. Also, remember to visit the Gitpod Integrations to make sure that all GitHub options are ticked in.

Then, install the Gitpod browser extension.

Click to enlarge
Click to enlarge

🔽 Local Workflow

💻 Install the environment yourself

If you prefer to work on the documentation on your own computer without using Cloud IDEs as described in the previous section, you need to install the following software packages:

Once you have installed them, just clone this repo, navigate to it and serve its content with the mkdocs serve command:

git clone https://github.com/icub-tech-iit/documentation
cd documentation
mkdocs serve

📦 Rely on package managers

In the next sections, we will describe in detail how to install the required dependencies using different package managers.

🐍 conda

You can use the conda-forge distribution to install the required dependencies on Linux, macOS or Windows. First of all you need a conda distribution, for example Miniforge3.

If you already have a conda distribution, just create a new environment (for example called mkdocs-env) and install in it the require dependencies:

conda create -n mkdocs-env
conda activate mkdocs-env
conda install --channel conda-forge mkdocs-material mkdocs-material-extensions pymdown-extensions

After the installation, whenever you need to test the website just activate the mkdocs-env environment and call mkdocs serve in the documentation directory:

cd documentation
conda activate mkdocs-env
mkdocs serve

Releases

No releases published

Packages

No packages published

Languages

  • Ruby 73.7%
  • Dockerfile 16.6%
  • Shell 9.7%