curben
/
blog
mirror of https://gitlab.com/curben/blog
1
0
Fork 0
Code Issues Releases Wiki Activity

Merge branch 'fix-readme' into 'master' 

removing 4th step - hexo generate

@axil 

I think it's better if we remove the step `hexo generate`, as we don't need to [generate](https://hexo.io/docs/generating.html) the site before [previewing](https://hexo.io/docs/server.html) with `hexo server`. 

We either `hexo generate --watch` or `hexo server` - I don't see why would we do both.

After adding our content, we could generate it, though.

Just my thoughts anyway...

Do you agree?

See merge request !2
This commit is contained in:
Virtua Creative 2016-04-06 13:31:46 +00:00
parent 5a784dcbe4 2d7a9050d4
commit f4e0c31ed1
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -50,11 +50,11 @@ pages:
To work locally with this project, you'll have to follow the steps below:
1. Fork, clone or download this project
1. [Install][] Hexo
1. [Install][] Hexo and [Hexo Sever][hexo-server]
1. Install dependencies: `npm install`
1. Generate the website: `hexo generate`
1. Preview your project: `hexo server`
1. Preview your site: `hexo server`
1. Add content
1. Generate your site (optional): `hexo generate`
Read more at Hexo's [documentation][].
@ -87,3 +87,4 @@ unless you want to contribute back to the upstream project.
[documentation]: https://hexo.io/docs/
[userpages]: http://doc.gitlab.com/ee/pages/README.html#user-or-group-pages
[projpages]: http://doc.gitlab.com/ee/pages/README.html#project-pages
[hexo-server]: https://hexo.io/docs/server.html