minchinweb / blog.minchin.ca Goto Github PK

Provide a small picture to go with the summary text.

Inspiration:

• https://amandapinsker.com/reading
  • she thinks it's important to note where she read it, and so include a picture of the where as well as the book cover

Could do it through a Pelican plugin -- https://github.com/pelican-plugins/pelimoji -- (just published 3 weeks ago!) although this would require provide a set of images (Use Twitter's? (https://twemoji.twitter.com/) Provide via a plugin?)

Could do it through a Markdown extension -- https://gist.github.com/insin/815656

I like the idea of have endnotes and footnotes as sidenotes, that appear int he column beside the main body of the article.

Issues include what to do on smaller screens.

One example --> https://wejn.org/2021/12/rethinking-number-formatting/

import comments from Blogger and provide a way to add comments here

Review how Open Graph tags are implemented. More details on the protocol: https://ogp.me/

In particular, make sure that header/featured images are referenced.

Look to travis-sphinx for ideas on how to do this

An idea to lean heavily into a book metaphor, and add page numbers through the site.

Page numbers would penalty have to be provided by a (Pelican) plugin, and then the theme modified to display them.

I haven't decided whether long blog posts should be considered a single page, or to somehow indicate page breaks mid-article; the latter would definitely be more in keeping with the metaphor.

Hi 👊

This is my first visit to this fine repo, but it seems you have been working hard to keep all dependencies updated so far.

Once you have closed this issue, I'll create seperate pull requests for every update as soon as I find one.

That's it for now!

Happy merging! 🤖

I've been thinking for a while that I would like to move to a CommonMark Markdown parser. The goal would be to have consistence performance, backed by a spec that has worked through many of the edge cases. As well, the hope is to make it easier to move Markdown content between applications (like to/from Obsidian).

Also, Pelican has taken to installing a CommonMark parser (markdown-it-py) as a sub-dependency of rich, which Pelican has taken to using as a CLI output library. So we already have the parser installed!

One complication is that the original Python commonmark.py parser (available on PyPI as commonmark) has been deprecated in favour of markdown-it-py (available as markdown-it-py[plugins]).

Markdown-it-py does support plugins. This is another complication in that I use several Markdown plugins currently, and not entirely standard Markdown as is.

Another issue is how to deal with front matter; I think Pelican is using it's own standard.

Available, existing Pelican Plugins:

• Markdown-IT reader -- actually supports Markdown-it. Available on PyPI. Last updated Dec 2021. Bundles and auto-activates a few plugins
• Pelican FrontMark -- relies on the commonmark package. Available on PyPI. Last updated in Dec 2022.
  • has an open issue about dealing with dates, as expected by Pelican\
  • has an (unsubmitted) PR to allow using the MARKDOWN setting. c.f. Issue #3
• pelican_commonmark plugin -- relies on the commonmark package. Intended to be available as part of the pelican-plugins repo, but never went beyond PR from 2015.
• CommonMark for Pelican -- relies on the commonmark package. Available on PyPI. Last updated Jan 2022. I actually have an open issue (from 2016!) here due to the commonmark package changing their API, and this never got updated to match.
• pelican-gfm plugin -- actually implementing GitHub Flavoured Markdown. Never progressed past a PR for 2019.

There doesn't appear to be anything in the pelican-plugins organization.

c.f. getpelican/pelican#2984

Netlify only supports Python 2.7 or 3.8 --> https://docs.netlify.com/configure-builds/available-software-at-build-time/

My microblogging plugin requires Python 3.9, because it uses str.removesuffix().

Turns out the RSS feeds haven't been updated in the last 4 years... oops!

The in-body article images should be resized, so smaller image files can be served, rather than the large, original files.

Add the ability to "microblog".

Microblogging is generally considered to be blog posts, but very short in length.

The most common example is Twitter, with an original limit of 140 characters (to be less than the SMS max of 160 characters). Twitter has since doubled their limit to 280 characters. The default on Mastedon is 500 characters, the same as (newly released) Threads.

(Note that on Twitter, all links are run through a shortener and so are 23 characters long.)

Micro blog posts don't typically have titles, so the theme layout, slug generation, and RSS feed generation may all have to be alerted to deal with that. (On Pelican, all slugs must be unique.)

Google Webmaster tools doesn't like the URLs in the sitemap (at http://blog.minchin.ca/sitemap.xml), likely because they don't start with http:// or https://, but with //.

When I am in the page of a category or tag, pagination leads me to a non-existing page and I get a 404 error.

For example, when I'm in http://blog.minchin.ca/label/python/ and click on the 2 page, I get to http://blog.minchin.ca/label/python/2.html, which doesn't exists.

The same problem with categories. For instance: http://blog.minchin.ca/category/misc/4.html

Leaning into the paper pseudo-feel, maybe make dates published look like a stamp cancellation.

Example from Postmarks