-
|
Hi! I have a couple of questions regarding Bookshop components:
Thanks so much for your help! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
You don't necessarily need to create separate modules for your own custom Bookshop components. Hinode uses Bookshop's folder structure as a reference. You can either mount your own files in the same way, or use the target folders to override the default Hinode assets. You can see the mount configuration here: hinode/config/_default/hugo.toml Lines 141 to 162 in 5b2b996 Bookshop will pick up the defined components "automagically". However, you may want to update bookshop.scss to include your custom stylesheet. As an example, you can create a custom file |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much. That all sounds quite logical, but I still can’t seem to get it working. I’ve been experimenting a bit to understand how it works and discovered the following:
Is my approach incorrect? What am I doing wrong? Thank you so much in advance!! I feel completely stuck 😊 |
Beta Was this translation helpful? Give feedback.
-
|
Both your examples use the The hugo mount documentation is not very exhaustive, so I can imagine it's challenging to get it to work immediately. It still gives my headaches sometimes... In general, the mounts as defined in the Hinode module do not apply to your own project. |
Beta Was this translation helpful? Give feedback.
Both your examples use the
/component-library/as the base directory, so you need to mount the files as mentioned in my initial reaction. You can copy the mount config from the Hinode repository to your own project configuration (e.g.config/_default/hugo.toml). Alternatively, you can override the files by copying them to the mount target(s).The hugo mount documentation is not very exhaustive, so I can imagine it's challenging to get it to work immediately. It still gives my headaches sometimes... In general, the mounts as defined in the Hinode module do not apply to your own project.