Guide to journaling

Why does this exist?

Good question, I created this journal website to act as a storage for my raw thoughts, while ideating and updating the project, it can also be used for journaling some best practices, how-to's so and so forth. Credits to my friend Prasad Raju for giving me the idea for this journal!

More or less the idea is to be pretty informal, not a very formal structure, thinking out loud and penning it down type of routine? I hope this doesn't get exhausting and can result in some good material for myself or someone else to go back and read.

How to run this project?

Of course, starting by cloning the repository, having obsidian set up and I like to open the obsidian directly in the /journals folder because I prefer writing directly into obsidian instead of updating markdown files

npm run build

I am using eleventy personally because I found it easier than Jekyll

How to add side notes?

When writing in your Markdown files (inside journals/*.md), you can now use a clean {% sidenote %} tag like this: I have yoinked this sidenote structure from Ginger bill's website when I read about it after talking to my colleague at work!

Package managers (for programming languages) are evil {% sidenote "hyperbole" %}The term “evil” is being used partially hyperbolic to
  make a point.{% endsidenote %}.

Important Details:

1. Notice the "hyperbole" part in {% sidenote "hyperbole" %}. This is the unique ID for that specific sidenote. You must give each sidenote on a page a unique ID (e.g., "note1", "note2", "hyperbole") so the mobile tap-to-expand functionality knows which note to open.
2. Everything you put between {% sidenote "id" %} and {% endsidenote %} becomes the content of the sidenote.

Frontmatter schema

---
layout: post
title: Guide to journaling
author: Asif Sayyed
excerpt: This journal contains all the little things about making / maintaining journals on this website
tags:
  - help
---

Code syntax highlighting

I tend to use a specific type of syntax highlighting for my journal code snippet, this isn't a default behavior yet, ideally it should be. but I believe taste can change and hence I haven't fixed it yet. so I like to paste this snippet below at the top of every obsidian file

<style>
.post-header h1 {
    font-size: 35px;
}
.post pre,
.post code {
    background-color: #EEEEFF;
    font-size: 13px; /* make code smaller for this post... */
}
</style>

And for now, that is it!