diff options
author | Ivan Boothe <git@rootwork.org> | 2022-05-18 02:03:37 +0300 |
---|---|---|
committer | Ivan Boothe <git@rootwork.org> | 2022-05-18 02:03:37 +0300 |
commit | beeb4b185b61e27d427226a87540e3737ddfa2e3 (patch) | |
tree | 44437216c4f87135367113d5b7369acd5d0f6c47 | |
parent | e5c72703a0b4d40e8155f8b56a26ea4a21e4ec7b (diff) |
more fix formatting
Signed-off-by: Ivan Boothe <git@rootwork.org>
-rw-r--r-- | README.md | 8 |
1 files changed, 6 insertions, 2 deletions
@@ -158,9 +158,11 @@ If you do already have a site and don't want to risk overwriting anything, we su hugo server ``` -If that seems like a lot of setup, it's meant to reduce the pain of pulling in new versions of Hugo Clarity when they are released. To pull in theme updates, run `hugo mod get -u github.com/chipzoller/hugo-clarity`. You can also update all your Hugo modules with `hugo mod get -u ./...`. [Read more about updating Hugo modules.](https://gohugo.io/hugo-modules/use-modules/#update-modules) +If that seems like a lot of setup, it's meant to reduce the pain of pulling in new versions of Hugo Clarity when they are released. -> There [is more you could do with hugo modules](https://github.com/rootwork/hugo-module-site), but this will suffice for our use case here. +To pull in theme updates, run `hugo mod get -u github.com/chipzoller/hugo-clarity`. You can also update all your Hugo modules with `hugo mod get -u ./...`. [Read more about updating Hugo modules.](https://gohugo.io/hugo-modules/use-modules/#update-modules) + +> There is [more you can do with hugo modules](https://github.com/rootwork/hugo-module-site), but this will suffice for our use case here. ### Option 3: Git submodules @@ -172,11 +174,13 @@ We assume you've already run `hugo new site <sitename>`, are in the `<sitename>` ```bash git submodule add https://github.com/chipzoller/hugo-clarity themes/hugo-clarity ``` + 2. Hugo Clarity comes with [`exampleSite` files](https://github.com/chipzoller/hugo-clarity/tree/master/exampleSite) prefilled with helpful configuration and sample posts. If you're starting a new Hugo site and don't have any content yet, it's easiest to grab the whole thing: ```bash cp -a themes/hugo-clarity/exampleSite/* . && rm -f config.toml ``` If you do already have a site and don't want to risk overwriting anything, we suggest copying the contents of [`config`](exampleSite/config/) over, as well as replacing your `archetypes/post.md` (if it exists) with [Hugo Clarity's](exampleSite/archetypes/post.md). Then migrate any necessary settings from `<sitename>/config.toml` to `<sitename>/config/_default/config.toml` and remove the original `<sitename>/config.toml` file. + 3. You can now run: ```bash hugo server |