Skip to content
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

Hugo extended edition required by default? #678

Open
mloskot opened this issue Mar 12, 2024 · 1 comment
Open

Hugo extended edition required by default? #678

mloskot opened this issue Mar 12, 2024 · 1 comment
Assignees

Comments

@mloskot
Copy link

mloskot commented Mar 12, 2024

I've read and learned this

#### Custom CSS
WARNING: Pending resolution of this [discussion](https://github.com/theNewDynamic/gohugo-theme-ananke/discussions/452#discussioncomment-1865301), Custom CSS only works with Hugo Extended

but using the latest

$ hugo version
hugo v0.123.8-5fed9c591b694f314e5939548e11cc3dcb79a79c linux/amd64 BuildDate=2024-03-07T13:14:42Z VendorInfo=gohugoio

and following the Hugo getting started tutorial together with

git submodule add https://github.com/budparr/gohugo-theme-ananke.git themes/ananke
echo 'theme = "ananke"' >> hugo.toml

I'm experiencing this:

image

Is this expected?

Replacing the standard Hugo with the extended Hugo fixes the problem, of course.

@davidsneighbour
Copy link
Collaborator

I always use the extended version for everything and think of the "regular" version as one we would use on slower, smaller systems where we have a finished theme and only content to transform.

I think the best solution in the future (in v2.12) will be to have a complete theme set compiled in static and, if we are working with the extended version of Hugo, to use the pipelines.

I am not 100% sure if that will work out of the box without configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants