• I don't have Jekyll and Ruby installed
  • Installing Ruby, Jekyll, and running this project
  • Creating a new project using Jekyll
• I have Jekyll and Ruby installed, and want to run this project
  • Running the site (if you already have ruby installed)
• RSS Readers and hero-image handling
• Customize minima theme
  • Overriding files in the base theme
  • How to customize syntax highlighting
  • Documentation and references on Jekyll styling, minima customization, and SASS
• Add support for mermaid diagrams
• References
  • Running github pages locally
  • More info on Jekyll and Liquid
• Change master to main

Feb 2024 - New deployment instructions

Recently GitHub made some changes to how github pages works. This is also related to the push GitHub Actions and Ruby 3. This commit has the details.

Here are the instructions.

1. Run run.fish to build the site. The docs folder holds the entire site output.
2. Commit the changes to the docs folder. And push to main.
3. If you want to run the changes locally, you can run npm install -g serve && serve docs and open http://localhost:3000 in your browser. There is no need to use webrick and bundle exec jekyll serve anymore. You can also do the following in 2 terminals (eg in VSCode):
   1. Run watch-build.fish to rebuild the site every 30 sec
   2. Run serve docs/ to serve the site on http://localhost:3000

I don't have Jekyll and Ruby installed

Installing Ruby, Jekyll, and running this project

To use Rails on macOS, you’ll need Ruby (an interpreter for the Ruby programming language) plus gems (software libraries) containing the Rails web application development framework. Run the following commands in your terminal app.

1. xcode-select --install
2. brew install ruby
3. Go to the folder in which you've cloned this repo
4. run bundle install ⇢ like npm install, and will download deps
5. and run jekyll serve⇢ like npm run serve, will launch server

Creating a new project using Jekyll

1. In order to create a new project using Jekyll
2. Go to a folder that you want to create your new website under, eg ~/github/
3. Run jekyll new jekyll_test
4. Your new site will be created in ~/github/jekyll_test
5. Run jekyll serve to run it
6. Point your web browser to http://localhost:4000

I have Jekyll and Ruby installed, and want to run this project

Running the site (if you already have ruby installed)

After you clone the repo, go the jekyll_test folder, and

1. Run bundler → Takes the Gemfile imports and installs them
2. Run jekyll serve → Builds the static site and serves it on port 4000
3. Open http://localhost:4000 in your browser

RSS Readers and hero-image handling

Using the hero-image property in the YAML header of each MD file in _posts folder doesn't work with RSS readers (feedly and Fluent RSS reader). Here is the new (preferred) way of adding hero images so they work w/ RSS readers.

Instead of using this YAML "hero-image" property (key) it is better to remove it and just add the image directly using an img tag like so:

``<img class="post-hero-image" src="{{ 'assets/<HERO_IMAGE_HERE>' | relative_url }}"/>

I successfully tested this using Fluent RSS reader on http://127.0.0.1:4000/feed.xml.

Customize minima theme

Jekyll is configured to use minima theme. This means that there are some files that are pulled from this dependency by Jekyll when it builds the static site. This dependency is located on your computer in echo (bundle info --path minima). Save the path to an environment variable called $MINIMA_HOME using set MINIMA_HOME (bundle info --path minima).

Here is an example of the files in the $MINIMA_HOME folder.

/home/nazmul/.ruby/gems/minima-2.5.1
├── assets
│   ├── main.scss
│   └── minima-social-icons.svg
├── _includes
│   ├── disqus_comments.html
│   └── ...
├── _layouts
│   ├── default.html
│   └── ...
└── _sass
    ├── minima
    │   ├── _base.scss
    │   ├── _layout.scss
    │   └── _syntax-highlighting.scss
    └── minima.scss

As you can imagine, in order to customize this theme you can simply provide a file that is your repo that is located on a similar path to the path that is in $MINIMIA_HOME, more info here

If you edit these minima files by accident (you will need sudo access to edit them), you can simply regenerate them by running bundle install --force.

Overriding files in the base theme

The interesting files are:

1. minima.scss
2. styles.scss (which is imported by the minima.scss)

Notes:

• If we provide our own copy of these files in a similar path in this repo, then they will simply be considered overrides by Jekyll when it builds the static site.
• Think of this as operator overloading but for files. So if the minima.scss file is found in this repo, then it overrides the equivalent one in the "base" theme located in $MINIMA_HOME.
• Look at the bottom of the minima.scss file and you will see imports that pull in styles.scss and syntax.scss (used for syntax highlighting).

I've created a file ./_sass/minima.scss which overrides the corresponding file in the base theme. This is where I do a lot of big customizations, like creating variables, and using @import to bring in other .scss files. Here are some examples of this.

@font-face {
  font-family: "JetBrains Mono";
  src: url("/assets/jetbrainsmono/JetBrainsMono-Regular.woff2") format("woff2");
}

...

$brand-color: #2f9ece !default;
$text-color: #e6e6e6 !default;

...

// Import other SCSS files.
// "minima/base" - override the minima theme files.
// "minima/layout" - override the minima theme files.
// "syntax" - Custom syntax highlighting (not using minima defaults).
// "styles" - Custom styles (not using minima defaults).
@import "minima/base", "minima/layout", "syntax", "styles";

These @import statements bring in lots of other scss files. One of them handles syntax highlighting, more on this below.

Here's a ./_site/assets/main.css.map file that is generated as part of the build process (which are driven by some key-value pairs in the _config.yml file) which has a list of all the scss files that are actually imported to give a clear picture of what files are actually used to generate the single ./_site/assets/main.css file everytime Jekyll generates the static site.

{
"version"
:
3
,
"file"
:
"main.css"
,
"sources"
:
[
"main.scss"
,
"_sass/minima.scss"
,
"_sass/minima/_base.scss"
,
"_sass/minima/_layout.scss"
,
"_sass/syntax.scss"
,
"_sass/styles.scss"
]
,
"sourcesContent"
:
[
"@import \"minima\";\n"
,
"@charset \"utf-8\";\n\n@font-face {\n  font-family: \"JetBrains Mono\";\n ..."
]
,
"names"
:
[
]
,
"mappings"
:
"ACEA,UAAU,..."
}

How to customize syntax highlighting

The syntax.scss file actually contains all the syntax highlighting SCSS. This overrides whatever comes w/ minima (it does come w/ some defaults in $MINIMA_HOME/_sass/minima/_syntax-hihglihting.scss). There's a repo called pygments-css which I simply copy from. In this repo, find the styling that you like, and just copy/paste the contents of that file into the syntax.scss file as described in the comments in this file, and it will be applied when Jekyll builds the static site.

Documentation and references on Jekyll styling, minima customization, and SASS

• Jekyll docs on styling
• Minima docs
• Tutorial on customization
• SASS basics

Add support for mermaid diagrams

More info on mermaid

• mermaid install guide
• mermaid theming guide
• mermaid live editor

To add mermaid diagrams to markdown files on the site, you add snippets like the following.

<div class="mermaid">
  graph TD
    A[Christmas] -->|Get money| B(Go shopping)
    B --> C{Let me think}
    B --> G[/Another/]
    C ==>|One| D[Laptop]
    C -->|Two| E[iPhone]
    C -->|Three| F[fa:fa-car Car]
    subgraph section
      C
      D
      E
      F
      G
    end
</div>

By default, the dark theme, font, and color overrides are provided in mermaid.html. If you wish to override them you can do as follows (some of these theme variables don't work in overrides via %%{init:...}%% or specifying them in mermaid.initialize(...) block). Here's a snippet that overrides the default them and font family.

<div class="mermaid">
%%{init: {'theme': 'dark', 'themeVariables': { 'fontFamily': 'Fira Mono'}}}%%
  sequenceDiagram
    autonumber
    participant created_not_running
    created_not_running ->> running: startTicking()
    activate running
    participant running
    rect rgb(83, 82, 101, 0.25)
      loop ticking
        running ->> running: onTick()
      end
    end
    running ->> stopped: stopTicking()
    alt duration is set
      running ->> stopped: duration has passed
    end
    deactivate running
</div>

Mailchimp form for newsletter sign up

• https://us14.admin.mailchimp.com/account/connected-sites/app-selection/
• https://www.youtube.com/watch?v=zhHY4tWpFz4

Forms on Mailchimp (make sure to remove address):

⚠️ This tutorial shows how to remove the mailing address that is automatically added to many things on Mailchimp - remove your address.

• new email template
  • The mailing address was removed from here
• subscribe embedded form
  • This form is located in subscribe.html
• popup subscribe form
  • This form is configured to popup when 1/2 of a page is scrolled and appears on the right side of the page (not a modal)
• subscribe confirmation form
  • The mailing address was removed from here

References

Running github pages locally

• Setting GitHub Pages site locally with Jekyll

More info on Jekyll and Liquid

• Printing debug variables
• True and false in
• Control flow

Change master to main

The Internet Engineering Task Force (IETF) points out that "Master-slave is an oppressive metaphor that will and should never become fully detached from history" as well as "In addition to being inappropriate and arcane, the master-slave metaphor is both technically and historically inaccurate." There's lots of more accurate options depending on context and it costs me nothing to change my vocabulary, especially if it is one less little speed bump to getting a new person excited about tech.

You might say, "I'm all for not using master in master-slave technical relationships, but this is clearly an instance of master-copy, not master-slave" but that may not be the case . Turns out the original usage of master in Git very likely came from another version control system (BitKeeper) that explicitly had a notion of slave branches.

• https://dev.to/lukeocodes/change-git-s-default-branch-from-master-19le
• https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx

#blacklivesmatter