Article content starts here.
-See the `Pelican documentation <http://docs.getpelican.com/en/stable/content.html>`_
+See the `Pelican documentation <https://docs.getpelican.com/en/stable/content.html>`_
for details about recognized fields and how various metadata can be also
automatically extracted from the filesystem. The
`m.css Pelican theme <{filename}/pelican/theme.rst>`_ recognizes a few more
</section>
There are some special features in Pelican for easier linking to internal
-content, be sure to `check out the documentation <http://docs.getpelican.com/en/stable/content.html#linking-to-internal-content>`_.
+content, be sure to `check out the documentation <https://docs.getpelican.com/en/stable/content.html#linking-to-internal-content>`_.
The :abbr:`reST <reStructuredText>` documentation also offers more detailed
info about `inline markup <http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup>`_.
referenced in the :py:`FORMATTED_FIELDS` (such as article summaries). In order
to expand links in additional fields and arbitrary strings, this plugin
provides two Jinja2 filters, producing results equivalent to
-`links expanded by Pelican <http://docs.getpelican.com/en/stable/content.html#linking-to-internal-content>`_.
+`links expanded by Pelican <https://docs.getpelican.com/en/stable/content.html#linking-to-internal-content>`_.
For formatted fields, one can use the ``expand_links`` Jinja2 filter in the
template. The link expansion needs the content object (either ``article`` or
Unlike with the image and figure directives above, Pelican *needs* to have
the images present on a filesystem to extract size information. It's
advised to use the builtin *absolute* ``{static}`` or ``{attach}`` syntax
- for `linking to internal content <http://docs.getpelican.com/en/stable/content.html#linking-to-internal-content>`_.
+ for `linking to internal content <https://docs.getpelican.com/en/stable/content.html#linking-to-internal-content>`_.
PLUGINS += ['m.htmlsanity', 'm.abbr']
The plugin overrides the builtin Pelican
-`abbr interpreted text role <http://docs.getpelican.com/en/stable/content.html#file-metadata>`_
+`abbr interpreted text role <https://docs.getpelican.com/en/stable/content.html#file-metadata>`_
and makes its syntax consistent with other common roles of :abbr:`reST <reStructuredText>`
and m.css.
The plugin overrides the builtin docutils
`code directive <http://docutils.sourceforge.net/docs/ref/rst/directives.html#code>`_
and `code interpreted text role <http://docutils.sourceforge.net/docs/ref/rst/roles.html#code>`_,
-replaces `Pelican code-block directive <http://docs.getpelican.com/en/3.6.3/content.html#syntax-highlighting>`_ and:
+replaces `Pelican code-block directive <https://docs.getpelican.com/en/stable/content.html#syntax-highlighting>`_ and:
- Wraps Pygments output in :html:`<code>` element for inline code and
:html:`<pre>` element for code blocks with :css:`.m-code` CSS class