1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
+++
title = "Installation"
description = ""
weight = 1
+++
{{% alert theme="warning" %}}HUGO **v0.50** minimum required to use this theme (prefer extended version if you want to modify this theme source{{%/alert%}}
{{% alert theme="info" %}}Last version of HUGO is recomended, tests are always done with the last version.{{%/alert%}}
The following steps are here to help you initialize your new website. If you don’t know Hugo at all, we strongly suggest you to train by following this [great documentation for beginners](https://gohugo.io/overview/quickstart/).
<!--more-->
## Installation
We assume that all changes to Hugo content and customizations are going to be tracked by git (GitHub, Bitbucket etc.). Develop locally, build on remote system.
Before start real work:
1. Initialize Hugo
2. Install DocPort theme
3. Configure DocPort and Hugo
### Prepare empty Hugo site
Create empty directory, which will be root of your Hugo project. Navigate there and let Hugo to create minimal required directory structure:
```
$ hugo new site .
```
After that, initialize this as git directory where to track further changes
```
$ git init
```
### Install DocPort
Next, there are at least three ways to install DocPort (first recommended):
1. **As git submodule**
2. As git clone
3. As direct copy (from ZIP)
Navigate to your themes folder in your Hugo site and use perform one of following scenarios.
#### 1. Install DocPort as git submodule
DocPort will be added like a dependency repo to original project. When using CI tools like Netlify, Jenkins etc., submodule method is required, or you will get `theme not found` issues. Same applies when building site on remote server trough SSH.
If submodule is no-go, use 3rd option.
On your root of Hugo execute:
```
$ git submodule add https://github.com/vjeantet/hugo-theme-docport.git themes/docport
```
Next initialize submodule for parent git repo:
```
$ git submodule init
$ git submodule update
```
Now you are ready to add content and customize looks. Do not change any file inside themes directory.
If you want to freeze changes to DocPort theme itself and use still submodules, fork private copy of DocPort and use that as submodule. When you are ready to update theme, just pull changes from origin to your private fork.
#### 2. Install DocPort simply as git clone
This method results that files are checked out locally, but won't be visible from parent git repo. Probably you will build site locally with `hugo` command and use result from `public/` on your own.
```
$ git clone https://github.com/vjeantet/hugo-theme-docport.git themes/docport
```
#### 3. Install DocPort from ZIP
All files from theme will be tracked inside parent repo, to update it, have to override files in theme. [{{%icon cloud_download%}} download zip](https://github.com/vjeantet/hugo-theme-docport/archive/master.zip) and extract inside `themes/`.
```
https://github.com/vjeantet/hugo-theme-docport/archive/master.zip
```
Name of theme in next step will be `hugo-theme-docport-master`, can rename as you wish.
## Configuration
[Follow instructions here]({{%relref "getting-start/configuration/_index.md"%}})
|
