Conversation
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
|
That would be really useful indeed. I wonder if the corresponding nav entry for a given excluded file/page should also be removed when building, because when I write something for my blog I have to comment/uncomment the post in the nav until it's ready. |
This reverts commit 4e0429e.
These files will not be picked up into the `Files` collection and as such, also the final built site. Also adds the ability to *un*-ignore the files that MkDocs forcibly ignores.
* Docs that match any of the `not_in_nav` patterns will not produce warnings about never being included into the nav. * Files that are excluded by `exclude_docs` will now be preserved in the `Files` collection and will even be rendered but only in `mkdocs serve` mode - such files will have a `DRAFT` notice prepended to the content.
…then serve Also rename `--dirtyreload` flag to `--dirty` (keep the old name working)
This comment was marked as abuse.
This comment was marked as abuse.
|
Seems to be working fine, thanks @oprypin 🙂 What's the reason for multiline strings instead of arrays for the config settings? |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
Hmmm I think my main argument would be that such a feature would allow me to exclude a file and remove the corresponding nav entry automatically, until I'm ready to publish it, and in which case I either move the file around or stop excluding it. In short: exclude it once when you start working on it, re-include it once when you're ready. Without such a feature, I constantly have to comment/uncomment the nav entry in mkdocs.yml, at least if I publish other things while working on the draft. This is annoying but not critical. It's probably possible to write a plugin that does that. |
This comment was marked as abuse.
This comment was marked as abuse.
Yeah true, I guess I'm lazy and don't want to type the URL myself instead of clicking 🤔 I remember Jekyll had some first-class support for drafts. I'll check again how it works to see if there's something we can improve in MkDocs 🙂 |
This comment was marked as abuse.
This comment was marked as abuse.
|
That would be nice yes :) |
And refactor `LiveReloadServer` to not start listening in the constructor
These files will not be picked up into the
Filescollection and as such, also the final built site.Also adds the ability to un-ignore the files that MkDocs forcibly ignores.