-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing menus #21
Comments
This is how Paige does it: https://github.com/willfaught/paige/blob/master/.github/workflows/pages.yml#L28-L29 Run hugo server in exampleSite, and tell it the path to the directory that contains Paige with --themesDir. For example: $ git clone ...
$ cd paige/exampleSite
$ hugo server --themesDir ../.. Edit: Changed checkout to clone |
Thanks for the prompt response. I can see that the site builds with the menus when I cd into |
I think I know what happened. I had both a |
OK, I’m glad it’s resolved. Note that the recommended way to install Paige is to import it as a module. See the readme instructions for that. |
Yes, I imported Paige as a module. The instructions were a bit confusing. I followed the Hugo Quickstart guide and then followed your installation instructions in the README. |
What was confusing about the Paige instructions? |
It wasn't clear whether I needed to follow the Hugo Quickstart to install the theme. It also wasn't clear that the |
Thanks, that's helpful. How did the config.yaml examples conflict? |
I thought the |
I'm going to keep this open for now. I plan to update the readme instructions to avoid this confusion. |
@jwp23 What do you think of the new setup section in the readme? You can see it live at https://github.com/willfaught/paige. Does that avoid the confusion? |
@willfaught That is clearer. One question I have is it necessary to use git submodules instructions int the hugo get started guide if you import the Paige module with the |
Importing as a module with hugo mod is separate from putting a copy of Paige into your themes directory with git submodule. The themes directory is the old way of doing things. Perhaps it’s confusing to include the Hugo getting started link at all. I use YAML for my own stuff, so I was thinking if you know Hugo, you’ll know that config.yaml and config.toml are equivalent. I guess that’s not clear if you don’t know Hugo well, and want to get started with Paige quickly. I suppose it would be clearer for the docs to use TOML too. I dislike TOML, but perhaps it’s worth ignoring that here. :) |
I'll have to try using the theme without using the git submodule. I think it's ok to use yaml for the documentation as long as it's clear that it's one or the other. I used a yaml to toml online converter to take your configuration samples and put it into my |
I converted the YAML to TOML in the readme: f599489 |
I also added links to Hugo's install and module guides. |
I'm going to close this, since I've made all the changes I planned. If you still see an issue, please reopen this or open a new issue. |
I am trying to install the theme and do not see the menu. I copied the
exampleSite
as outlined in #16 .When I run in the root directory of my repo the command
hugo server --source ./ --themesDir ./themes
I don't see the menu. I also tried
hugo server -D
and I get the same result
When I use the
exampleSite
directory in the theme, with the below command I see the menuhugo server --source ./themes/paige/exampleSite --themesDir ../..
The text was updated successfully, but these errors were encountered: