Lektor was accepted as a particpating project. For more information about
-the project there refer to the project overview on
+ Lektor was accepted as a participating project. For more information about
+the project there refer to the project overview on
RGSOC. We want to make it as easy as possible to work on Lektor during the event which
is why we will be very flexible with regards to which area interested
diff --git a/blog/2018/5/plugin-play/index.html b/blog/2018/5/plugin-play/index.html
index e437e948..9c8c8e78 100644
--- a/blog/2018/5/plugin-play/index.html
+++ b/blog/2018/5/plugin-play/index.html
@@ -85,7 +85,7 @@
Each plugin also now has its own dedicated page. On this page you can see the entire README for a plugin, in beautiful rendered Markdown or reStructuredText, GitHub statistics, authorship information, and tags. This page should give you all the information you need to be able to use the plugin, or to decide if it's what you're looking for as a guide to building your own. Plugins are tagged with specific key words or phrases that describe what they are used for and how they work. All of a plugin's tags are listed on its page as a link. Each tag has its own page where you can see other plugins that share that tag. This offers a powerful way to navigate between related content, and another way to discover more plugins. 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 Now go check out some plugins! Now go check out some plugins! Assets that correspond to directories can have children
+below them. The Lookup a child of the asset. Returns Naturally, this method always returns Assets are Source Objects that correspond to static files that
+are copied verbatim from the Usually, there is no need to manipulate Asset objects directly. Returns a query to the children of a page. Get child assetDetails
Tags
before-build-all event by looking at it's tag page here. Tag pages for events also have links back to the plugin documentation pages, including the page for that specific event.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ childrenchildren attribute provides a convenient way to access
+those. It returns an iterable of child assets.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ get_child (name, from_url=False)None if no child exists with the specified name.None unless the asset is a directory.Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ lektor.assets.Asset/assets folder to the output directory.
+
+ children
+
+
+
+
+ get_child()
+
+
+ Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
F.name literally just means
that a field by that name exists and is set to a value.
The query syntax is mostly the same in Python as well as in the Jinja 2 -templates, the main difference are and and or.
+templates, the main difference are and and or.>>> p.children.filter((F.name == 'foo') | (F.name == 'bar')).all()
[<Page model=u'page' id=u'bar'>, <Page model=u'page' id=u'foo'>]
shell command as well as from within the templates.
Static assets, copied verbatim to the output.
+ +shell command as well as from within the templates.
shell command as well as from within the templates.
shell command as well as from within the templates.
shell command as well as from within the templates.
shell command as well as from within the templates.
shell command as well as from within the templates.
shell command as well as from within the templates.
shell command as well as from within the templates.
shell command as well as from within the templates.
external can be used to also add t
domain part to the URL (if configured). The default behavior is to use the
configured URL style (which is relative) unless absolute or external were
explicitly provided. For more information read about this in the
-Project Configuration.
+Project Configuration.
{% set downloads = site.get('/downloads') %}
Path from downloads to here: {{ downloads.url_to(this) }}
This object is a configured Jinja2 environment. For more information you can -refer to the Jinja 2 Documentation.
+refer to the Jinja 2 Documentation.This is where plugins can inject additional data like custom filters, tests or global functions.
from lektor.pluginsystem import Plugin
diff --git a/docs/api/environment/render-template/index.html b/docs/api/environment/render-template/index.html
index e31dede9..f622875d 100644
--- a/docs/api/environment/render-template/index.html
+++ b/docs/api/environment/render-template/index.html
@@ -196,7 +196,7 @@ method. Here are the parameters and what they mean:
name: this is the name of the template that should be rendered. It's
the local filename relative to the templates folder and uses slashes
for paths.pad: when a Pad is available, it should be provided
+pad: when a Pad is available, it should be provided
so that the site variable can be populated. If a context is available
then the pad will also be pulled from the context if needed.this: the value of the this variable in templates. This should always
diff --git a/docs/api/plugins/events/after-build-all/index.html b/docs/api/plugins/events/after-build-all/index.html
index 2f8ba7d8..89a2a3b3 100644
--- a/docs/api/plugins/events/after-build-all/index.html
+++ b/docs/api/plugins/events/after-build-all/index.html
@@ -203,10 +203,13 @@
to the before-build-all event otherwise.
- - Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/after-build/index.html b/docs/api/plugins/events/after-build/index.html index 919289fe..213d12ff 100644 --- a/docs/api/plugins/events/after-build/index.html +++ b/docs/api/plugins/events/after-build/index.html @@ -203,10 +203,13 @@ artifact. It works pretty much exactly the same as the before-build event. -- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/after-prune/index.html b/docs/api/plugins/events/after-prune/index.html index c7a0fd7f..cb55d0eb 100644 --- a/docs/api/plugins/events/after-prune/index.html +++ b/docs/api/plugins/events/after-prune/index.html @@ -202,10 +202,7 @@This event is emitted after before Lektor searches the build directory for data that does not match a known artifact, and removes that data. This event is also emitted after a clean, that is, when the build directory is completely purged of all data.
- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/before-build/index.html b/docs/api/plugins/events/before-build/index.html index d87c1560..04b4b0d2 100644 --- a/docs/api/plugins/events/before-build/index.html +++ b/docs/api/plugins/events/before-build/index.html @@ -229,10 +229,13 @@ in future versions.- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/before-prune/index.html b/docs/api/plugins/events/before-prune/index.html index a07392e4..fdfd946e 100644 --- a/docs/api/plugins/events/before-prune/index.html +++ b/docs/api/plugins/events/before-prune/index.html @@ -202,10 +202,7 @@This event is emitted right before Lektor searches the build directory for data that does not match a known artifact. Orphaned data is then removed. This event is also emitted before a clean, that is, when the build directory is completely purged of all data.
- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/markdown-lexer-config/index.html b/docs/api/plugins/events/markdown-lexer-config/index.html index 13881f60..076a6fe3 100644 --- a/docs/api/plugins/events/markdown-lexer-config/index.html +++ b/docs/api/plugins/events/markdown-lexer-config/index.html @@ -204,10 +204,7 @@Future versions of Lektor may change its Markdown parser away from Mistune, and the various markdown related event hooks may be completely removed or work differently if that happens.
This event is emitted right after markdown renderer is made, but before it is used to render markdown. This is where lexer configuration can be set.
-- Plugins That Use This Event -
+ diff --git a/docs/api/plugins/events/markdown-meta-init/index.html b/docs/api/plugins/events/markdown-meta-init/index.html index ac29287c..058df2a5 100644 --- a/docs/api/plugins/events/markdown-meta-init/index.html +++ b/docs/api/plugins/events/markdown-meta-init/index.html @@ -215,10 +215,13 @@ -- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/markdown-meta-postprocess/index.html b/docs/api/plugins/events/markdown-meta-postprocess/index.html index 21e6dcab..c9be08db 100644 --- a/docs/api/plugins/events/markdown-meta-postprocess/index.html +++ b/docs/api/plugins/events/markdown-meta-postprocess/index.html @@ -232,10 +232,13 @@ -- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/process-template-context/index.html b/docs/api/plugins/events/process-template-context/index.html index 19ea953e..242a0e01 100644 --- a/docs/api/plugins/events/process-template-context/index.html +++ b/docs/api/plugins/events/process-template-context/index.html @@ -227,10 +227,13 @@ not be provided. -- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/server-spawn/index.html b/docs/api/plugins/events/server-spawn/index.html index 236bac8e..d956209d 100644 --- a/docs/api/plugins/events/server-spawn/index.html +++ b/docs/api/plugins/events/server-spawn/index.html @@ -231,10 +231,13 @@ used to detect server shutdowns. -- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/server-stop/index.html b/docs/api/plugins/events/server-stop/index.html index c0a835db..45cca69a 100644 --- a/docs/api/plugins/events/server-stop/index.html +++ b/docs/api/plugins/events/server-stop/index.html @@ -203,10 +203,13 @@ server-spawn which shows how to use it. -- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/plugins/events/setup-env/index.html b/docs/api/plugins/events/setup-env/index.html index d10cac0f..4ab4cbbd 100644 --- a/docs/api/plugins/events/setup-env/index.html +++ b/docs/api/plugins/events/setup-env/index.html @@ -217,10 +217,13 @@ filters and global variables. -- Plugins That Use This Event -
+ ++ A list of some plugins that make use of this event is available + here. +
+ diff --git a/docs/api/publisher/publish/index.html b/docs/api/publisher/publish/index.html index 12dbceb8..504ba249 100644 --- a/docs/api/publisher/publish/index.html +++ b/docs/api/publisher/publish/index.html @@ -180,7 +180,7 @@ and reports an error.target_url: a URL object with the parsed URL. This object comes from the
Werkzeug library and gives access to the individual parts of a URL by the
-exposed attributes (Read about the URL object).credentials: an optional dictionary with command line supplied credentials.
Note that these credentials might be completely absent and the keys which are
provided might change with future versions of Lektor.These is the list of custom filters added by Lektor in addition to the -built in filters.
+built in filters. diff --git a/docs/api/templates/globals/get-random-id/index.html b/docs/api/templates/globals/get-random-id/index.html index 042cc24c..e3fe1f99 100644 --- a/docs/api/templates/globals/get-random-id/index.html +++ b/docs/api/templates/globals/get-random-id/index.html @@ -172,13 +172,13 @@In some situations it can be very useful to generate a unique ID in templates. -This is particularly useful when creating templates for the Flow system and you need unique IDs for the DOM.
+This is particularly useful when creating templates for the Flow system and you need unique IDs for the DOM.{% set id = get_random_id() %}
<div id="{{ id }}">
<button data-target="{{ id }}" class="toggle">Hide This</button>
diff --git a/docs/api/utils/process-image/index.html b/docs/api/utils/process-image/index.html
index 24c4bcfc..8c47d904 100644
--- a/docs/api/utils/process-image/index.html
+++ b/docs/api/utils/process-image/index.html
@@ -180,7 +180,7 @@ absolute paths to the image's source and target files, the target image's
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, and exposed as an API for image-processing plugins.
+Used internally for the implementation of thumbnail, and exposed as an API for image-processing plugins.
Example
from lektor.build_programs import AttachmentBuildProgram
from lektor.context import get_ctx
from lektor.db import Image
diff --git a/docs/content/urls/index.html b/docs/content/urls/index.html
index b73a88de..f44bf7a3 100644
--- a/docs/content/urls/index.html
+++ b/docs/content/urls/index.html
@@ -228,7 +228,7 @@ an absolute or fully canonical (external) URL. For instance sitemaps or Atom
feeds do not work with relative URLs. In this case the absolute URL path has
to be configured.
You can pick the default for URL generation in the project configuration.
-For more information read about the Project Configuration.
+For more information read about the Project Configuration.
The default of relative, a relative URL style, means that you can deploy a
website to a sub folder without any configuration, however most likely custom
404 pages will fail to find the needed assets. Fully canonical URLs are not
diff --git a/docs/deployment/glpages/index.html b/docs/deployment/glpages/index.html
index d27680f0..d9e8a059 100644
--- a/docs/deployment/glpages/index.html
+++ b/docs/deployment/glpages/index.html
@@ -151,7 +151,7 @@
-
GitLab supports Lektor on their GitLab
+ GitLab supports Lektor on their GitLab
Pages infrastructure. Effectively
GitLab can build your website out of any repository on GitLab and hosts it
up on either a subdomain or a custom domain (including SSL).
@@ -216,13 +216,13 @@ To do so, you have to:
CNAME Support
If you want to use a CNAME with
GitLab pages you can configure it in the GitLab settings:
SSL/TLS Support
If you have an SSL certificate and a custom domain, you can upload your private
key and certificate to GitLab and SSL will become available on your custom
domain as well.
404 Pages
Per convention the file named 404.html is used as placeholder if a page
cannot be found. You can create such a page by creating a 404.html/contents.lr
diff --git a/docs/guides/sitemap/index.html b/docs/guides/sitemap/index.html
index ea4608b9..10f2b445 100644
--- a/docs/guides/sitemap/index.html
+++ b/docs/guides/sitemap/index.html
@@ -194,7 +194,7 @@ version the generated page and would like a clean history or a meaningful diff
from the last build.
Note that because sitemaps need to have external URLs (with scheme and
everything) you will need to configure the url of the site before the
-template starts working. For more information see Project File
+template starts working. For more information see Project File
Human Readable Sitemap
But what if you want a beautiful sitemap as a tree for human reading? This is
not any harder. Instead of making a sitemap.xml/contents.lr file just
create a sitemap/contents.lr file instead and use a template like
diff --git a/docs/plugins/dev/index.html b/docs/plugins/dev/index.html
index 9f8ea8ed..56041c6d 100644
--- a/docs/plugins/dev/index.html
+++ b/docs/plugins/dev/index.html
@@ -199,7 +199,7 @@ plugins when using them.
This should always be exactly one module named lektor_XXX where XXX
is your plugin name with underscores instead of dashes as separators.
If you need more than one module you should use a package instead. This is
-not covered here, but you can find this in the setuptools documentation.
+not covered here, but you can find this in the setuptools documentation.
entry_points: this is meta data that is needed to associate our package
with Lektor. Lektor will load all plugins in the lektor.plugins list.
It can be a list of definitions in the form plugin-name = import_path.
diff --git a/docs/plugins/howto/index.html b/docs/plugins/howto/index.html
index 4efb31b7..0afd3f67 100644
--- a/docs/plugins/howto/index.html
+++ b/docs/plugins/howto/index.html
@@ -227,7 +227,7 @@ The source image is tracked as direct source for the artifact and within the
function we also track the plugin's filename to rebuild if the plugin changes.
Adding New Field Types
Let's say you want to add an "asciidoc"
field type so you can write with AsciiDoc markup.
-First install AsciiDoc so its command-line program is available. Then update blog-post.ini from the blog guide like so:
+First install AsciiDoc so its command-line program is available. Then update blog-post.ini from the blog guide like so:
[fields.body]
label = Body
type = asciidoc # Custom type.
diff --git a/docs/plugins/publishing/index.html b/docs/plugins/publishing/index.html
index 8748520b..fbec6b8d 100644
--- a/docs/plugins/publishing/index.html
+++ b/docs/plugins/publishing/index.html
@@ -204,7 +204,7 @@ $ lektor dev publish-plugin
When you use this for the first time it will prompt you for your login
credentials for pypi. Next time it will have remembered them.
-Listing on this site
Guide
We'd love to see your new plugin listed on our plugins page. To do that, submit a pull request to this repository 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, please fill out your setup.py completely (as in the above snippet), including
+Listing on this site
Guide
We'd love to see your new plugin listed on our plugins page. To do that, submit a pull request to this repository 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, please fill out your setup.py completely (as in the above snippet), including
author and author_emailclassifiers, (optional) such as
diff --git a/docs/quickstart/index.html b/docs/quickstart/index.html
index 92a00f2a..698752d2 100644
--- a/docs/quickstart/index.html
+++ b/docs/quickstart/index.html
@@ -139,7 +139,7 @@ let Lektor generate a basic project layout for you. This requires the use of
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
-available yet just consult the Installation section of
+available yet just consult the Installation section of
the documentation.
Creating a New Project
To create a new project open a terminal and navigate to the preferred location
of your project. Then execute the quickstart command to create a new project:
diff --git a/docs/templates/videoops/index.html b/docs/templates/videoops/index.html
index 2f04c13d..dccb6377 100644
--- a/docs/templates/videoops/index.html
+++ b/docs/templates/videoops/index.html
@@ -149,7 +149,7 @@
<div class="video"><video src="{{ video|url }}"></div>
{% endfor %}
-Just like images you can also access them using site.get('/myfolder').attachments.videos or site.get('/myfolder').attachments.get('examplevideo.mp4'). Note that not all formats are detected as videos (see attachments). If your format is not in the list you may still be able to get it detected as a video by adding it to your Lektor project file.
+Just like images you can also access them using site.get('/myfolder').attachments.videos or site.get('/myfolder').attachments.get('examplevideo.mp4'). Note that not all formats are detected as videos (see attachments). If your format is not in the list you may still be able to get it detected as a video by adding it to your Lektor project file.
Accessing metadata
Video objects are sub-classes of Attachments but with a few extra properties.
diff --git a/docs/themes/installing/index.html b/docs/themes/installing/index.html
index 19122af1..5b443a0a 100644
--- a/docs/themes/installing/index.html
+++ b/docs/themes/installing/index.html
@@ -159,7 +159,10 @@ git clone https://github.com/rlaverde/lektor-theme-nix.git
If you download several themes, setting themes variable will allow you to only load
a particular theme.
Not implemented yet.
You could add the themes variable to the .lektorproject file and Lektor will
-search in the community themes and automatically install it.
+search in the
+
+community themes
+and automatically install it.
[project]
themes = lektor-theme-nix
diff --git a/docs/themes/packages/index.html b/docs/themes/packages/index.html
index 0fe44aa6..0e75916b 100644
--- a/docs/themes/packages/index.html
+++ b/docs/themes/packages/index.html
@@ -129,7 +129,7 @@
- Not implemented yet.
Themes could depend on plugins, and they will be loaded along
+
Not implemented yet.
Themes could depend on plugins, and they will be loaded along
the theme.
You could use the [packages] section of the theme.ini to install
diff --git a/index.html b/index.html
index 60d4dc73..2f3a23da 100644
--- a/index.html
+++ b/index.html
@@ -151,7 +151,7 @@ speak multiple languages and allow you to easily create localized websites.
Comments
+ + + + + +