Replies: 1 comment
-
|
I found |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I want to create a second website that only shows articles of one category of my main blog. I would like to use the same Pelican setup because the articles are already there and the theme and config will also be really similar.
I tried to simply create a config that includes my two default config files and then changes PATH to the directory I use for the category I want to have on my second site (a subdirectory of
content):PATH=content/secondsite. However, this causes issues with linking static that I do not know how to solve.My images are in
content/images. I link them in posts with{static}/images. This works fine for the main site since the folders for the categories are not preserved, so images work for all posts no matter the location of the post's source file. For the second site, Pelican does not grab the images since they are not in PATH anymore.I thought I may leave out
{static}and instead useSTATIC_PATHSand have that different for the two sites, but paths are preserved when static files are copied. So since my images folder iscontent/imagesand for the second site I havePATH=content/secondsite, I will need to putSTATIC_PATHS=['../images']for the second site, resulting in the images folder being placed next to the output folder instead of inside it.How am I supposed to handle this situation?
Beta Was this translation helpful? Give feedback.
All reactions