Our blog based on hexo, mirror from Gitlab
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Natale Vinto 6012a59dba Moved presentations to public directory 2 years ago
scaffolds first commit 4 years ago
source/_posts fix identazione 3 years ago
themes Moved presentations to public directory 2 years ago
.gitignore first commit 4 years ago
.gitlab-ci.yml changed image to node 4.2.2 4 years ago
README.md test 3 years ago
_config.yml modifica link a evento 3 years ago
package.json css fix 3 years ago


Build Status

Example Hexo website using GitLab Pages.

Learn more about GitLab Pages at https://pages.gitlab.io and the official documentation http://doc.gitlab.com/ee/pages/README.html.

Table of Contents generated with DocToc

GitLab CI

This project's static Pages are built by GitLab CI, following the steps defined in .gitlab-ci.yml:

image: node:4.2.2

    - node_modules/

  - npm install hexo-cli -g
  - npm install
  - hexo deploy
    - public
  - master

Building locally

To work locally with this project, you'll have to follow the steps below:

  1. Fork, clone or download this project
  2. Install Hexo and Hexo Sever
  3. Install dependencies: npm install
  4. Preview your site: hexo server
  5. Add content
  6. Generate your site (optional): hexo generate

Read more at Hexo's documentation.

GitLab User or Group Pages

To use this project as your user/group website, you will need one additional step: just rename your project to namespace.gitlab.io, where namespace is your username or groupname. This can be done by navigating to your project's Settings.

Read more about user/group Pages and project Pages.

Did you fork this project?

If you forked this project for your own use, please go to your project's Settings and remove the forking relationship, which won't be necessary unless you want to contribute back to the upstream project.


  1. CSS is missing! That means two things:

    Either that you have wrongly set up the CSS URL in your templates, or your static generator has a configuration option that needs to be explicitly set in order to serve static assets under a relative URL.

Forked from @VeraKolotyuk