parent
80168c8914
commit
ae9025399d
|
@ -28,7 +28,7 @@ command line scripts.
|
|||
## Template Usage
|
||||
|
||||
A ready-configured pad is always available under the `site` name which
|
||||
allows you to easily discover other pages. Here a basic example of
|
||||
allows you to easily discover other pages. Here is a basic example of
|
||||
how to do this through the [get :ref](get/) method:
|
||||
|
||||
```html+jinja
|
||||
|
|
|
@ -4,7 +4,7 @@ summary: Alternatives allow you to localize or internationalize a site.
|
|||
---
|
||||
body:
|
||||
|
||||
One particular useful feature of Lektor is the ability to define alternatives
|
||||
One particularly useful feature of Lektor is the ability to define alternatives
|
||||
to a content file. This allows you to translate your website into many
|
||||
different languages or to customize content specifically for some languages
|
||||
or regions.
|
||||
|
|
|
@ -11,7 +11,7 @@ about how to use Lektor from both a developer's as well as an end user's
|
|||
point of view. New to Lektor? Then read about [what makes Lektor
|
||||
special :ref](what/).
|
||||
|
||||
The documentation is work in progress and there will be areas that are
|
||||
The documentation is a work in progress and there will be areas that are
|
||||
lacking. If you have any feedback or you want to help out with the
|
||||
documentation project you can head over to the
|
||||
[GitHub Repository :ext](https://github.com/lektor/lektor-website) of this website.
|
||||
|
|
|
@ -8,7 +8,7 @@ allow_comments: no
|
|||
---
|
||||
body:
|
||||
|
||||
Because Lektor is quite a generic system, sometimes I might not be quite
|
||||
Because Lektor is quite a generic system, sometimes it might not be quite
|
||||
obvious what the best course of action is. This part of the documentation
|
||||
contains some guides that should help find inspiration for solving certain
|
||||
contains some guides that should help you find inspiration for solving certain
|
||||
problems.
|
||||
|
|
|
@ -5,7 +5,7 @@ summary: Quick demo of how to build a custom sitemap.xml.
|
|||
body:
|
||||
|
||||
If you want to have a `sitemap.xml` file for search engines this is something
|
||||
you can very easily create yourself. All you need for that is a contents file
|
||||
you can very easily create yourself. All you need is a contents file
|
||||
and a custom template.
|
||||
|
||||
## Contents File
|
||||
|
@ -23,7 +23,7 @@ _model: none
|
|||
This instructs Lektor to use the template `sitemap.xml` for this page. We
|
||||
also give it the empty `none` model for good measure.
|
||||
|
||||
!!! Starting with Lektor 2.0 you can also add `_discoverable: no` as field
|
||||
!!! Starting with Lektor 2.0 you can also add `_discoverable: no` as a field
|
||||
into the file to hide it from `.children`. This is useful for such special
|
||||
pages which should be excluded from navigation or automatic link generation.
|
||||
|
||||
|
|
|
@ -36,7 +36,7 @@ built into the final project. Each folder within corresponds to a record
|
|||
and the data of it is stored in the file by the name `contents.lr` within
|
||||
which is a Lektor content file. All other files are considered attachments.
|
||||
|
||||
Here a basic example layout to get an idea how this can look like:
|
||||
Here is a basic example layout to get an idea how this can look like:
|
||||
|
||||
```
|
||||
content/
|
||||
|
@ -103,5 +103,5 @@ files in there are named `<plugin-id>.ini`.
|
|||
Lektor also supports [Data Bags :ref](../../content/databags/) which go into a
|
||||
folder named `databags/`. These are files with some general information
|
||||
that can be accessed from templates. For instance you could store menus and
|
||||
navigations there, API keys and much more. This is generally just information
|
||||
navigations there, API keys and much more. This is generally just information
|
||||
you want to access from different places and maybe not keep in templates directly.
|
||||
|
|
|
@ -41,7 +41,7 @@ a child of the given path. Based on that information we automatically
|
|||
add a class to the link.
|
||||
|
||||
The index page requires a bit of special casing as we do not want it to
|
||||
be active if any of it's children are active. So we just check if the
|
||||
be active if any of its children are active. So we just check if the
|
||||
path of the current page is actually the path of the index page.
|
||||
|
||||
## Fully Automatic Navigation
|
||||
|
|
|
@ -11,12 +11,12 @@ height: 300
|
|||
----
|
||||
class:
|
||||
----
|
||||
contents:
|
||||
contents:
|
||||
#### text-block ####
|
||||
text:
|
||||
|
||||
Lektor is an [Open Source Project](../license/) and freely available to
|
||||
download. As it's currently still under heavy development and not all platforms
|
||||
download. It's currently still under heavy development and not all platforms
|
||||
are equally well supported.
|
||||
|
||||
## Command Line Interface
|
||||
|
|
Loading…
Reference in New Issue