zaine/org_web
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Committing extra source files

Browse Source
This commit is contained in:
Zaine Arch
2025-08-09 22:34:51 +01:00
parent 1cf2adcbf7
commit ddfbbf0718
35 changed files with 1534 additions and 454 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
blogs/2025/08/spending-the-whole-day-on-this-website.org Normal file
View File

@@ -0,0 +1,36 @@
#+TITLE: 09-08-2025: Website Changes
#+OPTIONS: num:nil title:nil
#+DATE: <2025-08-09 Sat>
#+FILETAGS: :emacs:website:
* What was worked on
I saw a few websites that used marginal notes on the right side of the screen like [[https://ogbe.net/blog/emacs_org_static_site][this one]], so I decided to try and implement this feature in this wesbite. In my mind I thought of using an external pre-configured CSS that I can just insert and ta-da it would work.
How wrong I was.
See, this website is published with ~org-publish~, meaning the org files that are written are converted to HTML through a transcoder. And as I already had a ~org.css~[fn:1] stylesheet which was primarily used for syntax highlighting, it caused some layout and formatting issue when I tried to use something like ~tufte.css~[fn:2]. Anyways, long story short, the main thing I worked on today was styling this website, and ensuring certain macros worked:
#+BEGIN_SRC emacs-lisp
(setq org-export-global-macros
(append
'(("sidenote"
. "@@html:<label for=\"sn$1\" class=\"margin-toggle sidenote-number\"></label><input type=\"checkbox\" id=\"sn$1\" class=\"margin-toggle\"/><span class=\"sidenote\">$2</span>@@")
("epigraph" . "@@html:<div class=\"epigraph\"><blockquote>$1<footer>$2</footer></blockquote></div>@@")
("epigraph_single" . "@@html:<div class=\"epigraph\"><blockquote>$1</blockquote></div>@@")
("epigraph3" . "@@html:<div class=\"epigraph\"><blockquote>$1<footer>$2, <cite>$3</cite></footer></blockquote></div>@@")
("kbd" . "@@html:<kbd>$1</kbd>@@@@latex:\\texttt{$1}@@")
("margimg"
. "@@html:<aside class=\"marginnote\"><figure class=\"mn-fig\"><img src=\"$1\" alt=\"$2\" class=\"mn-img\" loading=\"lazy\" decoding=\"async\"/>$3</figure></aside>@@")
org-export-global-macros)))
#+END_SRC
This worked quite nicely, and I made sure to make these changes accessible on smaller devices. Anyways, I quite like this style of posting. Nothing formal nor technical, just a bunch of rambling on about random things.
Oh, and also there's a darkmode theme switch now for you night owls.
[fn:1] See: https://gongzhitaao.org/orgcss/
[fn:2] See: https://edwardtufte.github.io/tufte-css/

0
blogs/2025/08/spending-the-whole-day-on-this-website.org~ Normal file
View File

18
blogs/2025/08/wacom-with-arch.org Normal file
View File

@@ -0,0 +1,18 @@
#+TITLE: Wacom With Arch
#+DATE: <2025-08-08 Fri>
#+OPTIONS: toc:nil num:nil title:nil
#+FILETAGS: :insights:
* Wacom With Arch
I purchased a [[https://www.wacom.com/en-gb/products/one-by-wacom][One by Wacom]] tablet almost 2 years ago now and it works flawlessly in both Windows and MacOS and even in most Linux distros with some configuration.
However with Arch and Hyprland, there were some issues related to the ~xserver~ it was running on. The X input driver module (e.g. xf86-input-wacom) is linked into the X server which in turn is in charge of rendering and generic input events. Hyprland on the other hand uses the Wayland display server protocol (replacement for the X protocol) hence why there is difficulty in input mapping.
I came across this issue as I was able to get the tablet to work across multiple monitors (mapping to a single one) through the ~xsetwacom~ function - which, at the time I was using Ubuntu. But with Hyprland there needs to be some manual intervention. I came across this [[https://thomaspurnell.com/003_wacom_graphics_hyprland/wacom_hyprland.html][post]] which explains nicely how to map the tablet to a single monitor. I took this approach with a slight configuration; in my ~hyprland.conf~ file, I simply added the following line:
#+BEGIN_SRC
exec-once = hyprctl keyword "device[wacom-one-by-wacom-m-pen]:output" "DP-1"
#+END_SRC
which mapped the device to the primary monitor DP-1.

6
blogs/2025/08/wacom-with-arch.org~ Normal file
View File

@@ -0,0 +1,6 @@
#+TITLE: Wacom With Arch
#+DATE: <2025-08-08 Fri>
#+OPTIONS: toc:nil num:nil title:nil
#+FILETAGS: :insights:
* Wacom With Arch

29
blogs/2025/08/what-do-i-want-to-do-with-emacs.org Normal file
View File

@@ -0,0 +1,29 @@
#+TITLE: What Do I Want To Do With Emacs
#+DATE: <2025-08-08 Fri>
#+OPTIONS: toc:nil num:nil
#+FILETAGS: :emacs:review:
I first started using Emacs (and Linux for that matter) since around the end of 2023, and it's been well over a year of trial and error with this text editor. At first I was using this for all sorts of things such as:
- Dashboard
- Agenda
- Text editing
- Magit (version controlling)
- Syncthing Management
... and the list goes on.
One thing I realised is just how powerful Emacs really is, just recently I found out that you can use the ~emoji-insert~ to insert emojis! Some have even gone to say it's an operating system in its own right. So this prompted the question today, what do /I/ want from Emacs?
After some thinking I narrowed it down and collated it in the following diagram:
[[../../../assets/sketchnotes/2025-08-08-emacs.svg]]
Of course this is the current workflow, where the text in red are items I /currently/ use Emacs for (high percentage likelihood this will increase), and the items in blue text are ones I plan on adding to my workflow. The main thing I want from this is to ensure consistency in daily practices.
- Org-roam bodies a huge aspect of the daily workflow, as it is a second brain where all information is stored.
- Learning elisp is primarily done in the scratch buffer and through projects.
- Java/Python IDE for when I'm leetcoding or doing any arbitrary project.
- Text editing mainly relates to config files for the arch setup.
- Org-agenda (more on this [[file:org-agenda-usage.org][here]]).
- Org-publish: see [[file:../../../setup.org][setup]].

29
blogs/2025/08/what-do-i-want-to-do-with-emacs.org~ Normal file
View File

@@ -0,0 +1,29 @@
#+TITLE: What Do I Want To Do With Emacs
#+DATE: <2025-08-08 Fri>
#+OPTIONS: toc:nil num:nil
#+FILETAGS: :emacs:review:
I first started using Emacs (and Linux for that matter) since around the end of 2023, and it's been well over a year of trial and error with this text editor. At first I was using this for all sorts of things such as:
- Dashboard
- Agenda
- Text editing
- Magit (version controlling)
- Syncthing Management
... and the list goes on.
One thing I realised is just how powerful Emacs really is, just recently I found out that you can use the ~emoji-insert~ to insert emojis! Some have even gone to say it's an operating system in its own right. So this prompted the question today, what do /I/ want from Emacs?
After some thinking I narrowed it down and collated it in the following diagram:
[[../../../assets/2025-08-08-emacs.svg]]
Of course this is the current workflow, where the text in red are items I /currently/ use Emacs for (high percentage likelihood this will increase), and the items in blue text are ones I plan on adding to my workflow. The main thing I want from this is to ensure consistency in daily practices.
- Org-roam bodies a huge aspect of the daily workflow, as it is a second brain where all information is stored.
- Learning elisp is primarily done in the scratch buffer and through projects.
- Java/Python IDE for when I'm leetcoding or doing any arbitrary project.
- Text editing mainly relates to config files for the arch setup.
- Org-agenda (more on this [[file:org-agenda-usage.org][here]]).
- Org-publish: see [[file:../../../setup.org][setup]].

9
blogs/zettelkasten.org → blogs/2025/08/zettelkasten.org
View File

@@ -1,5 +1,5 @@
#+TITLE: Zettelkasten Method
#+DATE: <2025-08-05 Tue>
#+DATE: <2025-08-07 Thu>
#+OPTIONS: toc:nil num:nil
#+FILETAGS: :education:
@@ -9,12 +9,13 @@ This Zettelkasten method is growing in popularity for taking notes. Ever felt as
The [[https://zettelkasten.de/introduction/][official website]] describes in detail exactly what the Zettelkasten method is, providing use cases and benefits to this method. The part I wanted to highlighted in this is the following paragraph, where the author depicts how this concept would be explained to someone unfamiliar with it:
#+BEGIN_QUOTE
{{{epigraph_single(A Zettelkasten is a personal tool for thinking and writing. It has hypertextual features to make a web of thoughts possible. The difference to other systems is that you create a web of thoughts instead of notes of arbitrary size and form\, and emphasize connection\, not a collection.
)}}}
A Zettelkasten is a personal tool for thinking and writing. It has hypertextual features to make a web of thoughts possible. The difference to other systems is that you create a web of thoughts instead of notes of arbitrary size and form, and emphasize connection, not a collection.
#+END_QUOTE
This web of thoughts is exactly what makes it useful, it takes on the seemingly cluttered /mess of information/ and is able to link the nodes together to create something meaningful and useful.
There are many personal knowledge management systems' (PKMS) out there that allow you to practice this method; the most common ones being [[https://obsidian.md/][Obsidian]] and [[https://www.orgroam.com/][Org Roam]]. After using Org Roam with Emacs for about a year or so, I realised how useful this method really is. A random idea can be jotted down and later connected to a bigger project or note system. The following picture below is a screenshot of a graph generated UI for all the nodes created in my Org Roam folder:
[[../assets/org-roam-ui-graph.png]]
[[../../../assets/images/org-roam-ui-graph.png]]

20
blogs/2025/08/zettelkasten.org~ Normal file
View File

@@ -0,0 +1,20 @@
#+TITLE: Zettelkasten Method
#+DATE: <2025-08-07 Thu>
#+OPTIONS: toc:nil num:nil
#+FILETAGS: :education:
* The Zettelkasten Method
This Zettelkasten method is growing in popularity for taking notes. Ever felt as though there's too much pieces of information but you don't know how to deal with it? This method solves exactly that problem and more. Think of it as forming a /second brain/, where you can jot down ideas and information whilst simultaneously being able to connect them together.
The [[https://zettelkasten.de/introduction/][official website]] describes in detail exactly what the Zettelkasten method is, providing use cases and benefits to this method. The part I wanted to highlighted in this is the following paragraph, where the author depicts how this concept would be explained to someone unfamiliar with it:
#+BEGIN_QUOTE
A Zettelkasten is a personal tool for thinking and writing. It has hypertextual features to make a web of thoughts possible. The difference to other systems is that you create a web of thoughts instead of notes of arbitrary size and form, and emphasize connection, not a collection.
#+END_QUOTE
This web of thoughts is exactly what makes it useful, it takes on the seemingly cluttered /mess of information/ and is able to link the nodes together to create something meaningful and useful.
There are many personal knowledge management systems' (PKMS) out there that allow you to practice this method; the most common ones being [[https://obsidian.md/][Obsidian]] and [[https://www.orgroam.com/][Org Roam]]. After using Org Roam with Emacs for about a year or so, I realised how useful this method really is. A random idea can be jotted down and later connected to a bigger project or note system. The following picture below is a screenshot of a graph generated UI for all the nodes created in my Org Roam folder:
[[../../../assets/images/org-roam-ui-graph.png]]

2
blogs/blogs-intro.org
View File

@@ -1,6 +1,6 @@
#+TITLE: Blogs Introduction
#+OPTIONS: toc:nil num:nil
#+DATE: <2025-08-08 Fri>
#+DATE: <2025-08-06 Wed>
#+FILETAGS: :introduction:
* Introduction

11
blogs/blogs-list.org
View File

@@ -1,6 +1,11 @@
#+TITLE: Blogs List
#+OPTIONS: toc:nil num:nil
* Posts:
- [[file:blogs-intro.org][Blogs Introduction]] @@html:<span class="post-date">2025-08-08</span>@@ @@html:<span class="post-tag">introduction</span>@@
- [[file:zettelkasten.org][Zettelkasten Method]] @@html:<span class="post-date">2025-08-05</span>@@ @@html:<span class="post-tag">education</span>@@
See the categories: @@html:<a href="../categories.html">Categories</a>@@
* Blogs:
- [[file:2025/08/spending-the-whole-day-on-this-website.org][09-08-2025: Website Changes]] @@html:<span class="post-date">2025-08-09</span>@@ @@html:<a href="/tags/emacs.html"> <span class="post-tag">emacs</span> </a>@@ @@html:<a href="/tags/website.html"> <span class="post-tag">website</span> </a>@@
- [[file:2025/08/wacom-with-arch.org][Wacom With Arch]] @@html:<span class="post-date">2025-08-08</span>@@ @@html:<a href="/tags/insights.html"> <span class="post-tag">insights</span> </a>@@
- [[file:2025/08/what-do-i-want-to-do-with-emacs.org][What Do I Want To Do With Emacs]] @@html:<span class="post-date">2025-08-08</span>@@ @@html:<a href="/tags/emacs.html"> <span class="post-tag">emacs</span> </a>@@ @@html:<a href="/tags/review.html"> <span class="post-tag">review</span> </a>@@
- [[file:2025/08/zettelkasten.org][Zettelkasten Method]] @@html:<span class="post-date">2025-08-07</span>@@ @@html:<a href="/tags/education.html"> <span class="post-tag">education</span> </a>@@
- [[file:blogs-intro.org][Blogs Introduction]] @@html:<span class="post-date">2025-08-06</span>@@ @@html:<a href="/tags/introduction.html"> <span class="post-tag">introduction</span> </a>@@