pastly / bm Goto Github PK

Since I'm sticking with bm for my blog needs, I figure might as well do stuff properly.

You're using the OG Markdown parser which, well, is quite outdated. No support for strikethroughs or automatic links or fenced code blocks and stuff.

I'm tempted to wrestle with shell scripts and whatnot to migrate to something more modern such as the github flavored markdown. I'm looking at https://github.com/github/cmark-gfm right now

My question is, would that be something you're interested in or am I better off just doing it for myself?

If you're at https://aadibajpai.com/blog/ and you try clicking on any of the links in the ToC then they will be broken, but if you open the post and then navigate then they'll work as expected.

I assume this one is as simple as inserting that ROOT_URL variable wherever the toc generation takes place 🤔

They get set in bm.conf.example to the contents of BLOG_TITLE and BLOG_SUBTITLE. The user is forced to set RSS_TITLE and RSS_DESCRIPTION in their bm.conf if they don't want the lame default values.

I welcome bug reports and feature requests on Github now. But I'll likely manually copy it to Gitea in order to keep track of everything in one place.

Please open issues on Gitea if you can (the email you use to make an account doesn't have to be real!), but you may open them here too.

So a lot of blogs have this cool thing where the blog post URL is like a word or two. Easy to remember, easy to share and really quite nifty. For example, posts on http://paulgraham.com/ have urls like http://paulgraham.com/genius.html or http://paulgraham.com/useful.html

Being able to do something like this if one chooses would be great, maybe through a 4th line option.

It looks like any initial whitespace gets trimmed while rendering, which is especially problematic for code snippets in a programming language where indentation is crucial like Python but also for readability I guess.

You can see the indentation is preserved in the .bm file https://github.com/aadibajpai/blog/blob/master/posts/2020/06/castorsctf-2020-writeups-DyHHAa2o.bm#L125-L134 but if you see the rendered output you'll notice there's no indentation https://aadibajpai.com/blog/p/DyHHAa2o.html#magic-school-bus

I'd be happy to try and fix it, but I'm not sure how to 🙂

Output of meta/<post_id>/toc

- <a href='#1-choose-your'>1. Choose your org early.</a>
- <a href='#2-get-acquainted'>2. Get acquainted with how version control works.</a>
- <a href='#3-quality-over'>3. Quality over quantity would be the way to go except...</a>
- <a href='#4-try-to'>4. Try to make life easier for your org.</a>
- <a href='#5-don’t-restrict'>5. Don’t restrict yourself to tasks.</a>
- <a href='#6-try-to'>6. Try to get really involved.</a>
- <a href='#7-last-but'>7. Last but not the least, be nice be respectful.</a>
- <a href='#useful-links'>Useful Links-</a>

./bm theme set terminal should provide an error message about how you should be using an index instead of a theme name. The correct command is ./bm theme set 2 (or similar).

If you see this post, you'll notice how especially large numbers don't get wrapped and continue beyond the margins.

While simply ugly on desktop, it's worse on mobile devices because the long lines squish the margins for rest of the text which hampers readability for the whole article.

Something like a scrollbar like github does

41027546415588921135190519817388916847442693284567375482282571314638757544938653824671437300971782426302443281077457253827782026089649732942648771306702020

or even text wrapping might be very useful here.