320 lines
34 KiB
XML
320 lines
34 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<feed xmlns="http://www.w3.org/2005/Atom"><title>The Transcript</title><link href="https://www.getlektor.com/blog/" rel="alternate"></link><link href="https://www.getlektor.com/blog/feed.xml" rel="self"></link><id>urn:uuid:5bbc5195-cb84-35a2-830d-a7b199f60b13</id><updated>2020-08-20T00:00:00Z</updated><author><name></name></author><subtitle>Lektor's blog</subtitle><entry><title>Lektor 3.2 Released</title><link href="https://www.getlektor.com/blog/2020/8/lektor-32-released/" rel="alternate"></link><updated>2020-08-20T00:00:00Z</updated><author><name>Andreas Runfalk</name></author><id>urn:uuid:63bde824-43e5-3848-a5f4-eb664cd3336e</id><content type="html">
|
|
<div class="page-banner page-banner-500" style="background-image: url(coffee-ground-1171092-1599x1066.jpg)"></div>
|
|
|
|
<div class="text-block text-block-default">
|
|
<p>It's been a long time in the making, and on behalf of the Lektor Team I'm happy to introduce the 3.2 release of Lektor. As some of you may have noticed the development pace of Lektor has slowed down over the past two years. Those of you who have had open PRs for a long time, sorry for the delay and we'll try to do better going forward!</p>
|
|
<p>Recently we've made a big push to bring the project back on its feet. Our focus besides merging PRs and fixing various issues has been to streamline the CI and release process. The biggest change was the <a href="https://github.com/lektor/lektor/pull/734">switch from Travis and Appveyor to GitHub actions</a> which should make the release process a lot easier going forward.</p>
|
|
<p>We have also promoted <a href="https://github.com/lektor/lektor-tags">lektor-tags</a> and <a href="https://github.com/lektor/lektor-atom">lektor-atom</a> to official plugins. This represents our commitment to keep them up to date. We have also deployed a <a href="https://github.com/lektor/lektor-atom/pull/28">new CI workflow</a> that can publish new versions using tags. This will be something all plugin authors can use in their own projects. Thank you <a href="https://github.com/goanpeca">Gonzalo Peña-Castellanos</a> for spearheading the CI improvements.</p>
|
|
<p>A big shoutout to all the contributors who help make Lektor awesome!</p>
|
|
<div class="admonition admonition-info"><p>Since Python 2 is EOL and its <a href="https://blog.python.org/2020/04/python-2718-last-release-of-python-2.html">final release ever</a> happened on April 20th, 2020, this will be the last Lektor release with Python 2 support. This is also the last release supporting Python 3.5 since it is <a href="https://devguide.python.org/#status-of-python-branches">very near EOL</a> and we want to have opportunity to work with several benefits of Python 3.6 going forward.</p></div><div class="admonition admonition-warning"><p>The slugify change may mean that your URLs will change when you update to Lektor 3.2. This could lead to broken links from external sites such as search engines. This can be fixed by providing a custom slug for the necessary pages.</p></div><h1 id="changelog">Changelog</h1><h2 id="bugfixes">Bugfixes</h2><ul>
|
|
<li>Fix to correctly calculate relative urls from slugs that contain dots. (thank you <a href="https://github.com/f-seven">f-seven</a>)</li>
|
|
<li>Fix to allow negative integers in integer fields in the admin UI. (thank you <a href="https://github.com/davidferguson">David Ferguson</a>)</li>
|
|
<li>Fix <code>lektor plugins reinstall</code> triggered <code>on_setup_env</code> instead of just reinstalling plugins. (thank you <a href="https://github.com/germn">Mikhail Gerasimov</a>)</li>
|
|
<li>Fix failing dimensions detection for some JPEG thumbnails. (thank you <a href="https://github.com/xlotlu">Ionuț Ciocîrlan</a>)</li>
|
|
<li>Fix mismatch between reported thumbnail size and on-disk image when both width &amp; height are provided. (thank you <a href="https://github.com/xlotlu">Ionuț Ciocîrlan</a>)</li>
|
|
<li>Return JPEG dimensions swapped when EXIF rotation is in effect. (thank you <a href="https://github.com/xlotlu">Ionuț Ciocîrlan</a>)</li>
|
|
<li>Fix off-by-1px rounding discrepancy between reported thumbnail dimensions and actual dimensions. (thank you <a href="https://github.com/xlotlu">Ionuț Ciocîrlan</a>)</li>
|
|
<li>Fix off-by-one error in pagination's iter_pages in the interpretation of the right_current argument, and adding an appropriate trailing <code>None</code> for some uses. (thank you <a href="https://github.com/dairiki">Jeff Dairiki</a>)</li>
|
|
</ul>
|
|
<h2 id="new-features">New features</h2><ul>
|
|
<li>Added the ability to <a href="/docs/templates/videoops/">generate video thumbnails</a> with ffmpeg. (thank you <a href="https://github.com/runfalk">Andreas Runfalk</a>)</li>
|
|
</ul>
|
|
<h2 id="improvements">Improvements</h2><ul>
|
|
<li>Added support for setting the output_path in the project file. (thank you <a href="https://github.com/georgeyk">George Kussumoto</a>)</li>
|
|
<li>Added support for deleting and excluding files for the rsync deployment publisher. (thank you <a href="https://github.com/m-lnrs">m-lnrs</a>)</li>
|
|
<li>Several modernization and performance improvements to the admin UI (thank you <a href="https://github.com/yagebu">Jakob Schnitzer</a>)</li>
|
|
<li>Improved speed of source info updates. (thank you <a href="https://github.com/dairiki">Jeff Dairiki</a>)</li>
|
|
<li>Set colorspace to sRGB for thumbnails. This should result in significantly reduced thumbnail file size when the source image uses a more exotic colorspace. (thank you <a href="https://github.com/skorokithakis">Stavros Korokithakis</a>)</li>
|
|
<li>Now stripping profiles and comments from thumbnails, for even smaller file size. (thank you <a href="https://github.com/skorokithakis">Stavros Korokithakis</a>)</li>
|
|
<li>Improved speed of flow rendering in the admin UI. (thank you <a href="https://github.com/davidferguson">David Ferguson</a>)</li>
|
|
<li>Improved image-heavy build speeds by reducing the amount of data extracted from EXIFs. (thank you <a href="https://github.com/tgpfeiffer">Tobias Pfeiffer</a>)</li>
|
|
<li>Added the ability to collapse flow elements in the admin UI. (thank you <a href="https://github.com/jtraub91">Jason Traub</a>)</li>
|
|
<li>Now <code>extra_flags</code> is passed to all plugin events. (thank you <a href="https://github.com/nixjdm">Joseph Nix</a>)</li>
|
|
<li>Extra flags can now be passed to the <code>clean</code> and <code>dev shell</code> CLI commands. (thank you <a href="https://github.com/nixjdm">Joseph Nix</a>)</li>
|
|
<li>Deprecate the <code>crop</code> thumbnail argument in favor of the new <code>mode</code> argument, which can be one of <code>fit</code> (the default), <code>crop</code>, or <code>stretch</code>. (thank you <a href="https://github.com/xlotlu">Ionuț Ciocîrlan</a>)</li>
|
|
<li><code>upscale=False</code> for thumbnails can now prevent up scaling. (thank you <a href="https://github.com/xlotlu">Ionuț Ciocîrlan</a>)</li>
|
|
<li>Added a new CLI command <code>lektor dev new-theme</code>. (thank you <a href="https://github.com/nixjdm">Joseph Nix</a>)</li>
|
|
<li>Made admin use full UTF-8 version of RobotoSlab. Fixes missing glyphs for some languages (thank you <a href="https://github.com/yagebu">Jakob Schnitzer</a>)</li>
|
|
<li>Bumped minimum Jinja2 version to 2.11 (thank you <a href="https://github.com/nixjdm">Joseph Nix</a>)</li>
|
|
<li>Bumped filetype dependency to 1.0.7 because of API changes (thank you <a href="https://github.com/xlotlu">Ionuț Ciocîrlan</a>)</li>
|
|
<li>Relative urls are now as short as possible. (thank you <a href="https://github.com/relikd">Oleg Geier</a> and <a href="https://github.com/xlotlu">Ionuț Ciocîrlan</a>)</li>
|
|
<li>Automatically include setup.cfg configured for universal wheels when creating plugins (thank you <a href="https://github.com/georgeyk">George Kussumoto</a>)</li>
|
|
<li>Changed default slug creation to use <a href="https://github.com/un33k/python-slugify">python-slugify</a>. This should mean greater language support, but this may produce slightly different results than before for some users (thank you <a href="https://github.com/nixjdm">Joseph Nix</a> and <a href="https://github.com/xlotlu">Ionuț Ciocîrlan</a>)</li>
|
|
</ul>
|
|
|
|
</div></content></entry><entry><title>Plugin Play</title><link href="https://www.getlektor.com/blog/2018/5/plugin-play/" rel="alternate"></link><updated>2018-05-15T00:00:00Z</updated><author><name>Joseph Nix</name></author><id>urn:uuid:2fd54836-a434-3fcf-9ea2-172841724e99</id><content type="html">
|
|
<div class="page-banner page-banner-300" style="background-image: url(spices.jpg)"></div>
|
|
|
|
<div class="text-block text-block-default">
|
|
<h2 id="get-lektor-updates">Get Lektor Updates</h2><p>This site just updated the way it lists available plugins! Now <a href="https://www.getlektor.com/plugins/">https://www.getlektor.com/plugins/</a> gives you a list of all known Lektor plugins in a much more interactive and informative way. This will hopefully make it much easier for you to discover plugins that are relevant to your project and your needs. If you are a plugin developer, this should also help you find examples from existing plugins to help you learn how to interact better with Lektor's plugin system.</p>
|
|
<h3 id="categories">Categories</h3><p>Each plugin now falls within one of a few broad categories to help quickly narrow your search for what you're looking for.</p>
|
|
<h3 id="details">Details</h3><p>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.</p>
|
|
<h3 id="tags">Tags</h3><p>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.</p>
|
|
<p>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 <code>before-build-all</code> event by looking at it's tag page <a href="/plugins/tag/before-build-all/">here</a>. Tag pages for events also have links back to the plugin documentation pages, including the page for that specific event.</p>
|
|
<p>Now go check out some <a href="/plugins/">plugins</a>!</p>
|
|
|
|
</div></content></entry><entry><title>Lektor 3.1 Released</title><link href="https://www.getlektor.com/blog/2018/1/lektor-31-released/" rel="alternate"></link><updated>2018-01-29T00:00:00Z</updated><author><name>Joseph Nix</name></author><id>urn:uuid:9fdb673f-5a8c-3eab-90df-cd6d57657cbc</id><content type="html">
|
|
<div class="page-banner page-banner-500-tall" style="background-image: url(pancakes-2020863.jpg)"></div>
|
|
|
|
<div class="text-block text-block-default">
|
|
<p>Lektor continues to be discovered and used by more people, and many of these fine people have given back. Lektor is now a little easier to use, and more robust with plenty of bugfixes and added support for Python 3. Let's take a brief look at what's been done, and what we want next.</p>
|
|
<h2 id="lektor-themes">Lektor Themes</h2><p>Perhaps the most eye-catching change is the introduction of the ability for Lektor to use <a href="/docs/themes/">themes</a>. This can become a very powerful tool, allowing people to make beautiful sites even more quickly by standing on the shoulders of those who have gone before them. Why spend more time fiddling with your CSS, or template queries than you need to? If there's a theme that's similar to yours in either design or function, you can start from there. Assets, templates, models, and flowblocks are all able to be themed, offering a lot of flexibility in what they could provide.</p>
|
|
<p>This is a very new and experimental feature. We'd love to add more support for themes so that making them and using them is easy, but it may be a bit rough around the edges at the moment. The <a href="https://github.com/rlaverde">contributor</a> who gave Lektor its initial theming ability also created the <a href="https://github.com/rlaverde/lektor-theme-nix">first theme</a>, which is a simple theme based on the <a href="https://themes.gohugo.io/hugo-theme-nix/">Nix Hugo theme</a>.</p>
|
|
<p>I think this feature has a lot of potential. It's pretty exciting.</p>
|
|
<h2 id="improved-support-and-testing">Improved Support and Testing</h2><p>If you take a look at the changelog since version 2.0, you'll notice many references to bugfixes and dependency updates. We now support Python 3, and have a more extensive automated testing environment. We have upgraded the versions of Mistune (our current Markdown parser), and several JavaScript dependencies that drive the admin interface. Windows users have a few bugfixes to help them out, and added automated testing to catch more bugs before they reach a release.</p>
|
|
<h2 id="other-features">Other Features</h2><ul>
|
|
<li>Templates now have greater control of image quality and rotation.</li>
|
|
<li>Fixed and expanded handling of image EXIF data.</li>
|
|
<li>Improved date handling in the admin interface.</li>
|
|
<li>Added ability to publish from different file systems.</li>
|
|
<li>Fields can now be disabled for alternatives in the admin interface.</li>
|
|
<li>Another Plugin hook added between instantiating the Renderer and creating the Markdown Processor.</li>
|
|
<li><code>lektor dev shell</code> now uses IPython if it's installed.</li>
|
|
</ul>
|
|
<h2 id="support-for-mac-installer-paused">Support for Mac Installer Paused</h2><p>The code that was used to create the Mac installer for the Desktop App has <a href="https://github.com/lektor/lektor/issues/420">some problems</a>. We're (hopefully temporarily) pulling support for the desktop app because of this. If you have modern experience making executables (especially cross-platform) and would like to contribute, we'd love to have your support. We generally want to make Lektor as easy to use as possible, and a new desktop app could really help with that.</p>
|
|
<h2 id="want-to-contribute">Want to Contribute?</h2><p>Open Source Software lives and dies by the communities that use them, love them, and support them. If you're a developer looking to get your feet wet in OSS, we'd love to review your pull request. &lt;3</p>
|
|
<p>A larger task, if you're someone with React (and Python) knowledge, is our admin interface. It has served us pretty well so far, but it also has <a href="https://github.com/lektor/lektor/issues/458">some issues</a>. It could use some TLC.</p>
|
|
|
|
</div></content></entry><entry><title>Lektor 2.0 Released</title><link href="https://www.getlektor.com/blog/2016/4/lektor-2-released/" rel="alternate"></link><updated>2016-04-11T00:00:00Z</updated><author><name>Armin Ronacher</name></author><id>urn:uuid:a460c855-a897-3465-a8a7-212394a23eb8</id><content type="html">
|
|
<div class="page-banner page-banner-500" style="background-image: url(banner.jpg)"></div>
|
|
|
|
<div class="text-block text-block-default">
|
|
<p>After quite a bit of wait, I'm happy to announce the 2.0 release of Lektor.
|
|
Some things that previously were supposed to go into this release were pushed
|
|
out a bit more because the wait just was too long and quite a few features
|
|
were already in this release.</p>
|
|
<p>Here is the changelog of what's in this release:</p>
|
|
<ul>
|
|
<li>Added <code>_discoverable</code> system field which controls if a page should show
|
|
up in <code>children</code>. The default is that a page is discoverable. Setting it
|
|
to <code>False</code> means in practical terms that someone needs to know the URL as
|
|
all collection operations will not return it.</li>
|
|
<li>Added <code>for_page</code> function to pagination that returns the pagiantion for a
|
|
specific page.</li>
|
|
<li>Make pagination next_page and prev_page be None on the edges.</li>
|
|
<li>Allow plugins to provide publishers.</li>
|
|
<li>Added <code>|markdown</code> filter.</li>
|
|
<li>Added French translations.</li>
|
|
<li>Unicode filenames as final build artifacts are now explicitly disallowed.</li>
|
|
<li>Serve up a 404.html as an error page in the dev server.</li>
|
|
<li>Improvements to the path normalization and alt handling. This should support
|
|
URL generation in more complex cases between alts now.</li>
|
|
<li>Show a clearer error message when URL generation fails because a source
|
|
object is virtual (does not have a path).</li>
|
|
<li>Empty text is now still valid markdown.</li>
|
|
<li>Lektor clean now loads the plugins as well.</li>
|
|
<li>Basic support for type customization.</li>
|
|
<li>Fields that are absent in a content file from an alternative are now pulled
|
|
from the primary content file.</li>
|
|
<li>Development server now resolves index.html for assets as well.</li>
|
|
<li>Markdown processing now correctly adjusts links relative to where the
|
|
rendered output is rendered.</li>
|
|
<li>Added Dutch translations.</li>
|
|
<li>Added Record.get_siblings()</li>
|
|
<li>Added various utilties: build_url, join_path, parse_path</li>
|
|
<li>Added support for virtual paths and made pagination work with it.</li>
|
|
<li>Added support for Query.distinct</li>
|
|
<li>Add support for pagination url resolving on root URL.</li>
|
|
<li>Server information can now also contain extra key/value pairs that
|
|
can be used by publishers to affect the processing.</li>
|
|
<li>The thumbnails will now always have the correct width and height set
|
|
as an attribute.</li>
|
|
<li>added datetime type</li>
|
|
<li>added support for the process_image utility functions so that plugins
|
|
can use it directly.</li>
|
|
<li>added support for included_assets and excluded_assets in the project file.</li>
|
|
<li>added Spanish translations.</li>
|
|
<li>added Japanese translations.</li>
|
|
<li>added support for discovering existing alts of sources.</li>
|
|
<li>added support for image cropping.</li>
|
|
<li>added preliminary support for publishing on windows.</li>
|
|
<li>children and attachments can now have a hidden flag configured explicitly.
|
|
Attachments will also no longer inherit the hidden flag of the parent
|
|
record as that is not a sensible default.</li>
|
|
<li>changed internal sqlite consistency mode to improve performance on HDDs.</li>
|
|
<li>allow SVG files to be treated as images. This is something that does not
|
|
work in all situations yet (in particular thumbnailing does not actually
|
|
do anything for those)</li>
|
|
</ul>
|
|
<p>As always you can install the release as mentioned in the release notes.
|
|
If you had a previous version of Lektor the install process should auto
|
|
upgrade. If you use the OS X desktop build, just drag the new application over
|
|
the already existing one.</p>
|
|
|
|
</div></content></entry><entry><title>Lektor at Rails Girls Summer of Code 2016</title><link href="https://www.getlektor.com/blog/2016/3/lektor-at-rails-girls-summer-of-code/" rel="alternate"></link><updated>2016-03-17T00:00:00Z</updated><author><name>Armin Ronacher</name></author><id>urn:uuid:f1aec1d5-2464-3f3b-ac3a-181dac9fda2f</id><content type="html">
|
|
<div class="page-banner page-banner-500" style="background-image: url(banner.jpg)"></div>
|
|
|
|
<div class="text-block text-block-default">
|
|
<p>I'm happy to announce that Lektor is participating as a project in this year's
|
|
<a href="http://railsgirlssummerofcode.org/">Rails Girls Summer of Code</a> (RGSOC).
|
|
Unlike what the name would suggest, RGSOC is open for all Open Source projects
|
|
and not just Ruby.</p>
|
|
<p>The goal of RGSOC is to bring more women into programming. To quote the
|
|
website:</p>
|
|
<blockquote><p>Rails Girls Summer of Code is a global fellowship program aimed at bringing
|
|
more diversity into Open Source. Successful applicants are paid a monthly
|
|
stipend, from July-September, to work on Open Source projects of their
|
|
choice.</p>
|
|
</blockquote>
|
|
<p>Lektor was accepted as a participating project. For more information about
|
|
the project there refer to the <a href="https://railsgirlssummerofcode.org/blog/page/36/" class="ext">project overview on
|
|
RGSOC</a>.</p>
|
|
<p>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
|
|
developers want to work on.</p>
|
|
<p>If you are interested in working on Lektor you can reach out to us via
|
|
Twitter at <a href="https://twitter.com/getlektor">@getlektor</a> or
|
|
<a href="https://gitter.im/lektor/lektor"
|
|
class="js-gitter-toggle-chat-button">Gitter</a>.</p>
|
|
|
|
</div></content></entry><entry><title>Road to Lektor 2.0</title><link href="https://www.getlektor.com/blog/2016/3/road-to-lektor-2/" rel="alternate"></link><updated>2016-03-10T00:00:00Z</updated><author><name>Armin Ronacher</name></author><id>urn:uuid:657883df-54db-392e-8eb8-64572e8febcb</id><content type="html">
|
|
<div class="page-banner page-banner-500" style="background-image: url(header.jpg)"></div>
|
|
|
|
<div class="text-block text-block-default">
|
|
<p>It's great to see what people have been building with Lektor so far. It also
|
|
shows us what still needs to be built. For a lot of things we improved for
|
|
Lektor 2.0 which is going to release very soon indeed. To give you some ideas
|
|
what's going to change here is a current brief look into the changelog and
|
|
what has been changed so far.</p>
|
|
<h2 id="page-discovery">Page Discovery</h2><p>One of the biggest frustrations users have voiced is the inability to control
|
|
discoverability of pages. In Lektor 1.0 you can only hide pages entirely in
|
|
which case the build process skips over them but there was no way to hide them
|
|
by default from queries. While you could always hide pages by changing the
|
|
query, this did not work for pagination and it also required you to be quite
|
|
careful with the queries you are writing in templates.</p>
|
|
<p>In Lektor 2.0 we introduced the system <code>_discoverable</code> attribute which allows
|
|
you to easily hide pages from any query. Queries can explicitly include
|
|
undiscoverable pages but you do not need to take care of this yourself. This
|
|
makes it possible to automatically hide drafts from blogs for instance. Lektor
|
|
will still build it but without knowing the URL you cannot see it on the
|
|
overview.</p>
|
|
<h2 id="virtual-paths">Virtual Paths</h2><p>The biggest change in Lektor 2.0 is the introduction of virtual paths and
|
|
sources. This is somewhat of an under the hood change but it has big
|
|
implications on what is possible with Lektor plugins. Each page can have
|
|
virtual resources below it that can be provided by plugins. These virtual
|
|
resources are separated from the page through what is called a virtual path
|
|
which is indicated by the at-sign (<code>@</code>). For instance this blog here uses
|
|
a plugin which provides a blog archive available at <code>/blog@blog-archive</code> and
|
|
the year 2015 is available at <code>/blog@blog-archive/2015</code> etc.</p>
|
|
<h2 id="next/previous-page">Next / Previous Page</h2><p>Lektor 2.0 implements sibling support through it's virtual path system which
|
|
allows you to refer to the next or previous record easily. This is for
|
|
instance used by this blog here to link between blog posts.</p>
|
|
<h2 id="improved-alternative-support">Improved Alternative Support</h2><p>Alternatives were heavily improved. Individual fields that are absent in
|
|
content files now fall back to the primary content file. In addition it is
|
|
now possible to ask Lektor about which alternatives exist for a given source
|
|
or in total. This simplifies handling of internationalized pages greatly
|
|
but more work will be done in that field.</p>
|
|
<h2 id="improved-plugin-support">Improved Plugin Support</h2><p>Plugins now have the ability to do a few more things they could not do before:</p>
|
|
<ul>
|
|
<li>custom field types (want to render reStructuredText? You can now build a plugin)</li>
|
|
<li>custom build programs: because of the virtual source and path support you can
|
|
now build custom build programs that build things that do not exist in the
|
|
source tree. For instance you can build feeds, blog archives etc.</li>
|
|
</ul>
|
|
|
|
</div></content></entry><entry><title>Lektor Loves Travis-CI and GitHub Pages</title><link href="https://www.getlektor.com/blog/2015/12/travis-and-ghpages/" rel="alternate"></link><updated>2015-12-23T00:00:00Z</updated><author><name>Armin Ronacher</name></author><id>urn:uuid:29328c66-b90f-3afc-9a37-6cbbbf7de829</id><content type="html">
|
|
<div class="page-banner page-banner-500" style="background-image: url(header.jpg)"></div>
|
|
|
|
<div class="text-block text-block-default">
|
|
<p>Open Source projects need websites, that's a given, and one of the most popular
|
|
ways to host them these days is <a href="https://pages.github.com/" class="ext">GitHub Pages</a>.
|
|
It's a free service provided by <a href="https://github.com/" class="ext">GitHub</a> which allows
|
|
hosts a git repository as a website on a subdomain of <code>github.io</code>.</p>
|
|
<p>Wouldn't it be nice if you could easily host Lektor projects on there? Turns
|
|
out you can with the help of <a href="https://travis-ci.org/" class="ext">Travis-CI</a>. Because
|
|
Lektor has built-in support for deploying to GitHub Pages pairing up the three
|
|
is a breeze.</p>
|
|
<p>We <a href="../../../../docs/deployment/travisci/" class="ref">created a guide</a> and also recorded
|
|
a screencast that goes with it:</p>
|
|
<iframe width="100%" height=410 frameborder="0" allowfullscreen="allowfullscreen"
|
|
src="https://www.youtube.com/embed/3pj_EyZIL5A?autoplay=0&fs=1">
|
|
</iframe>
|
|
</div></content></entry><entry><title>Hello Lektor!</title><link href="https://www.getlektor.com/blog/2015/12/hello-lektor/" rel="alternate"></link><updated>2015-12-21T00:00:00Z</updated><author><name>Armin Ronacher</name></author><id>urn:uuid:16dbb267-fb7c-3988-aae1-07106bd5bfb7</id><content type="html">
|
|
<div class="page-banner page-banner-500" style="background-image: url(banner.jpg)"></div>
|
|
|
|
<div class="text-block text-block-default">
|
|
<p>About <a href="http://w3techs.com/technologies/details/cm-wordpress/all/all">25% of the Internet uses
|
|
Wordpress</a> and
|
|
it's estimated that about 50% of Wordpress installations out there are
|
|
vulnerable to security problems because they have not been updated. This is a
|
|
very high number.</p>
|
|
<p>Because I know how much work it can be to keep software updated and my own
|
|
terrible track record of spending time of updating everything I'm running
|
|
I kept getting increasingly frustrated with the lack of software that would
|
|
allow me to run a simple website in a secure manner without having to resort
|
|
to all kinds of user-unfriendly hackery.</p>
|
|
<p>While there are many static site generators none of them really matched what I
|
|
actually wanted: a content management system that just happens to run
|
|
on the client. Most static website generators are too “hacker focused” in the
|
|
sense that they could not be used by people without programming experiences or
|
|
they are full fledged content management systems that need a server to run on
|
|
or require regular maintenance for security updates.</p>
|
|
<p>There the hacker's favorite projects like
|
|
<a href="https://github.com/getpelican/pelican">Pelican</a> or
|
|
<a href="https://jekyllrb.com/">Jekyll</a> which support generating websites out of static
|
|
files that are tracked through version control and there are CMS systems like
|
|
<a href="http://statamic.com/">Statamic</a> which store all of its data in flat files
|
|
— but as mentioned — needs PHP.</p>
|
|
<p>None of those were what I was looking for. Static file generators like Jekyll
|
|
are nice in a way but not just end user unfriendly, but also very limited in
|
|
what you can do with them. They are more suited for building blogs than
|
|
more complex sites. I tried a bunch of them and built different things
|
|
with them, but ultimately always felt like something was missing.</p>
|
|
<p>After about two years of frustration with that situation I finally sat down
|
|
and spend some time working on a system to solve this problem. May I
|
|
introduce: Lektor.</p>
|
|
<h2 id="what-is-lektor">What is Lektor?</h2><p>Lektor combines the experience of using a content management system like
|
|
Wordpress with a static website generator like Jekyll and has some of the
|
|
flexibility of a web development framework like Django. It can run locally
|
|
on your computer and deploy to remote servers. All source assets are stored
|
|
either in version control or Dropbox and when you are satisfied with the end
|
|
results, you can push them online from the UI to a remote server.</p>
|
|
<p>And this is what it roughly looks like when you look at the admin panel:</p>
|
|
<div class="screenshot-frame"><img src="admin.png"></div><h2 id="how-do-i-use-it">How do I use it?</h2><p>That depends on who you are. Lektor is based on the idea that there are
|
|
two parties to a website: the web developers and the editors. The former
|
|
create the design, layout, data layout and configures Lektor in general. The
|
|
latter change the contents of the website according to the general setup.</p>
|
|
<p>If you are a web developer you can install two versions of Lektor: you can
|
|
use the command line client or if you are on a Mac, you can install the
|
|
desktop version. Either version comes with a handy web interface that
|
|
can be used to preview and edit all pages.</p>
|
|
<p>Once you have configured Lektor to your liking you can put the project into
|
|
version control (or just Dropbox) and let your users modify the contents. All
|
|
they have to do is to install the Desktop version of Lektor, double click the
|
|
project in their Dropbox and start changing it.</p>
|
|
<p>If you just want to edit the contents of a project you can install the
|
|
Desktop version or maybe in the future use a cloud hosted version.</p>
|
|
<h2 id="project-layout">Project Layout</h2><p>To get an idea how it works, you can have a look at the <a href="https://github.com/lektor/lektor-website/">github repository of
|
|
this website</a> which contains the
|
|
project for this website and blog and have a look at the introduction
|
|
documentation: <a href="../../../../docs/quickstart/" class="ref">Getting Started</a>. You can
|
|
also find a screencast there.</p>
|
|
<p>On a very basic level Lektor takes <code>.lr</code> files which are basic text files
|
|
with a super simple format and generates out HTML files. The <code>.lr</code> files
|
|
correspond to a previously set up data model. They are pure text format for
|
|
key/value pairs. Each pair is separated by three dashes (<code>---</code>):</p>
|
|
<pre><code>field_1: value
|
|
---
|
|
field_2:
|
|
|
|
a longer value
|
|
</code></pre>
|
|
<p>You can set up data models for simple things like blog posts but also more
|
|
elaborate ones if you want to build portfolio sites. For instance you could
|
|
set up models for your projects and then access that data in the templates.</p>
|
|
<p>The content files are stored in folders in a tree like structure and at any
|
|
level you can add other files as attachments:</p>
|
|
<div class="screenshot-frame"><img src="structure.png"></div><h2 id="an-open-source-project">An Open Source Project</h2><p>Lektor is available under <a href="../../../../license/">a BSD license</a> and run as a
|
|
community Open Source project <a href="https://github.com/lektor/lektor/" class="ext">on github</a>.
|
|
The build system is written in Python, the UI in JavaScript with React and
|
|
the GUI components use Electron.</p>
|
|
<h2 id="feedback-appreciated">Feedback Appreciated</h2><p>Lektor took two attempts to get into a usable application and I'm sure that
|
|
there is more that needs to be done to scratch the needs of most users.
|
|
However I also know that there is no point in delaying an initial release
|
|
unnecessarily. What's being released today is the application as it exists
|
|
today and I think it's in a good shape to build really cool websites with
|
|
it. I welcome you to give it a try and give feedback on what you think
|
|
about it.</p>
|
|
|
|
</div></content></entry></feed> |