Introduce a new configuration option, PLAUSIBLE_DOMAIN. If set,
include the Plausible (https://plausible.io) analytics script for that
domain.
Fixes#317.
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"]
