If some talented individual could cook up a vector logo (SVG) for pelican users and their themes, we could proudly show a "Generated by Pelican" icon. :bird:

Just an idea, perhaps something like http://openclipart.org/detail/26579/pelican-with-fish-by-johnny_automatic

The AGPL is a highly viral license, which means that there are contexts where I cannot use Pelican even though I would want to.

Given that Pelican is not intended to be used as a server-side application, the GPL would preserve the same essential freedoms while allowing a greater scope for use.

I don't mean to whinge. Fundamentally, I am grateful for Pelican and for it being released as open source software. I realize that license changing bugs can be a hassle and I respect the right of authors of a work to choose how it's shared. However, I do want to make it clear that at least one of your users would rather it weren't AGPL.

to speed up the generation on really big blogs (>200 entries), Pelican should look at the rst.md file dates + html dates and skip the files that are up to date

I'm thinking we could just generate a JSON file that contains the search index, and have some client side JS search through that index and display results.

I'm not sure the best way to roll this into Pelican, however, as it seems to me that a large portion of the functionality would need to be written into the theme? Unless we have Pelican generate the index and a generic implementation of the JS search code, and have the templates just call that generic search routine to get a list of objects to style how it sees fit.

I'm thinking we could model this after Sphinx quite nicely.

I'm willing to take on this piece once there's a good plan for implementation and for rolling into Pelican.

I am trying to manually overwrite an automatically generated category page (which worked in previous versions) and I get this error:

CRITICAL: File /Users/jack/code/mine/jack.minardi.org/.source/output/projects/index.html is to be overwritten

Which I think was introduced by this commit: https://github.com/getpelican/pelican/commit/ff7410c

Is there any way to go back to the old behavior where I was able to manually write my own page to a category page.

If not, is there a different way to accomplish what I am trying to do?

Hi @justinmayer !

I just installed pelican from the latest commit and found pelican -lr to not be working on Windows. Either works, on the other hand (pelican -l or pelican -r).

I get the following output:

$ pelican -lrD
DEBUG: Pelican version: 3.7.2.dev0
DEBUG: Python version: 3.6.2
DEBUG: Adding current directory to system path
DEBUG: Temporarily adding PLUGIN_PATHS to system path
DEBUG: Restoring system path
CRITICAL: TypeError: can't pickle generator objects
Traceback (most recent call last):
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\runpy.                                                                                              py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\runpy.                                                                                              py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\Jonathan Hale\AppData\Local\Programs\Python\Python36\Scripts\pe                                                                                              lican.exe\__main__.py", line 9, in <module>
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\site-p                                                                                              ackages\pelican\__init__.py", line 563, in main
    p1.start()
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\multip                                                                                              rocessing\process.py", line 105, in start
    self._popen = self._Popen(self)
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\multip                                                                                              rocessing\context.py", line 223, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\multip                                                                                              rocessing\context.py", line 322, in _Popen
    return Popen(process_obj)
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\multip                                                                                              rocessing\popen_spawn_win32.py", line 65, in __init__
    reduction.dump(process_obj, to_child)
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\multip                                                                                              rocessing\reduction.py", line 60, in dump
    ForkingPickler(file, protocol).dump(obj)
TypeError: can't pickle generator objects
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\multip                                                                                              rocessing\spawn.py", line 99, in spawn_main
    new_handle = reduction.steal_handle(parent_pid, pipe_handle)
  File "c:\users\jonathan hale\appdata\local\programs\python\python36\lib\multip                                                                                              rocessing\reduction.py", line 87, in steal_handle
    _winapi.DUPLICATE_SAME_ACCESS | _winapi.DUPLICATE_CLOSE_SOURCE)
PermissionError: [WinError 5] Zugriff verweigert

("Zugriff verweigert" means "Access denied")

This is on a basic pelican-quickstart project, no additional plugins, content or custom theme.

Though this may be important for #2162 .

Cheers, Jonathan.

Allow for overriding individual templates from the theme by configuring the Jinja2 Environment loader to search for templates in the THEME_TEMPLATE_OVERRIDES path before the theme's templates/ directory.

Hello,

Currently, pelican will skip .md files if the "markdown" python packge is not installed. This result in a WARNING: No valid files found in content." which is extremely confusing and has made me lost 30min of debugging.

A better behavior would be to print a warning because there isn't a situation where a user would add a .md file to his content/ while not wanting it to be parsed.

Kind regards,

• Short extension names ('extra', 'meta') are deprecated
  https://pythonhosted.org/Markdown/release-2.6.html#shortened-extension-names-deprecated
• Extension config as part of extension name is deprecated
  https://pythonhosted.org/Markdown/release-2.6.html#extension-configuration-as-part-of-extension-name-deprecated

The MD_EXTENSIONS documentation in docs/settings.rst hasn't been touched, so it still shows the old value.

Hello Using Pelican version 3.2.2

→ pelican --version
3.2.2

With the current file

Title: Network Panel in Firefox 23 Developer Tools
Date: 2013-08-07
Slug: network-panel-firefox
Status: draft

[…]
![Firefox 22 Screenshot with developer tools](|filename|firefox22-devtools.jpg)

[…]
![Firefox 23 Screenshot with developer tools](|filename|firefox23-devtools.jpg)

In the current structure

→ ls -1 content/2013/08/07/
firefox22-devtools.jpg
firefox23-devtools.jpg
network-panel.md

And generating the html

→ make html

creates the output among other lines.

WARNING: Unable to find 2013/08/07/firefox22-devtools.jpg, skipping url replacement
WARNING: Unable to find 2013/08/07/firefox23-devtools.jpg, skipping url replacement

Then accessing the draft folder

http://localhost:8000/drafts/network-panel-firefox.html

Images are not displayed. Inside the HTML, the code is

<p><img alt="Firefox 23 Screenshot with developer tools" 
       src="|filename|firefox23-devtools.jpg" /></p>

make rsync_upload has the same issue

Using

RELATIVE_URLS = True

doesn't solve the issue.

What I would expect

The images to be displayed and put at the right place on 2013/08/07/firefox23-devtools.jpg.

Thanks.

Included is a new HTMLParser class that more closely mimics HTML style and also uses python's builtin HTMLParser class rather than relying on regexes.

Rather than parsing for metadata in HTML comments, it pulls metadata out of the meta tag. It also pulls the title out of the title tag. A summary can either be provided by using a summary meta tag, or by putting in an html comment into the body of the page where everything above the comment will become the summary. This last feature I gladly leave open for discussion - it is somewhat fragile, but I have seen it used in other places and should capture the intent of a summary.

I also converted the utils.open function to a proper context manager, as it would silence some errors when exit could not be found.

• [x] I have searched the issues (including closed ones) and believe that this is not a duplicate.
• [x] I have searched the documentation and believe that my question is not covered.
• [x] I am willing to lend a hand to help implement this feature.

Feature Request

Few languages are written from right to left like, Arabic, Persian Urdu and Hebrew. To display those languages correctly it requires direction support.

For more info https://rtlcss.com/learn/

It might simple to change by converting the css using rtlcss: https://rtlcss.com/playground/

Other python static site generator that supports RTL: https://squidfunk.github.io/mkdocs-material/setup/changing-the-language/#directionality

This might be more related to Theme but user should be able to set directionality in config file and standard theme should support it at least.

I'm translating the documentation into Spanish. I think that translating changelog is not worth the effort, so I'm going to leave that out.

I'm using this guide.

Related issue #2401

• [x] I have read the Filing Issues and subsequent “How to Get Help” sections of the documentation.

• [x] I have searched the issues (including closed ones) and believe that this is not a duplicate.

• OS version and name: ARMBIAN 5.31 stable Debian GNU/Linux 10 (buster) 4.19.62-sunxi

• Python version: 3.7.3

• Pelican version: 4.7.1

• Link to theme: Pelican Elegant

• Links to plugins: ['post_stats', 'pelican.plugins.related_posts', 'pelican.plugins.tipue_search', 'extract_toc', 'pelican.plugins.sitemap', 'pelican.plugins.neighbors', 'pelican.plugins.photos', 'pelican.plugins.thumbnailer', 'pelican.plugins.series', ]

• Link to your site: https://matija.suklje.name/hooks-highscores

• Link to your source: N/A

• Link to a Gist with the contents of your settings file: https://gist.github.com/silverhook/dcd30826d2b331a0819abaa386c03a08

Issue

I am using the <details> and <summary> HTML tags on my website.

When doing so, I noticed that whatever MarkDown is written within those tags gets ignored and parses verbatim as text.

For example, what I would like to do is e.g.:

<details>
<summary>Expand for images of _proof_<summary>

Some `fancy` text here to prove my **point** better.

![Screenshot: Anger Force Reloaded score summary]({static}/images/Leaderboards/AFR – 2020-11-03.jpg)
</details>

But instead I need to use HTML by hand:

<details>
<summary>Expand for images of <em>proof</em><summary>

Some <code>fancy</code> text here to prove my <strong>point</strong> better.

<img alt="Screenshot: Anger Force Reloaded score summary" src="/images/Leaderboards/AFR – 2020-11-03.jpg"/>
</details>

This is especially annoying when linking to existing static files or articles/pages in Pelican as neither {filename} nor {static} (nor {attach}) get expanded. Which means I need to predict where the file will end up, instead of letting Pelican do the heavy lifting, which is what would happen if the <details> tag was missing.

Hello, I need to add metadata (i.e: :avatar:) to author but I do not find how to. I've tested several things such as creating a dedicated profile page into /content/author/my-author.rst but content is not used my custom html.

Is there a way to do it ?

• [x] I have searched the issues (including closed ones) and believe that this is not a duplicate.

Issue

In the docs, the pagination links, "Previous" and "Next" , can vary a lot in size. Sometimes the boxes are very small and text is difficult to read. Screenshots attached!

My guess from taking a brief look is that a minimum width needs to be set somewhere. I'm happy to take this on!