diff --git a/plugins/lektor-google-analytics/index.html b/plugins/lektor-google-analytics/index.html
index d8c1de7e..9fe376d1 100644
--- a/plugins/lektor-google-analytics/index.html
+++ b/plugins/lektor-google-analytics/index.html
@@ -130,58 +130,86 @@
Project Description
-
This plugin adds support for Google analytics to Lektor CMS.
-
Once the plugin is enabled, a generate_google_analytics() function
-is available to be included in target template which automatically
-include Google-Analytics code in final HTML files rendered by
-Lektor.
-
-Basic Usage
-
-Enabling the Plugin
-To enable the plugin add this to your project file:
-[packages]
-lektor-google-analytics = 0.1
-
-
-Configuring the Plugin
-The plugin needs a config file with your Google analytics code in
-it.
-Just create a file named google-analytics.ini into ./configs
-folder in your Lektor project’s base directory. And, put the
-GOOGLE_ANALYTICS_ID key with target property ID of form
-UA-XXXXXXXX-Y which you obtained from:
-GOOGLE_ANALYTICS_ID = UA-XXXXXXXX-Y
-
-
-Using in Templates
-Now you can add a Google analytics code-snippet in your templates by
-just calling the generate_google_analytics function inside its <body> </body> tags.
-<div class="ga-script">{{ generate_google_analytics() }}</div>
-That’s it. All the HTML files that rendered from that template will
-include Google-Analytics code automatically.
-
-
-
-Advanced
-
-- You can use GOOGLE_ANALYTICS_PROPERTY property to include your
-custom-built Google Analytics tracking code. In that case, your
-./configs/google-analytics.ini will look like this:
-
-
-GOOGLE_ANALYTICS_ID = UA-XXXXXXXX-Y
-GOOGLE_ANALYTICS_PROPERTY = 'my custom code'
-Don’t use this property unless you know what are you doing. By default,
-it is set to auto.
-To go deeper than this, please refer to Google-Analytics
-documentation.
-
-Copyright (c) 2015, Khaled Monsoor
-All rights reserved.
-Licensed under BSD license.
-
-
+ lektor-google-analytics
+
=======================
+
+
+
This plugin adds support for `Google analytics` to `Lektor CMS`.
+
+
Once the plugin is enabled, a ``generate_google_analytics()`` function
+
is available to be included in target ``template`` which automatically
+
include Google-Analytics code in final HTML files rendered by
+
``Lektor``.
+
+
+
Basic Usage
+
-----------
+
+
Enabling the Plugin
+
~~~~~~~~~~~~~~~~~~~
+
+
To enable the plugin add this to your project file:
+
+
.. code:: ini
+
+
[packages]
+
lektor-google-analytics = 0.1
+
+
Configuring the Plugin
+
~~~~~~~~~~~~~~~~~~~~~~
+
+
The plugin needs a config file with your ``Google analytics`` code in
+
it.
+
+
Just create a file named ``google-analytics.ini`` into ``./configs``
+
folder in your Lektor project’s base directory. And, put the
+
``GOOGLE_ANALYTICS_ID`` key with target property ID of form
+
``UA-XXXXXXXX-Y`` which you obtained from:
+
+
.. code:: ini
+
+
GOOGLE_ANALYTICS_ID = UA-XXXXXXXX-Y
+
+
Using in Templates
+
~~~~~~~~~~~~~~~~~~
+
+
Now you can add a Google analytics code-snippet in your templates by
+
just calling the ``generate_google_analytics`` function inside its ``<body> </body>`` tags.
+
+
.. code:: html
+
+
<div class="ga-script">{{ generate_google_analytics() }}</div>
+
That’s it. All the ``HTML`` files that rendered from that template will
+
include Google-Analytics code automatically.
+
+
+
Advanced
+
--------
+
+
You can use ``GOOGLE_ANALYTICS_PROPERTY`` property to include your
+
custom-built Google Analytics tracking code. In that case, your
+
``./configs/google-analytics.ini`` will look like this:
+
+
.. code:: ini
+
+
GOOGLE_ANALYTICS_ID = UA-XXXXXXXX-Y
+
GOOGLE_ANALYTICS_PROPERTY = 'my custom code'
+
+
Don’t use this property unless you know what are you doing. By default,
+
it is set to ``auto``.
+
+
To go deeper than this, please refer to `Google-Analytics
+
documentation`.
+
+
+
-----
+
+
+
**Copyright** (c) 2015, Khaled Monsoor
+
+
All rights reserved.
+
+
Licensed under `BSD` license.
diff --git a/plugins/lektor-gulp/index.html b/plugins/lektor-gulp/index.html
index d3fe5ec0..4c67ef18 100644
--- a/plugins/lektor-gulp/index.html
+++ b/plugins/lektor-gulp/index.html
@@ -139,40 +139,7 @@
Project Description
-
This plugin for Lektor CMS adds gulp support to projects. When
-enabled with the -f gulp flag it runs npm install and then the
-gulp default or watch tasks as they are defined into your own
-gulpfile.js.
-
The general documentation about Lektor plugins is here.
-
-lektor build
-The command lektor build -f gulp runs the ``default`` gulp task,
-for example defined as something like:
-gulp.task('build', ['clean', 'copy', 'js', 'css', 'imagemin'], () => { });
-gulp.task('default', ['build'], () => { });
-In the above example the default task points to a build task,
-which is usually composed by several other gulp tasks, etc.
-
-
-lektor server
-The command lektor server -f gulp runs the Lektor embedded server on
-http://localhost:5000, starting a gulp ``watch`` task in background.
-For example, you can define something such as:
-gulp.task('watch', () => {
- gulp.watch('lib/js/**/*.js', ['js']);
- gulp.watch('lib/css/**/*.css', ['css']);
-});
-In the above example, each time one touches Javascript or CSS files in
-the lib/ folder then assets could be minified, concatenated and
-copied into the standard assets/static/ lektor folder, or whatever
-is defined into your own gulpfile.js.
-
-
-Credits
-This plugin is based on the official Webpack plugin with very little
-differences.
-
-
+ lektor-gulp
===========
This plugin for `Lektor CMS`_ adds `gulp`_ support to projects. When
enabled with the ``-f gulp`` flag it runs ``npm install`` and then the
gulp ``default`` or ``watch`` tasks as they are defined into your own
``gulpfile.js``.
The general documentation about Lektor plugins is `here`_.
lektor build
------------
The command ``lektor build -f gulp`` runs the **``default``** gulp task,
for example defined as something like:
.. code::
gulp.task('build', ['clean', 'copy', 'js', 'css', 'imagemin'], () => { });
gulp.task('default', ['build'], () => { });
In the above example the ``default`` task points to a ``build`` task,
which is usually composed by several other gulp tasks, etc.
lektor server
-------------
The command ``lektor server -f gulp`` runs the Lektor embedded server on
http://localhost:5000, starting a gulp **``watch``** task in background.
For example, you can define something such as:
.. code::
gulp.task('watch', () => {
gulp.watch('lib/js/**/*.js', ['js']);
gulp.watch('lib/css/**/*.css', ['css']);
});
In the above example, each time one touches Javascript or CSS files in
the ``lib/`` folder then assets could be minified, concatenated and
copied into the standard ``assets/static/`` lektor folder, or whatever
is defined into your own ``gulpfile.js``.
Credits
-------
This plugin is based on the official `Webpack plugin`_ with very little
differences.
.. _Lektor CMS: https://www.getlektor.com
.. _gulp: http://gulpjs.com
.. _here: https://www.getlektor.com/docs/plugins/
.. _Webpack plugin: https://github.com/lektor/lektor-webpack-support
diff --git a/plugins/lektor-htmlmin/index.html b/plugins/lektor-htmlmin/index.html
index 11883046..143a8cf5 100644
--- a/plugins/lektor-htmlmin/index.html
+++ b/plugins/lektor-htmlmin/index.html
@@ -130,30 +130,7 @@
Project Description
-
-
HTML minifier for Lektor that automatically minifies generated .html files.
-
Uses htmlmin and looks for .html files,
-minifying them as part of the build process.
-
-Installing
-You can install the plugin with Lektor’s installer:
-lektor plugins add lektor-htmlmin
-Or by hand, adding the plugin to the packages section in your lektorproject file:
-[packages]
-lektor-htmlmin = 1.0
-
-
-Usage
-To enable minification, pass the htmlmin flag when starting the development
-server or when running a build:
-lektor build -O my_build_folder -f htmlmin
-When the flag is present, htmlmin will overwrite all HTML files in the output
-directory with their minified counterparts.
-Note: The htmlmin plugin currently minifies every file in the project after a build.
-Not just files that have been changed. This should have no ill effects, but
-might increase build times if there are many files to minify.
-
-
+ lektor-htmlmin
--------------
|Pypi|
HTML minifier for Lektor that automatically minifies generated .html files.
Uses `htmlmin <https://github.com/mankyd/htmlmin>`_ and looks for .html files,
minifying them as part of the build process.
Installing
##########
You can install the plugin with Lektor's installer::
lektor plugins add lektor-htmlmin
Or by hand, adding the plugin to the packages section in your lektorproject file::
[packages]
lektor-htmlmin = 1.0
Usage
#####
To enable minification, pass the `htmlmin` flag when starting the development
server or when running a build::
lektor build -O my_build_folder -f htmlmin
When the flag is present, htmlmin will overwrite all HTML files in the output
directory with their minified counterparts.
*Note:* The htmlmin plugin currently minifies every file in the project after a build.
Not just files that have been changed. This should have no ill effects, but
might increase build times if there are many files to minify.
.. |Pypi| image:: https://img.shields.io/pypi/v/lektor-htmlmin.svg?maxAge=3600&style=flat-square
:target: https://pypi.python.org/pypi/efesto
diff --git a/plugins/lektor-markdown-excerpt/index.html b/plugins/lektor-markdown-excerpt/index.html
index bfcbeca8..082cf133 100644
--- a/plugins/lektor-markdown-excerpt/index.html
+++ b/plugins/lektor-markdown-excerpt/index.html
@@ -127,18 +127,7 @@
Project Description
-
# lektor-markdown-excerpt
-
This plugin adds filter for Markdown body excerpt.
-
## Enabling the Plugin
-
To enable the plugin run this command:
-
`ini $ lektor plugins add markdown-excerpt `
-
## In Templates
-
Plugin provides the |excerpt filter that can be used to render first
-paragraph of Markdown:
-
`jinja {{ post.body|excerpt }} `
-
It takes one optional argument which is the separator for the excerpt:
-
`jinja {{ post.body|excerpt:'\n\n##' }} `
-
+ # lektor-markdown-excerpt
This plugin adds filter for Markdown body excerpt.
## Enabling the Plugin
To enable the plugin run this command:
```ini
$ lektor plugins add markdown-excerpt
```
## In Templates
Plugin provides the `|excerpt` filter that can be used to render first
paragraph of Markdown:
```jinja
{{ post.body|excerpt }}
```
It takes one optional argument which is the separator for the excerpt:
```jinja
{{ post.body|excerpt:'\n\n##' }}
```
diff --git a/plugins/lektor-minify/index.html b/plugins/lektor-minify/index.html
index a680a02f..7ce2f944 100644
--- a/plugins/lektor-minify/index.html
+++ b/plugins/lektor-minify/index.html
@@ -136,15 +136,7 @@
Project Description
-
This plugin allows you to minify the build artifacts of your Lektor project
-during the build process, without any additional tool. It currently supports
-minifying HTML, CSS and JS files.
-
The plugin only minifies the files changed during the last build, avoiding
-slowing down the build if your project consists of a lot of files. Internally
-it uses the rcssmin and rjsmin libraries, and it’s released under the MIT
-license.
-
Learn more about the plugin
-
+
=============
lektor-minify
=============
This plugin allows you to minify the build artifacts of your `Lektor`_ project
during the build process, without any additional tool. It currently supports
minifying HTML, CSS and JS files.
The plugin only minifies the files changed during the last build, avoiding
slowing down the build if your project consists of a lot of files. Internally
it uses the rcssmin and rjsmin libraries, and it's released under the MIT
license.
`Learn more about the plugin`_
.. _Lektor: https://www.getlektor.com
.. _Learn more about the plugin: https://github.com/pietroalbini/lektor-minify
diff --git a/plugins/lektor-read-full-post/index.html b/plugins/lektor-read-full-post/index.html
index 248d9d90..448666a6 100644
--- a/plugins/lektor-read-full-post/index.html
+++ b/plugins/lektor-read-full-post/index.html
@@ -121,8 +121,7 @@
Project Description
-
Lektor plugin that allows blog listing posts to be shortened with a link to the full post.
-
+ Lektor plugin that allows blog listing posts to be shortened with a link to the full post.
diff --git a/plugins/lektor-tags/index.html b/plugins/lektor-tags/index.html
index 23d286dd..5a08a2df 100644
--- a/plugins/lektor-tags/index.html
+++ b/plugins/lektor-tags/index.html
@@ -62,7 +62,7 @@
-
Plugin – lektor-tags 0.5.1
+ Plugin – lektor-tags 0.5.2
@@ -96,7 +96,7 @@
Meta
-
Version: 0.5.1
+
Version: 0.5.2
Author:
A. Jesse Jiryu Davis
diff --git a/plugins/lektor-tawk/index.html b/plugins/lektor-tawk/index.html
index 8dfb5e23..e01156ff 100644
--- a/plugins/lektor-tawk/index.html
+++ b/plugins/lektor-tawk/index.html
@@ -130,18 +130,7 @@
Project Description
-
# Lektor Tawk
-
This plugin adds support for Tawk to Lektor. Once the plugin is enabled a render_tawk function will render a Tawk Live Chat.
-
## Enabling the Plugin
-
To enable the plugin add this to your project file:
-
` $ lektor plugins add lektor-tawk `
-
## Configuring the Plugin
-
The plugin has a config file that is needed to inform it about your website. Just create a file named tawk.ini into your configs/ folder and configure the live_chat_code key with the ID if your Tawk:
-
` live_chat_code = your_live_chat_code `
-
## In Templates
-
Now you can render to any of your templates by just using the render_tawk function. Just calling it is enough to get the live chat:
-
` <div>{{ render_tawk }}</div> `
-
+ # Lektor Tawk
This plugin adds support for Tawk to Lektor. Once the plugin is enabled a render_tawk function will render a Tawk Live Chat.
## Enabling the Plugin
To enable the plugin add this to your project file:
```
$ lektor plugins add lektor-tawk
```
## Configuring the Plugin
The plugin has a config file that is needed to inform it about your website. Just create a file named tawk.ini into your configs/ folder and configure the live_chat_code key with the ID if your Tawk:
```
live_chat_code = your_live_chat_code
```
## In Templates
Now you can render to any of your templates by just using the render_tawk function. Just calling it is enough to get the live chat:
```
<div>{{ render_tawk }}</div>
```
diff --git a/plugins/lektor-yandex-metrica/index.html b/plugins/lektor-yandex-metrica/index.html
index 7510f891..4a1124fe 100644
--- a/plugins/lektor-yandex-metrica/index.html
+++ b/plugins/lektor-yandex-metrica/index.html
@@ -130,23 +130,7 @@
Project Description
-
This plugin adds support for Yandex Metrica
-to Lektor CMS
-
-Enabling the Plugin
-lektor plugins add lektor-yandex-metrica
-
-
-Configuring the Plugin
-Just create a file named yandex-metrica.ini
in your configs/
folder and configure id
key with the provided counter id:
-id = YOUR_COUNTER_ID
-
-
-In Templates
-Now you can add a Yandex Metrica counter to any of your templates by just using the generate_yandex_metrica
function in its tag as below.
-{{ generate_yandex_metrica() }}
-
-
+ lektor-yandex-metrica
=====================
This plugin adds support for `Yandex Metrica <https://metrica.yandex.com>`_
to `Lektor CMS <https://www.getlektor.com>`_
Enabling the Plugin
-------------------
.. code-block:: bash
lektor plugins add lektor-yandex-metrica
Configuring the Plugin
----------------------
Just create a file named :code:`yandex-metrica.ini` in your :code:`configs/` folder and configure :code:`id` key with the provided counter id:
.. code-block:: ini
id = YOUR_COUNTER_ID
In Templates
------------
Now you can add a Yandex Metrica counter to any of your templates by just using the :code:`generate_yandex_metrica` function in its tag as below.
.. code:: html
{{ generate_yandex_metrica() }}