Websites
/
lektor-website
mirror of https://github.com/lektor/lektor-website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Synchronized build

This commit is contained in:
Lektor Bot 2023-11-11 12:12:23 +00:00
parent 0bde937dd5
commit a7b326093c
10 changed files with 92 additions and 167 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
index.html
View File

@ -151,7 +151,7 @@ speak multiple languages and allow you to easily create localized websites.</li>
<div class="slideshow-wrapper"> <div class="slideshow-wrapper">
<div class="slideshow"> <div class="slideshow">
<div class="slideshow-inner"> <div class="slideshow-inner">
<div class="carousel slide" data-ride="carousel" data-interval="8500" id="carousel-38fc9d76147049158be7ef92f38277e5"> <div class="carousel slide" data-ride="carousel" data-interval="8500" id="carousel-beb560494c81464bb6439d6bcec68e55">
<div class="carousel-inner" role="listbox"> <div class="carousel-inner" role="listbox">
@ -210,11 +210,11 @@ be completely customized.</p>
</div> </div>
</div> </div>
<a class="left carousel-control" href="#carousel-38fc9d76147049158be7ef92f38277e5" role="button" data-slide="prev"> <a class="left carousel-control" href="#carousel-beb560494c81464bb6439d6bcec68e55" role="button" data-slide="prev">
<span class="glyphicon glyphicon-chevron-left" aria-hidden="true"></span> <span class="glyphicon glyphicon-chevron-left" aria-hidden="true"></span>
<span class="sr-only">Previous</span> <span class="sr-only">Previous</span>
</a> </a>
<a class="right carousel-control" href="#carousel-38fc9d76147049158be7ef92f38277e5" role="button" data-slide="next"> <a class="right carousel-control" href="#carousel-beb560494c81464bb6439d6bcec68e55" role="button" data-slide="next">
<span class="glyphicon glyphicon-chevron-right" aria-hidden="true"></span> <span class="glyphicon glyphicon-chevron-right" aria-hidden="true"></span>
<span class="sr-only">Next</span> <span class="sr-only">Next</span>
</a> </a>

132
plugins/lektor-google-analytics/index.html
View File

@ -130,58 +130,86 @@
<div class="col-sm-9 doc-styling"> <div class="col-sm-9 doc-styling">
<h2>Project Description</h2> <h2>Project Description</h2>
<p>This plugin adds support for <cite>Google analytics</cite> to <cite>Lektor CMS</cite>.</p> lektor-google-analytics
<p>Once the plugin is enabled, a <span class="docutils literal">generate_google_analytics()</span> function <br>=======================
is available to be included in target <span class="docutils literal">template</span> which automatically <br>
include Google-Analytics code in final HTML files rendered by <br>
<span class="docutils literal">Lektor</span>.</p> <br>This plugin adds support for `Google analytics` to `Lektor CMS`.
<section id="basic-usage"> <br>
<h2>Basic Usage</h2> <br>Once the plugin is enabled, a ``generate_google_analytics()`` function
<section id="enabling-the-plugin"> <br>is available to be included in target ``template`` which automatically
<h3>Enabling the Plugin</h3> <br>include Google-Analytics code in final HTML files rendered by
<p>To enable the plugin add this to your project file:</p> <br>``Lektor``.
<pre><code><span class="k">[packages]</span><span class="w"> <br>
</span><span class="na">lektor-google-analytics</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><s>0.1</s></code></pre> <br>
</section> <br>Basic Usage
<section id="configuring-the-plugin"> <br>-----------
<h3>Configuring the Plugin</h3> <br>
<p>The plugin needs a config file with your <span class="docutils literal">Google analytics</span> code in <br>Enabling the Plugin
it.</p> <br>~~~~~~~~~~~~~~~~~~~
<p>Just create a file named <span class="docutils literal"><span class="pre">google-analytics.ini</span></span> into <span class="docutils literal">./configs</span> <br>
folder in your Lektor project’s base directory. And, put the <br>To enable the plugin add this to your project file:
<span class="docutils literal">GOOGLE_ANALYTICS_ID</span> key with target property ID of form <br>
<span class="docutils literal"><span class="pre">UA-XXXXXXXX-Y</span></span> which you obtained from:</p> <br>.. code:: ini
<pre><code><span class="na">GOOGLE_ANALYTICS_ID</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><s>UA-XXXXXXXX-Y</s></code></pre> <br>
</section> <br> [packages]
<section id="using-in-templates"> <br> lektor-google-analytics = 0.1
<h3>Using in Templates</h3> <br>
<p>Now you can add a Google analytics code-snippet in your templates by <br>Configuring the Plugin
just calling the <span class="docutils literal">generate_google_analytics</span> function inside its <span class="docutils literal">&lt;body&gt; &lt;/body&gt;</span> tags.</p> <br>~~~~~~~~~~~~~~~~~~~~~~
<pre><code><span class="p">&lt;</span><span class="nt">div</span> <span class="na">class</span><span class="o">=</span><s>"ga-script"</s><span class="p">&gt;</span>{{ generate_google_analytics() }}<span class="p">&lt;/</span><span class="nt">div</span><span class="p">&gt;</span></code></pre> <br>
<p>That’s it. All the <span class="docutils literal">HTML</span> files that rendered from that template will <br>The plugin needs a config file with your ``Google analytics`` code in
include Google-Analytics code automatically.</p> <br>it.
</section> <br>
</section> <br>Just create a file named ``google-analytics.ini`` into ``./configs``
<section id="advanced"> <br>folder in your Lektor project’s base directory. And, put the
<h2>Advanced</h2> <br>``GOOGLE_ANALYTICS_ID`` key with target property ID of form
<dl class="simple"> <br>``UA-XXXXXXXX-Y`` which you obtained from:
<dt>You can use <span class="docutils literal">GOOGLE_ANALYTICS_PROPERTY</span> property to include your</dt> <br>
<dd><p>custom-built Google Analytics tracking code. In that case, your <br>.. code:: ini
<span class="docutils literal"><span class="pre">./configs/google-analytics.ini</span></span> will look like this:</p> <br>
</dd> <br> GOOGLE_ANALYTICS_ID = UA-XXXXXXXX-Y
</dl> <br>
<pre><code><span class="na">GOOGLE_ANALYTICS_ID</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><s>UA-XXXXXXXX-Y</s><span class="w"> <br>Using in Templates
</span><span class="na">GOOGLE_ANALYTICS_PROPERTY</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><s>'my custom code'</s></code></pre> <br>~~~~~~~~~~~~~~~~~~
<p>Don’t use this property unless you know what are you doing. By default, <br>
it is set to <span class="docutils literal">auto</span>.</p> <br>Now you can add a Google analytics code-snippet in your templates by
<p>To go deeper than this, please refer to <cite>Google-Analytics <br>just calling the ``generate_google_analytics`` function inside its ``&lt;body&gt; &lt;/body&gt;`` tags.
documentation</cite>.</p> <br>
<hr class="docutils"> <br>.. code:: html
<p><strong>Copyright</strong> (c) 2015, Khaled Monsoor</p> <br>
<p>All rights reserved.</p> <br> &lt;div class="ga-script"&gt;{{ generate_google_analytics() }}&lt;/div&gt;<br>
<p>Licensed under <cite>BSD</cite> license.</p> <br>That’s it. All the ``HTML`` files that rendered from that template will
</section> <br>include Google-Analytics code automatically.
<br>
<br>
<br>Advanced
<br>--------
<br>
<br>You can use ``GOOGLE_ANALYTICS_PROPERTY`` property to include your
<br> custom-built Google Analytics tracking code. In that case, your
<br> ``./configs/google-analytics.ini`` will look like this:
<br>
<br>.. code:: ini
<br>
<br> GOOGLE_ANALYTICS_ID = UA-XXXXXXXX-Y
<br> GOOGLE_ANALYTICS_PROPERTY = 'my custom code'
<br>
<br>Don’t use this property unless you know what are you doing. By default,
<br>it is set to ``auto``.
<br>
<br>To go deeper than this, please refer to `Google-Analytics
<br>documentation`.
<br>
<br>
<br>-----
<br>
<br>
<br>**Copyright** (c) 2015, Khaled Monsoor
<br>
<br>All rights reserved.
<br>
<br>Licensed under `BSD` license.

35
plugins/lektor-gulp/index.html
View File

@ -139,40 +139,7 @@
<div class="col-sm-9 doc-styling"> <div class="col-sm-9 doc-styling">
<h2>Project Description</h2> <h2>Project Description</h2>
<p>This plugin for <a href="https://www.getlektor.com" rel="nofollow">Lektor CMS</a> adds <a href="http://gulpjs.com" rel="nofollow">gulp</a> support to projects. When lektor-gulp<br>===========<br><br>This plugin for `Lektor CMS`_ adds `gulp`_ support to projects. When<br>enabled with the ``-f gulp`` flag it runs ``npm install`` and then the<br>gulp ``default`` or ``watch`` tasks as they are defined into your own<br>``gulpfile.js``.<br><br>The general documentation about Lektor plugins is `here`_.<br><br>lektor build<br>------------<br><br>The command ``lektor build -f gulp`` runs the **``default``** gulp task,<br>for example defined as something like:<br><br>.. code::<br><br> gulp.task('build', ['clean', 'copy', 'js', 'css', 'imagemin'], () =&gt; { });<br> gulp.task('default', ['build'], () =&gt; { });<br><br>In the above example the ``default`` task points to a ``build`` task,<br>which is usually composed by several other gulp tasks, etc.<br><br>lektor server<br>-------------<br><br>The command ``lektor server -f gulp`` runs the Lektor embedded server on<br>http://localhost:5000, starting a gulp **``watch``** task in background.<br>For example, you can define something such as:<br><br>.. code::<br><br> gulp.task('watch', () =&gt; {<br> gulp.watch('lib/js/**/*.js', ['js']);<br> gulp.watch('lib/css/**/*.css', ['css']);<br> });<br><br>In the above example, each time one touches Javascript or CSS files in<br>the ``lib/`` folder then assets could be minified, concatenated and<br>copied into the standard ``assets/static/`` lektor folder, or whatever<br>is defined into your own ``gulpfile.js``.<br><br>Credits<br>-------<br><br>This plugin is based on the official `Webpack plugin`_ with very little<br>differences.<br><br>.. _Lektor CMS: https://www.getlektor.com<br>.. _gulp: http://gulpjs.com<br>.. _here: https://www.getlektor.com/docs/plugins/<br>.. _Webpack plugin: https://github.com/lektor/lektor-webpack-support
enabled with the <span class="docutils literal"><span class="pre">-f</span> gulp</span> flag it runs <span class="docutils literal">npm install</span> and then the
gulp <span class="docutils literal">default</span> or <span class="docutils literal">watch</span> tasks as they are defined into your own
<span class="docutils literal">gulpfile.js</span>.</p>
<p>The general documentation about Lektor plugins is <a href="https://www.getlektor.com/docs/plugins/" rel="nofollow">here</a>.</p>
<section id="lektor-build">
<h2>lektor build</h2>
<p>The command <span class="docutils literal">lektor build <span class="pre">-f</span> gulp</span> runs the <strong>``default``</strong> gulp task,
for example defined as something like:</p>
<pre><code>gulp.task('build', ['clean', 'copy', 'js', 'css', 'imagemin'], () =&gt; { });
gulp.task('default', ['build'], () =&gt; { });</code></pre>
<p>In the above example the <span class="docutils literal">default</span> task points to a <span class="docutils literal">build</span> task,
which is usually composed by several other gulp tasks, etc.</p>
</section>
<section id="lektor-server">
<h2>lektor server</h2>
<p>The command <span class="docutils literal">lektor server <span class="pre">-f</span> gulp</span> runs the Lektor embedded server on
<a href="http://localhost:5000" rel="nofollow">http://localhost:5000</a>, starting a gulp <strong>``watch``</strong> task in background.
For example, you can define something such as:</p>
<pre><code>gulp.task('watch', () =&gt; {
gulp.watch('lib/js/**/*.js', ['js']);
gulp.watch('lib/css/**/*.css', ['css']);
});</code></pre>
<p>In the above example, each time one touches Javascript or CSS files in
the <span class="docutils literal">lib/</span> folder then assets could be minified, concatenated and
copied into the standard <span class="docutils literal">assets/static/</span> lektor folder, or whatever
is defined into your own <span class="docutils literal">gulpfile.js</span>.</p>
</section>
<section id="credits">
<h2>Credits</h2>
<p>This plugin is based on the official <a href="https://github.com/lektor/lektor-webpack-support" rel="nofollow">Webpack plugin</a> with very little
differences.</p>
</section>

25
plugins/lektor-htmlmin/index.html
View File

@ -130,30 +130,7 @@
<div class="col-sm-9 doc-styling"> <div class="col-sm-9 doc-styling">
<h2>Project Description</h2> <h2>Project Description</h2>
<p><a href="https://pypi.python.org/pypi/efesto" rel="nofollow"><img alt="Pypi" src="https://img.shields.io/pypi/v/lektor-htmlmin.svg?maxAge=3600&amp;style=flat-square"></a></p> lektor-htmlmin<br>--------------<br>|Pypi|<br><br>HTML minifier for Lektor that automatically minifies generated .html files.<br><br>Uses `htmlmin &lt;https://github.com/mankyd/htmlmin&gt;`_ and looks for .html files,<br>minifying them as part of the build process.<br><br>Installing<br>##########<br><br>You can install the plugin with Lektor's installer::<br><br> lektor plugins add lektor-htmlmin<br><br><br>Or by hand, adding the plugin to the packages section in your lektorproject file::<br><br> [packages]<br> lektor-htmlmin = 1.0<br><br><br>Usage<br>#####<br><br>To enable minification, pass the `htmlmin` flag when starting the development<br>server or when running a build::<br><br> lektor build -O my_build_folder -f htmlmin<br><br><br>When the flag is present, htmlmin will overwrite all HTML files in the output<br>directory with their minified counterparts.<br><br>*Note:* The htmlmin plugin currently minifies every file in the project after a build.<br>Not just files that have been changed. This should have no ill effects, but<br>might increase build times if there are many files to minify.<br><br><br>.. |Pypi| image:: https://img.shields.io/pypi/v/lektor-htmlmin.svg?maxAge=3600&amp;style=flat-square<br> :target: https://pypi.python.org/pypi/efesto
<p>HTML minifier for Lektor that automatically minifies generated .html files.</p>
<p>Uses <a href="https://github.com/mankyd/htmlmin" rel="nofollow">htmlmin</a> and looks for .html files,
minifying them as part of the build process.</p>
<section id="installing">
<h2>Installing</h2>
<p>You can install the plugin with Lektor’s installer:</p>
<pre>lektor plugins add lektor-htmlmin</pre>
<p>Or by hand, adding the plugin to the packages section in your lektorproject file:</p>
<pre>[packages]
lektor-htmlmin = 1.0</pre>
</section>
<section id="usage">
<h2>Usage</h2>
<p>To enable minification, pass the <cite>htmlmin</cite> flag when starting the development
server or when running a build:</p>
<pre>lektor build -O my_build_folder -f htmlmin</pre>
<p>When the flag is present, htmlmin will overwrite all HTML files in the output
directory with their minified counterparts.</p>
<p><em>Note:</em> 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.</p>
</section>

13
plugins/lektor-markdown-excerpt/index.html
View File

@ -127,18 +127,7 @@
<div class="col-sm-9 doc-styling"> <div class="col-sm-9 doc-styling">
<h2>Project Description</h2> <h2>Project Description</h2>
<p># lektor-markdown-excerpt</p> # lektor-markdown-excerpt<br><br>This plugin adds filter for Markdown body excerpt.<br><br>## Enabling the Plugin<br><br>To enable the plugin run this command:<br><br>```ini<br>$ lektor plugins add markdown-excerpt<br>```<br><br>## In Templates<br><br>Plugin provides the `|excerpt` filter that can be used to render first<br>paragraph of Markdown:<br><br>```jinja<br>{{ post.body|excerpt }}<br>```<br><br>It takes one optional argument which is the separator for the excerpt:<br><br>```jinja<br>{{ post.body|excerpt:'\n\n##' }}<br>```<br>
<p>This plugin adds filter for Markdown body excerpt.</p>
<p>## Enabling the Plugin</p>
<p>To enable the plugin run this command:</p>
<p><span class="docutils literal">`ini $ lektor plugins add <span class="pre">markdown-excerpt</span> `</span></p>
<p>## In Templates</p>
<p>Plugin provides the <cite>|excerpt</cite> filter that can be used to render first
paragraph of Markdown:</p>
<p><span class="docutils literal">`jinja {{ post.body|excerpt }} `</span></p>
<p>It takes one optional argument which is the separator for the excerpt:</p>
<p><span class="docutils literal">`jinja {{ <span class="pre">post.body|excerpt:'\n\n##'</span> }} `</span></p>

10
plugins/lektor-minify/index.html
View File

@ -136,15 +136,7 @@
<div class="col-sm-9 doc-styling"> <div class="col-sm-9 doc-styling">
<h2>Project Description</h2> <h2>Project Description</h2>
<p>This plugin allows you to minify the build artifacts of your <a href="https://www.getlektor.com" rel="nofollow">Lektor</a> project <br>=============<br>lektor-minify<br>=============<br><br>This plugin allows you to minify the build artifacts of your `Lektor`_ project<br>during the build process, without any additional tool. It currently supports<br>minifying HTML, CSS and JS files.<br><br>The plugin only minifies the files changed during the last build, avoiding<br>slowing down the build if your project consists of a lot of files. Internally<br>it uses the rcssmin and rjsmin libraries, and it's released under the MIT<br>license.<br><br>`Learn more about the plugin`_<br><br>.. _Lektor: https://www.getlektor.com<br>.. _Learn more about the plugin: https://github.com/pietroalbini/lektor-minify<br><br><br>
during the build process, without any additional tool. It currently supports
minifying HTML, CSS and JS files.</p>
<p>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.</p>
<p><a href="https://github.com/pietroalbini/lektor-minify" rel="nofollow">Learn more about the plugin</a></p>

3
plugins/lektor-read-full-post/index.html
View File

@ -121,8 +121,7 @@
<div class="col-sm-9 doc-styling"> <div class="col-sm-9 doc-styling">
<h2>Project Description</h2> <h2>Project Description</h2>
<p>Lektor plugin that allows blog listing posts to be shortened with a link to the full post.</p> Lektor plugin that allows blog listing posts to be shortened with a link to the full post.

4
plugins/lektor-tags/index.html
View File

@ -62,7 +62,7 @@
<div class="plugin"> <div class="plugin">
<div class="row"> <div class="row">
<div class="col-sm-12"> <div class="col-sm-12">
<h1>Plugin &ndash; lektor-tags 0.5.1</h1> <h1>Plugin &ndash; lektor-tags 0.5.2</h1>
</div> </div>
</div> </div>
@ -96,7 +96,7 @@
<div class="separator"> <div class="separator">
<h4>Meta</h4> <h4>Meta</h4>
</div> </div>
<p><strong>Version:</strong> 0.5.1</p> <p><strong>Version:</strong> 0.5.2</p>
<p><strong>Author:</strong> <p><strong>Author:</strong>
<a href="mailto:jesse@emptysquare.net">A. Jesse Jiryu Davis</a> <a href="mailto:jesse@emptysquare.net">A. Jesse Jiryu Davis</a>

13
plugins/lektor-tawk/index.html
View File

@ -130,18 +130,7 @@
<div class="col-sm-9 doc-styling"> <div class="col-sm-9 doc-styling">
<h2>Project Description</h2> <h2>Project Description</h2>
<p># Lektor Tawk</p> # Lektor Tawk<br><br>This plugin adds support for Tawk to Lektor. Once the plugin is enabled a render_tawk function will render a Tawk Live Chat.<br><br>## Enabling the Plugin<br><br>To enable the plugin add this to your project file:<br><br>```<br>$ lektor plugins add lektor-tawk<br>```<br><br>## Configuring the Plugin<br><br>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:<br><br>```<br>live_chat_code = your_live_chat_code<br>```<br><br>## In Templates<br><br>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:<br><br>```<br>&lt;div&gt;{{ render_tawk }}&lt;/div&gt;<br>```<br>
<p>This plugin adds support for Tawk to Lektor. Once the plugin is enabled a render_tawk function will render a Tawk Live Chat.</p>
<p>## Enabling the Plugin</p>
<p>To enable the plugin add this to your project file:</p>
<p><span class="docutils literal">` $ lektor plugins add <span class="pre">lektor-tawk</span> `</span></p>
<p>## Configuring the Plugin</p>
<p>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:</p>
<p><span class="docutils literal">` live_chat_code = your_live_chat_code `</span></p>
<p>## In Templates</p>
<p>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:</p>
<p><span class="docutils literal">` <span class="pre">&lt;div&gt;{{</span> render_tawk <span class="pre">}}&lt;/div&gt;</span> `</span></p>

18
plugins/lektor-yandex-metrica/index.html
View File

@ -130,23 +130,7 @@
<div class="col-sm-9 doc-styling"> <div class="col-sm-9 doc-styling">
<h2>Project Description</h2> <h2>Project Description</h2>
<p>This plugin adds support for <a href="https://metrica.yandex.com" rel="nofollow">Yandex Metrica</a> lektor-yandex-metrica<br>=====================<br><br>This plugin adds support for `Yandex Metrica &lt;https://metrica.yandex.com&gt;`_<br>to `Lektor CMS &lt;https://www.getlektor.com&gt;`_<br><br>Enabling the Plugin<br>-------------------<br><br>.. code-block:: bash<br><br> lektor plugins add lektor-yandex-metrica<br><br>Configuring the Plugin<br>----------------------<br>Just create a file named :code:`yandex-metrica.ini` in your :code:`configs/` folder and configure :code:`id` key with the provided counter id:<br><br>.. code-block:: ini<br><br> id = YOUR_COUNTER_ID<br><br>In Templates<br>------------<br>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.<br><br>.. code:: html<br><br> {{ generate_yandex_metrica() }}<br><br><br>
to <a href="https://www.getlektor.com" rel="nofollow">Lektor CMS</a></p>
<section id="enabling-the-plugin">
<h2>Enabling the Plugin</h2>
<pre><code>lektor<span class="w"> </span>plugins<span class="w"> </span>add<span class="w"> </span>lektor-yandex-metrica</code></pre>
</section>
<section id="configuring-the-plugin">
<h2>Configuring the Plugin</h2>
<p>Just create a file named <code>yandex-metrica.ini</code> in your <code>configs/</code> folder and configure <code>id</code> key with the provided counter id:</p>
<pre><code><span class="na">id</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><s>YOUR_COUNTER_ID</s></code></pre>
</section>
<section id="in-templates">
<h2>In Templates</h2>
<p>Now you can add a Yandex Metrica counter to any of your templates by just using the <code>generate_yandex_metrica</code> function in its tag as below.</p>
<pre><code>{{ generate_yandex_metrica() }}</code></pre>
</section>