-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
Docusaurus build and push commands do not copy *.css files from subdirectories of website/static. #942
Comments
Using doxygen to view the site locally with 'npm start' finds the .css files. The Doxygen-generated tree in website/static is rendered correctly. |
I am working with @mvm3k now on this. |
After chatting with @mvm3k - I believe we just needed to use the
@mvm3k is testing it now. He made a good point that we should probably add something about Doxygen integration at a higher level of our docs where this setting could be crucial for Docusaurus. |
This worked. 🎉 We still have a bug where files starting with |
🐛 Bug Report
yarn run build and publish-gh-pages do not copy *.css files from our website/static/api directory that contains Doxygen-generated API docs into website/build. Is this intentional? All the other files, hundreds of them in a deep directory structure, are copied fine, but these two CSS files are ignored.
Have you read the Contributing Guidelines on issues?
yes
To Reproduce
Expected behavior
I expected all files in all subdirectories of website/static to be copied into the corresponding subdirectores of website/build. Is this a correct assumption? Should I put Doxygen-generated files under website/pages instead?
bash-3.2$ diff ~/api.files ~/build.files
26d25
< doxygen.css
54d52
< tabs.css
Reproducible Demo
this is a private Facebookincubator repo at this time.
The text was updated successfully, but these errors were encountered: