Replies: 1 comment 16 replies
-
Follow Hugo's site skeleton and keep themes override things separated. Note that in line with that, there's an integrations directory for integrations overrides. I'm not sure what's more intuitive (keep things separated or all in one place) and what setup minimizes possible conflicts best? |
Beta Was this translation helpful? Give feedback.
16 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hyas (or the respective file structure in create-hyas) instructs to put user customizations under
themes/my-XYZ-theme/
instead of just using the Hugo project's top-level dirs. IMHO this unnecessarily complicates the setup (two instead of one place for users to customize files). Any particular reason for this?Moving all the Hugo component folders from
themes/my-XYZ-theme/
two levels up would be more intuitive I think. It would also allow us to cut down module config by two entries per Hyas theme.Beta Was this translation helpful? Give feedback.
All reactions