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

Can't find assets directory? #65

Closed
cormullion opened this issue Mar 5, 2024 · 7 comments
Closed

Can't find assets directory? #65

cormullion opened this issue Mar 5, 2024 · 7 comments

Comments

@cormullion
Copy link

My attempt at a build is erroring because it can't find an assets directory:

┌ Warning: DocumenterVitepress: no assets directory found.
└ @ DocumenterVitepress ~/.julia/packages/DocumenterVitepress/SZzuS/src/writer.jl:228

...

build error:
RollupError: Could not resolve "./assets/figures/f.gif" from "build/.documenter/basics.md"

although it's unchanged from the usual Documenter.jl structure:

docs
└───src
    └───basics.md
    └───index.md
    └───.vitepress
        └───config.mts
    └───assets
        └───logo.png
        └───logo.svg
        └───styles.css
        └───figures
            └───f.gif
    └───reference
        └───api.md
        └───functionindex.md

Is there some configuration option I've overlooked?

@lazarusA
Copy link
Collaborator

lazarusA commented Mar 5, 2024

Repo? Branch?

@asinghvi17
Copy link
Collaborator

asinghvi17 commented Mar 5, 2024

ah, the issue here is that we move the files in the src/assets folder into .documenter/public during the build step. I can walk that change back and only copy files matching logo.* and favicon into public instead.

@cormullion
Copy link
Author

Yes, I'm using Markdown links such as ![ alt text](assets/figures/figure.svg) (Documenter-style). I'm hoping that I wouldn't have to rewrite them all.

@lazarusA
Copy link
Collaborator

lazarusA commented Mar 6, 2024

I see. Yes, I have the same issue. Going from assets to public (replacing/ renaming) its confusing. Maybe it should be better to keep assets as assets :D, and create the extra folder public in docs? and then copy both? public is mandatory in vitepress ....

@asinghvi17
Copy link
Collaborator

@cormullion could you try your build on the latest master?

@cormullion
Copy link
Author

Works perfectly!

Screenshot 2024-03-08 at 17 43 16

@asinghvi17
Copy link
Collaborator

Perfect! That package looks really cool, by the way :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants