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

Image folder options #28

Open
mvsde opened this issue Jun 2, 2022 · 0 comments
Open

Image folder options #28

mvsde opened this issue Jun 2, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@mvsde
Copy link
Member

mvsde commented Jun 2, 2022

The images aren’t necessarily located in the base path in the source folder. For example they could also be directly in src/images if the source folder has a more “flat” folder structure. The above code forces you to put images in root/base/images.

Instead of a “two tier” folder structure where root and base are basically two ways to specify the asset’s root folder, we can use something similar to the fstack configuration.

Just one userOptions.assets.root option that can point to src/assets for example, or for those who want to put the assets directly into src, it can just be src.

For the output there can be a separate userOptions.assets.output that gets concatenated with Eleventy’s dir.output. This would keep input and output folder structure independent from each other (like in fstack with rootFolder and distFolder).

@mvsde mvsde added the enhancement New feature or request label Jun 2, 2022
dnnsjrng added a commit that referenced this issue Jun 2, 2022
Until issue #28 is solved properly we have to add a trailing slash to the assets_path to access the assets independend from the current path
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant