wermos / blog

Home of my own blog.

Hello!

My name is Tirthankar Mazumder.

Here is my blog website.

blog's Issues

Run GitHub Actions on PRs

Run GitHub Actions on PRs that are opened on this repo so that we can see which version bumps cause the blog to stop working, if any.

Add a spell check GitHub Action.

That way, I won't be as reliant on a pair of careful eyes and won't have to perpetually worry about making a silly spelling mistake.

GSOC enthusiasts requesting info

Hi Tirthankar,
I read your blog regarding your CERN(https://wermos.github.io/blog/gsoc/gsoc-the-application-process) gsoc. It was fantastic read. I wanted to ask you few questions that is why I opened this issue.

I have started to contribute to documentation since last month. Is it possible to get selected solely on the basis of documentation contribution ? I know python (not very good though) though and thinking of learning c++ as well. I am from electronics background so my programming skill is not that good.

What kind of coding problem you were given for cern-hsf for Qualification Task-based Organizations ? How hard it was ?

Can you guide me what to do to be selected for cern projects if start it from now?

Thanks in advance

Change background color for inline code snippets

Edit the relevant variable and put the correct color in assets/css/main.scss.

Look into the Jekyll repo's spellcheck action.

I would feel more comfortable using a spellcheck GitHub Action that is more widely used because it would mean that there is a lesser chance of it becoming unmaintained at some point.

However, as my current Action is good, and is also getting updates, I will keep this as low priority.

Move out the blog assets into their own submodule and prune Git history

Assets submodule

To be written.

Pruning Git History

To be written.

Add a scroll-to-top button.

Like the title says, add a scroll-to-top button.

Add a MathJax configuration to allow single dollar signs

Make it so that single dollar signs work, and put the content into inline math mode. Here are three references: one and two, and three.

Open links in new tabs.

As the title says, make sure that links open in new tabs so that users don't have to Ctrl + click all links to open them.

Access keys for certain shortcuts

This person's blog has certain access keys for certain actions built into his blog. For example, Alt + G is scroll-to-top, Alt + / is search, etc.

Figure out how to do the same thing in Jekyll.

Add (optional) table of contents.

A table of contents would help users get a sense of what they're getting into while reading a long blog post, and also skip to the section they're interested in.

Only load the code highlighter if it's needed.

This way, the page download size is kept small, and the load times are faster.

Add Disqus

Add Disqus or some other integration so that people can leave comments on the blog post and interact with me, the author.

Add a visitor count/flag counter to the main page.

It's a nice touch, and it would let me see how many people I am reaching.

Something like Aryaman's idea or Param's idea would nice.

Fix dead GIF links

Put new Naruto GIFs in the blog post, that are as close to the original GIFs as possible. It'd be best to use a local copy of the GIF so that we don't run into this issue in the future.

The current GIF links aren't working because gfycat (the company) went bankrupt and took down all their GIFs with them.

Add support for tabs

I want to add something like the tabs in this page: https://keqingmains.com/hu-tao/#Artifact_Sets and be able to make it look the way I want. I found a Jekyll plugin for tabs, but the CSS is underwhelming.

I will probably need to integrate Tailwind or Bootstrap with Jekyll in order to make the tabs look really nice. I will probably need Webpack for Tailwind, but I don't know how to add Bootstrap. I need to investigate this further.

Add a favicon.

Add some sort of icon to the blog so that the icon doesn't show up as the default icon on browser tabs.

Modify the MathJax configuration further.

Investigate what all those AMS configuration things that people do to their MathJax means, and if it's worth doing. Also, see if packages like mathtools can be imported in MathJax.

(Optional) Line numbers for code snippets.

Figure out how to get optional line numbers from PrismJS. We might need to fork an existing Jekyll plugin and make a few modifications to get the desired result.

Add Markdown link checker to CI

This will help us ensure that all the links in blog posts are alive.

Pointers for later: https://github.com/gaurav-nelson/github-action-markdown-link-check, https://github.com/netdata/netdata/actions/runs/5501180985/jobs/10024581953, https://github.com/netdata/netdata/blob/master/.github/workflows/docs.yml

Create a detailed README.

Write a README and specify what this repository is about.

See if a dependabot integration is useful/worthwhile.

It appears that dependabot finds out-of-date dependencies and opens a PR which updates the outdated dependency.

Perfect the code highlighting CSS

In #1, we added a code highlighter with support for line numbers, but the CSS is a bit wonky in certain cases:

The top is how we expect it to look, but for some reason, the Python one is indented too far to the right.

Investigate the jekyll-paginate-v2 plugin

Learn what pagination is and determine whether adding the jekyll-paginate-v2 plugin is worth it or not.

Investigate the jekyll-minifier plugin

Figure out how to activate it and choose what files to minify (which should be all CSS, HTML, and JS files only).

Add Markdown Lint to CI

Run the Markdown linter in CI so that any Markdown mistakes are caught in CI.

Pointers: https://github.com/marketplace/actions/markdownlint-mdl-action

See if adding GIFs works on the blog.

As the title states, see if this is something Jekyll supports out of the box. Use the first blog post as a testing ground.

Investigate multi-lingual support.

This is a bit of a longer-term thing, but it's worth investigating what the workflow for writing multilingual blog posts would be. At the very least, we would need Japanese support, with some Sanskrit and Bengali also thrown in for good measure.

Add CSS minifier

There should be some mechanism to remove the unused CSS from the final website.

Add Markdown Lint file

Use the Markdown Linter to check for any Markdown mistakes.

Write a custom Markdown style file that fits your personal use case.

Minify the JS of the blog.

Minify the JS of the blog, to allow for faster download times.

Internal links, and links to sections.

This is kind of the other side of the coin that is #23. Links to specific headings would allow the table of contents to be more useful, and also allow people to share specific portions of any blog post.

Add a search bar.

The theme allows Lunr and Algolia as search engine providers. See which one is better.

Google Custom Search is also allowed, but I'm not a fan of the way it looks.

Markdown Link Check Falsely Flags Intel websites

Currently, the Markdown Link Checker flags the Intel website links in my blog posts as broken links. However, these links are not broken as can be seen manually, or by using curl.

I have opened an issue on the relevant repo to see if the issue is due to DDoS protection, or something else.

Another interesting thing to note is that there was this commit in the llama-recipes repo which was added to address the Intel website issue.

In the meantime, I will add HTML comments to ignore those links specifically so that the CI passes.