Add trailing slashes to links that should have them

content/blog/plugin-play/contents.lr

@@ -37,6 +37,6 @@ Plugins are tagged with specific key words or phrases that describe what they ar
 
 I think this is especially useful for plugin development when the tag is an event that the plugin hooks. This allows you to quickly find the source code of plugins that depend on the same Lektor plugin events, so that you can see many quick examples to help you write your own plugin. For instance, you can find all of the plugins that hook the `before-build-all` event by looking at it's tag page [here](/plugins/tag/before-build-all/). Tag pages for events also have links back to the plugin documentation pages, including the page for that specific event.
 
-Now go check out some [plugins](/plugins)! 
+Now go check out some [plugins](/plugins/)! 
 ----
 class: default

content/docs/api/utils/process-image/contents.lr

@@ -18,7 +18,7 @@ width and/or height, and the operation mode.
 In the default mode, if width or height are `None`, they are calculated
 from the source image's dimensions so that the image is scaled proportionally.
 
-Used internally for the implementation of [thumbnail :ref](../../db/record/thumbnail), and exposed as an API for image-processing plugins.
+Used internally for the implementation of [thumbnail :ref](../../db/record/thumbnail/), and exposed as an API for image-processing plugins.
 
 ## Example
 

content/docs/plugins/howto/contents.lr

@@ -117,7 +117,7 @@ function we also track the plugin's filename to rebuild if the plugin changes.
 Let's say you want to add an "asciidoc"
 [field type :ref](../../api/db/types/) so you can write with [AsciiDoc](http://www.methods.co.nz/asciidoc) markup.
 
-First [install AsciiDoc](http://www.methods.co.nz/asciidoc/INSTALL.html) so its command-line program is available. Then update `blog-post.ini` from the [blog guide :ref](../../guides/blog) like so:
+First [install AsciiDoc](http://www.methods.co.nz/asciidoc/INSTALL.html) so its command-line program is available. Then update `blog-post.ini` from the [blog guide :ref](../../guides/blog/) like so:
 
 ```ini
 [fields.body]

content/docs/plugins/publishing/contents.lr

@@ -86,7 +86,7 @@ credentials for `pypi`.  Next time it will have remembered them.
 
 ### Guide
 
-We'd love to see your new plugin listed on [our plugins page  :ref](/plugins). To do that, submit a pull request to [this repository :ext](https://github.com/lektor/lektor-website) that adds your plugin as a sub-page of /plugins. To have your plugin page look it's best and be found more easily here and on [PyPI :ext](https://pypi.org/), please [fill out your setup.py :ext](https://packaging.python.org/tutorials/distributing-packages/) completely (as in [the above snippet :ref](/docs/plugins/publishing/#enhance-your-setup.py)), including
+We'd love to see your new plugin listed on [our plugins page  :ref](/plugins/). To do that, submit a pull request to [this repository :ext](https://github.com/lektor/lektor-website) that adds your plugin as a sub-page of /plugins. To have your plugin page look it's best and be found more easily here and on [PyPI :ext](https://pypi.org/), please [fill out your setup.py :ext](https://packaging.python.org/tutorials/distributing-packages/) completely (as in [the above snippet :ref](/docs/plugins/publishing/#enhance-your-setup.py)), including
 
 * `author` and `author_email`
 * `classifiers`, (optional) such as

content/docs/quickstart/contents.lr

@@ -12,7 +12,7 @@ the command line client which is the recommended way to do development until
 the website is ready for end user management.
 
 If you do not have the `lektor` [command line executable :ref](../cli/)
-available yet just consult the [Installation :ref](../installation) section of
+available yet just consult the [Installation :ref](../installation/) section of
 the documentation.
 
 ## Creating a New Project

content/docs/themes/installing/contents.lr

@@ -38,7 +38,7 @@ a particular theme.
 !!!! Not implemented yet.
 
 You could add the `themes` variable to the `.lektorproject` file and Lektor will
-search in the [community themes](/themes) and automatically install it.
+search in the [community themes](/themes/) and automatically install it.
 
 ```ini
 [project]

content/docs/themes/packages/contents.lr

@@ -8,7 +8,7 @@ body:
 
 !!!! Not implemented yet.
 
-Themes could depend on [plugins](../../plugins), and they will be loaded along
+Themes could depend on [plugins](../../plugins/), and they will be loaded along
 the theme.
 
 1. You could use the `[packages]` section of the `theme.ini` to install

content/plugins/contents.lr

@@ -9,7 +9,7 @@ text:
 
 Lektor is a young project but it has a growing list of both official and community supported plugins. Official plugins are maintained by Lektor and kept in good shape together with the rest of the project. Community plugins are moderated and updated regularly, but they might not keep pace with development on Lektor. They are maintained by the community. Install them with `lektor plugins add NAME`.
 
-If you want to make or publish your own plugin, or see our [docs :ref](/docs/plugins).
+If you want to make or publish your own plugin, or see our [docs :ref](/docs/plugins/).
 
 (*) Asterisks denote official plugins.
 ----

databags/menu.ini

@@ -1,27 +1,27 @@
 [download]
-path = /downloads
+path = /downloads/
 label = Download
 
 [docs]
-path = /docs
+path = /docs/
 label = Documentation
 
 [poweredby]
-path = /showcase
+path = /showcase/
 label = Showcase
 
 [plugins]
-path = /plugins
+path = /plugins/
 label = Plugins
 
 # [themes]
-# path = /themes
+# path = /themes/
 # label = Themes
 
 [community]
-path = /community
+path = /community/
 label = Community
 
 [blog]
-path = /blog
+path = /blog/
 label = Blog

templates/blog-archive/index.html

@@ -3,7 +3,7 @@
 {% block blog_body %}
   <h1>The Transcript Archive</h1>
   <p>
-    <a href="{{ '/blog'|url }}">&laquo; back to the blog</a>
+    <a href="{{ '/blog/'|url }}">&laquo; back to the blog</a>
   <p>
     There have been posts in the following years:
   <ul>

templates/layout.html

@@ -68,8 +68,8 @@
           {%- endif %}
         </div>
         <div class="col-sm-8">
-          <a href="{{ '/license'|url }}">License & Copyright</a> •
+          <a href="{{ '/license/'|url }}">License & Copyright</a> •
-          <a href="{{ '/contact'|url }}">Contact</a> •
+          <a href="{{ '/contact/'|url }}">Contact</a> •
           Made with <i class="fa fa-fw fa-heart" title="Heart"><span hidden>Heart</span></i> in Carinthia
         </div>
       </div>

templates/plugin-tag.html

@@ -12,11 +12,11 @@
         Take a look at their source code to see how they work!
       </p>
       <p>
-        <a href="{{ '/docs/plugins'|url }}" class="ref">Intro to Plugins</a>
+        <a href="{{ '/docs/plugins/'|url }}" class="ref">Intro to Plugins</a>
         ||
         <a href="{{ '/docs/cli/plugins/'|url }}" class="ref">Plugin Commands</a>
         ||
-        <a href="{{ '/docs/api/plugins'|url }}" class="ref">Plugin API</a>
+        <a href="{{ '/docs/api/plugins/'|url }}" class="ref">Plugin API</a>
         ||
         <a href="{{ event|url }}" class="ref">This Event</a>
       </p>
@@ -30,6 +30,6 @@
   </div>
 
   <p>View a list of all Lektor plugin tags
-    <a href="{{ '/plugins/tags'|url }}" class="ref">here</a>.
+    <a href="{{ '/plugins/tags/'|url }}" class="ref">here</a>.
   </p>
 {% endblock %}

templates/plugin.html

@@ -69,7 +69,7 @@
           <p>Plugin has no tags.</p>
         {% endif %}
         <p>
-          View <a href="{{ '/plugins/tags'|url }}" class="ref">all tags</a>.
+          View <a href="{{ '/plugins/tags/'|url }}" class="ref">all tags</a>.
         </p>
       </div>
 

templates/plugins.html

@@ -27,6 +27,6 @@
     Plugins are also tagged with keywords and topics.
     Their tags are listed on their page and are navigable.
     You can view a list of all of the tags
-    <a href="{{ '/plugins/tags'|url }}" class="ref">here</a>.
+    <a href="{{ '/plugins/tags/'|url }}" class="ref">here</a>.
   </p>
 {% endblock %}