A website's `<title>` cannot contain further html formatting and
layouting elements. Thus, as already done in the article template,
additional html tags need to be stripped from the title to not appear in
verbatim in a browser's title page.
This is relevant when using TYPOGRIFY integration, as that might also
augment a page title with further html elements automatically.
problem description:
When using the i18n_subsites plugin – which is somehow supported by this
theme – the SITEURL is modified for all but the default language,
causing the construction {{ SITEURL }}/{{ CUSTOM_CSS }} to change as
well.
This in principle affects all such template constructions where SITEURL
is prepended to a custom loading path.
One exception is {{ THEME_STATIC_DIR }}, which is adjusted by the
i18n_subsites code to still match for translations.
solution:
The i18n plugin introduces an additional context variable
{{ main_siteurl }}, which always points at the original unmodified
SITEURL. As unfortunately this variable is not present in non-i18n
sites, it's existence is checked first, taking SITEURL as a fallback.
This special handling is acceptable IMHO, as at first glance I could not
find any other affected URLs in templates.
follow-up to #192
The tipue plugin registers itself as pelican.plugins.tipue_search (namespace
plugin) in the latest version see here:
7fe8f3f05c
Keep old style tipue_search to be compatible with old versions.
To use the search one would need to add "search" to DIRECT_TEMPLATES in
pelicanconf.py so that search.html is copied to the output folder:
DIRECT_TEMPLATES = ["index", "tags", "categories", "archives", "search"]
The Pelican Series plugin (https://github.com/pelican-plugins/series)
is a convenient way for authors to link articles together as multiple
installments of a series.
Add support for the Series plugin to this theme: render articles
belonging to a series with a footer pointing to the preceding and
following articles in the series, using the same styling as "related
posts" links.
This implementation is heavily inspired by the Series plugin in the
Pelican bootstrap3 theme (MIT licensed):
https://github.com/getpelican/pelican-themes/blob/master/pelican-bootstrap3/templates/includes/series.htmlFixes#289.
Article summary improvement, in case the summary consist of only 1 line.
This patch takes care that the button "Continue Reading" is shown under the article, instead of against the article.
It will be located at the same location compared to multi-line summaries.
Article summary improvement, in case the summary consist of only 1 line.
This patch takes care that the button "Continue Reading" is shown under the article, instead of against the article.
It will be located at the same location compared to multi-line summaries.
- To speed up page load the js files should be loaded on bottom of page.
- search files are only needed if you search. Move them to search page
- instantiate tipue search only on search page
This addition enables users to set their Google Measurement ID into the variable GOOGLE_GLOBAL_SITE_TAG in pelicanconf so that they can track analytics using GA 4 Closes#256 (#257)
* Add option to output canonical URL
Canonical links are handy to tell search engines which page is
canonical amongst various permutations of URLs (e.g. https vs. http
and www subdomain or not). Add an option to output one via the
following pelicanconf.py setting:
REL_CANONICAL = True
Pelican 4.5.0 changed the plugins mechanism and the default for
PLUGINS is now None. The following type of construct is used in a
number of places in Flex:
{% if 'tipue_search' in PLUGINS %}
If PLUGINS is not set in pelicanconf.py, the following exception will
be triggered under Pelican 4.5.0:
TypeError: argument of type 'NoneType' is not iterable
The Pelican maintainers did not intend the examination of PLUGINS by
templates to be a stable API (per a discussion on IRC). Per their
request, an enhancement request for a mechanism to do this has been
submitted here: https://github.com/getpelican/pelican/issues/2797
This commit changes the problematic constructs in Flex to be in the
style of:
{% if PLUGINS and 'tipue_search' in PLUGINS %}
This allows Flex to work with Pelican 4.5.0 even if users do not
define PLUGINS. Note that to use the new namespace plugins in Pelican
4.5.0, PLUGINS will have to be left at its default of None.
Resolves#245
The 300 weight of Source Code Pro is not used anywhere. This change
also updates to using Google Fonts CSS API v2 and specifying
display=swap to avoid a "flash of invisible text".
Resolves#241
