From 5432dc04a64c9282ef35fd6017047f5215a00dfd Mon Sep 17 00:00:00 2001 From: winlu Date: Mon, 5 Jan 2015 12:07:01 +0100 Subject: [PATCH 1/3] fix double definition of simple theme link to different targets --- docs/themes.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/themes.rst b/docs/themes.rst index 198f8334..25926893 100644 --- a/docs/themes.rst +++ b/docs/themes.rst @@ -325,6 +325,7 @@ period A tuple of the form (`year`, `month`, `day`) that =================== =================================================== You can see an example of how to use `period` in the `"simple" theme +period_archives.html template `_. From 30c4d0eaf38f13f442946be29243f881e0c5e1a7 Mon Sep 17 00:00:00 2001 From: winlu Date: Mon, 5 Jan 2015 12:22:00 +0100 Subject: [PATCH 2/3] fix whitespace --- docs/content.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/content.rst b/docs/content.rst index 4de480ba..12bd887f 100644 --- a/docs/content.rst +++ b/docs/content.rst @@ -502,9 +502,9 @@ If your articles should be automatically published as a draft (to not accidental publish an article before it is finished) include the status in the ``DEFAULT_METADATA``:: DEFAULT_METADATA = { - 'status': 'draft', - } - + 'status': 'draft', + } + .. _W3C ISO 8601: http://www.w3.org/TR/NOTE-datetime .. _AsciiDoc: http://www.methods.co.nz/asciidoc/ .. _pelican-plugins: http://github.com/getpelican/pelican-plugins From 49481f60a54eed144b2d09d510e203f03fcdc2d4 Mon Sep 17 00:00:00 2001 From: winlu Date: Mon, 5 Jan 2015 12:36:35 +0100 Subject: [PATCH 3/3] fix headers, this fixes issues with docs/contributing.rst throwing errors because of the different content structure --- CONTRIBUTING.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 85d30c97..862cf7a7 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -1,5 +1,5 @@ Filing issues -------------- +============= * Before you file an issue, try `asking for help`_ first. * If determined to file an issue, first check for `existing issues`_, including @@ -9,7 +9,7 @@ Filing issues .. _`existing issues`: https://github.com/getpelican/pelican/issues How to get help ---------------- +=============== Before you ask for help, please make sure you do the following: @@ -66,7 +66,7 @@ Once the above preparation is ready, you can contact people willing to help via Remember to include all the information you prepared. The #pelican IRC channel -........................ +------------------------ * Because of differing time zones, you may not get an immediate response to your question, but please be patient and stay logged into IRC — someone will almost @@ -81,7 +81,7 @@ The #pelican IRC channel Contributing code ------------------ +================= Before you submit a contribution, please ask whether it is desired so that you don't spend a lot of time working on something that would be rejected for a @@ -89,7 +89,7 @@ known reason. Consider also whether your new feature might be better suited as a plugin_ — you can `ask for help`_ to make that determination. Using Git and GitHub -.................... +-------------------- * `Create a new git branch`_ specific to your change (as opposed to making your commits in the master branch). @@ -116,7 +116,7 @@ Using Git and GitHub turn your GitHub issue into a pull request containing your code. Contribution quality standards -.............................. +------------------------------ * Adhere to `PEP8 coding standards`_ whenever possible. This can be eased via the `pep8 `_ or `flake8