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

Investigate whether docs resources can be stored in relative directory rather than static #134

Open
gdams opened this issue Feb 22, 2022 · 7 comments

Comments

@gdams
Copy link
Member

gdams commented Feb 22, 2022

No description provided.

@tellison
Copy link
Contributor

tellison commented Dec 2, 2022

Still valid?

@gdams
Copy link
Member Author

gdams commented Dec 2, 2022

yup

@gdams
Copy link
Member Author

gdams commented Dec 2, 2022

For a bit of extra context... https://www.npmjs.com/package/gatsby-remark-copy-linked-files does this for Markdown files so in principle we need to find a way of doing something similar for the asciidoc files or potentially even extend the functionality of the plugin upstream.

I've asked the question in gatsbyjs/gatsby#37149 to see if other people are interested in this.

@ascheman
Copy link

ascheman commented Jan 21, 2023

Could you please add a small description about the problem?

I suspect it is about error messages shown in an IDE, e.g., IntelliJ (using the IntelliJ AsciiDoctor Plugin):

image

and the missing preview

image

At least for IntelliJ this can be resolved by adding a file .asciidoctorconfig into the respective directory (/content here).

:imagesdir: {asciidoctorconfigdir}/../static/images

Then the error in IntelliJ is gone, a mouse over will even show the referenced image:

image

and the preview will of course show the image as well

image

@ascheman
Copy link

If you feel my comment above describes the problem, you may assign the issue to me @gdams / @smlambert and add it to the Q1 2023 project.

@gdams
Copy link
Member Author

gdams commented Jan 21, 2023

@ascheman I should have marked this as fixed by #1397. We should hopefully no longer have this problem. Thanks for bringing the issue to my attention again thought.

@gdams gdams linked a pull request Jan 21, 2023 that will close this issue
4 tasks
ascheman pushed a commit to ascheman-adoptium/adoptium.net that referenced this issue Jan 21, 2023
@ascheman
Copy link

Please, please don't drop AsciiDoc in favour of markdown.

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

Successfully merging a pull request may close this issue.

3 participants