You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MkDocs assumes /docs folder exists, it's hard coded to look for and set paths to /docs.
Over-write commands are available, user has to make sure to check and fix things with special commands to alternate desired directories to ensure all the mkdoc's features work as intended.
/Documentation to /docs
/images to /docs/img (needed to add favicon, reference )
Hello. I just exactly work these days on rearranging some files/directories inside the repository. So I decided to bring this report up before merge will be accepted. Since some changes are coming anyway, this issue can be addressed & resolved as well. However, I've read your report, and both of the provided links. But I don't see any issue here to be honest with you. So, could you, please, be more specific, why exactly Documentation should be renamed?
Because the way how it works now (thanks to your help as I can see) - there are/[will be] already valid configuration files:
And while I was testing changes, I can confirm that now simple run of mkdocs build -f scripts/IronOS-mkdocs.yml -d ../site
generates local static documentation in local site/ directory and mkdocs gh-deploy -f scripts/IronOS-mkdocs.yml -d ../site
deploys it successfully online even for a forked repo in a fully automagical way.
So... what is the issue now exactly? Is this report still valid? Just very curious now. Thanks.
MkDocs assumes /docs folder exists, it's hard coded to look for and set paths to /docs.
Over-write commands are available, user has to make sure to check and fix things with special commands to alternate desired directories to ensure all the mkdoc's features work as intended.
reference:
Just something to consider if you want stuff to "automatically" work without fuss.
The text was updated successfully, but these errors were encountered: