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.

Sign up for GitHub

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

Jump to bottom

Have all assets in content/:slug/assets folder instead of top level #22

Closed
saurabhdaware opened this issue Jun 6, 2020 · 0 comments · Fixed by #20
Closed

Have all assets in content/:slug/assets folder instead of top level #22

saurabhdaware opened this issue Jun 6, 2020 · 0 comments · Fixed by #20
Assignees
@saurabhdaware
Labels
enhancement New feature or request
Milestone
v1.0.0

Comments

@saurabhdaware
Copy link
Member

Describe the solution you'd like
A clear and concise description of what you want to happen.

Having images in content/:slug/ can make it difficult to track which are static files and which are only needed for build (meta.json, index.md etc).

By having all the images in content/:slug/assets, we can ignore files in top-level and make assets statically accessible.
@saurabhdaware saurabhdaware added the enhancement New feature or request label Jun 6, 2020
@saurabhdaware saurabhdaware self-assigned this Jun 6, 2020
@saurabhdaware saurabhdaware added this to the v1.0.0 milestone Jun 6, 2020
@saurabhdaware saurabhdaware mentioned this issue Jun 6, 2020
Merged
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@saurabhdaware saurabhdaware

Labels
enhancement New feature or request
Projects
None yet
Milestone
v1.0.0
Development

Successfully merging a pull request may close this issue.

v0.3.0 abelljs/abell
1 participant
@saurabhdaware