Let's move our primary development onto the 1.0 branch by merging that into master.
I have pushed up a 0.16 branch which is the current state of master. Any future bugfixes that would make for a good candidate for a 0.16.x bugfix release can then be backported from master. That's easier to manage than forward-porting bugfixes from master to 1.0.dev. It also removes the need to then merge all that back to master later (I had to resolve a lot of conflicts to get this in shape, don't want to have to do that again).
Warning, I rebased 1.0.dev with master, so any existing 1.0.dev clones/forks won't merge with this directly. However, I did the work in a private branch and have not pushed the rebase publicly. Therefore, the 1.0.dev branch here on GitHub is left alone for reference purposes. It should simply be considered inactive.
All Markdown handling is now contained within the `Page` object, which external code no longer needs to know the internals of. A slightly different approach to the work started in #713. Include the multimarkdown meta-data parser from docdata See: https://github.com/waylan/docdata Tests have been updated. However, as noted in #713, they could use some refactoring. The existing tests all pass. We can leave refactoring as a seperate matter from this. Closes #713.
See the included documentation for a full explanation of the API. Search has been removed and wrapped in a plugin (named "legacy_search"). The search feature was ported as-is. None of the open issues with search have been addressed. Presumably, a new search plugin will be built from the ground up which addresses those issues. Note that there is no 'default' plugins. That means that users get no search unless they enable it in the config by adding the following to their `mkdocs.yml` file: plugins: - legacy_search Fixes #206