mirror of https://github.com/mkdocs/mkdocs.git synced 2026-03-27 18:08:31 +07:00

Go to file

Waylan Limberg daf97c282b Ensure nav.homepage.url is not blank on error pages. (#1132 )

Also maintain pattern of ending urls with a slash in nav (all non-error pages
do so the error page should also). A couple extra checks to ensure base_url
doesn't end in a slash though as it is expected that the string appended
to base_url will always begin with a slash.

Fixes #1131

2017-01-29 20:34:13 -05:00

docs

Bump the version and add release notes

2016-12-22 09:06:58 +00:00

mkdocs

Ensure nav.homepage.url is not blank on error pages. (#1132 )

2017-01-29 20:34:13 -05:00

requirements

Up livereload version to >=2.5.1. (#1122 )

2017-01-08 17:53:08 -05:00

.codecov.yml

Update the codecov config

2016-05-31 12:03:09 +01:00

.csslintrc

Add csslint to lint CSS.

2016-10-09 20:32:18 -04:00

.gitignore

Update tox.ini

2014-02-10 19:44:11 +00:00

.jshintignore

Add jshint to lint JS.

2016-10-09 10:05:15 -04:00

.travis.yml

Allow pypy3 failures for now

2016-11-23 21:28:58 +00:00

appveyor.yml

Include Py35 tests in CI tests.

2015-11-17 19:26:36 -05:00

CONTRIBUTING.md

Corrected lint errors in Markdown docs.

2015-08-13 10:18:34 -04:00

LICENSE

Add BSD license file

2014-10-13 21:23:34 +01:00

MANIFEST.in

fix name of license file in manifest

2016-11-11 20:53:48 -06:00

mkdocs.yml

Deprecate auto-populating extra_css/javascript.

2016-08-09 22:50:35 -04:00

README.md

Adopt the PyPA Code of Conduct

2016-06-28 21:22:22 +01:00

setup.cfg

Add universal = 1 for wheels

2015-04-21 16:57:32 +01:00

setup.py

Up livereload version to >=2.5.1. (#1122 )

2017-01-08 17:53:08 -05:00

tox.ini

Add csslint to lint CSS.

2016-10-09 20:32:18 -04:00

README.md

MkDocs

Project documentation with Markdown.

View the MkDocs documentation.
Project release notes.
Visit the MkDocs wiki for community resources, including third party themes and a list of MkDocs users.
IRC channel: #mkdocs on freenode.
Discussions and support: https://groups.google.com/forum/#!forum/mkdocs

Code of Conduct

Everyone interacting in the MkDocs project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the PyPA Code of Conduct.