diff --git a/.gitattributes b/.gitattributes
index 32ba157..fd96767 100644
--- a/.gitattributes
+++ b/.gitattributes
@@ -1,2 +1,2 @@
-assets/ filter=lfs diff=lfs merge=lfs -text
-templates/images/ filter=lfs diff=lfs merge=lfs -text
+assets/* filter=lfs diff=lfs merge=lfs -text
+templates/images/* filter=lfs diff=lfs merge=lfs -text
diff --git a/.helix/languages.toml b/.helix/languages.toml
new file mode 100644
index 0000000..ab93542
--- /dev/null
+++ b/.helix/languages.toml
@@ -0,0 +1,25 @@
+[[language]]
+name = "grz"
+scope = "scope.grz"
+injection-regex = "grz"
+file-types = ["grz"]
+roots = []
+auto-format = true
+comment-token = "//"
+indent = { tab-width = 4, unit = " " }
+language-servers = ["grezi"]
+
+[[grammer]]
+name = "grz"
+
+[[language]]
+name = "djot"
+scope = "scope.djot"
+injection-regex = "dj|djot"
+file-types = ["dj"]
+roots = []
+comment-token = "{%"
+indent = { tab-width = 4, unit = " " }
+
+[[grammar]]
+name = "djot"
diff --git a/.woodpecker.yml b/.woodpecker.yml
index 44ad97f..8218473 100644
--- a/.woodpecker.yml
+++ b/.woodpecker.yml
@@ -1,7 +1,13 @@
steps:
- name: build
image: journal
+ environment:
+ BASE_URL: https://compute.nations.lol
+ CODE_THEME: emacs
+ HELIX_RUNTIME: /usr/lib/helix/runtime
commands:
- bruin-journal-gen
volumes:
- /var/woodpecker:/var/woodpecker
+ - /usr/share/fonts:/usr/share/fonts
+ - /usr/lib/helix/runtime/:/usr/lib/helix/runtime/
diff --git a/assets/Jumping.gif b/assets/Jumping.gif
index 151fa04..5ba88ee 100644
Binary files a/assets/Jumping.gif and b/assets/Jumping.gif differ
diff --git a/assets/giga_chad.jpg b/assets/giga_chad.jpg
index 7150f96..81706ac 100644
Binary files a/assets/giga_chad.jpg and b/assets/giga_chad.jpg differ
diff --git a/assets/google_cosplay.jpg b/assets/google_cosplay.jpg
new file mode 100644
index 0000000..1b1549f
--- /dev/null
+++ b/assets/google_cosplay.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:61bfb2944db74262c41e81d30d2577c7a1d3be9516b7f5b36e79f068c7b47ac6
+size 59430
diff --git a/assets/the_pipeline.svg b/assets/the_pipeline.svg
index b8a8fb2..a1c6d1d 100644
--- a/assets/the_pipeline.svg
+++ b/assets/the_pipeline.svg
@@ -1 +1,3 @@
-
\ No newline at end of file
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba624db767ebc7902e2103f57bf63cbe37b35d65739c7b1717f44a96fd51d163
+size 96905
diff --git a/src/how_to_run_a_journal.dj b/src/how_to_run_a_journal.dj
index 6541ce2..5103fb7 100644
--- a/src/how_to_run_a_journal.dj
+++ b/src/how_to_run_a_journal.dj
@@ -1,3 +1,5 @@
+`attributes`{published="2024-05-02 08:00"}
+
# Web-dev, and the Power of Simplicity.
Hi! I'm Isaac Mills, I'm the guy managing the infrastructure behind Compute! In this article, I'd like to talk about just that: the infra behind this media outlet, how it all works, and why it is the way it is.
@@ -45,7 +47,7 @@ Consider the following: If I'm accepting untrusted code from the public into my
Their pipeline checks if the library with your new code compiles to every platform it's compatible with, with every feature enabled. It also makes sure that your code is well-formatted, contains no conflicts of license, uses no libraries banned by the project, and contains no security advisories. The _only_ way this many checks can be done on every git commit, is through CI, GitHub Actions in egui's case.
-The way I've described CI so far has probably made it seem like the least simplest thing you could add to your project, but CI is actually _quite_ simple, and it's an excellent example of how capable of a tool you can make by just building simple, on top of simple, on top of simple. Really, CI is just shell scripting with extra steps. Despite it's inherent simplicity, CI can not only serve as a means to filter bugs out of pull requests, but it can also be a simple way to communicate to open source developers _what a project wants_ out of their code. Instead of having to read a big `CONTRIBUTORS.md` file to get an idea of that, developers can know that their code is good quality if it just passes CI.
+The way I've described CI so far has probably made it seem like the least simple thing you could add to your project, but CI is actually _quite_ simple, and it's an excellent example of how capable of a tool you can make by just building simple, on top of simple, on top of simple. Really, CI is just shell scripting with extra steps. Despite it's inherent simplicity, CI can serve not only as a means to filter bugs out of pull requests, but it can also be a simple way to communicate to open source developers _what a project wants_ out of their code. Instead of having to read a big `CONTRIBUTORS.md` file to get an idea of that, developers can know that their code is good quality if it just passes CI.
Fortunately, the level of CI I've described above isn't required for journalism. Our CI simply compiles our journalists' unreviewed articles, and serves them on an un-indexed (not visible on production) web page so that they and the team can preview their work before merging it. Our CI is also responsible for indexing and publishing finished articles onto our production website.
@@ -61,11 +63,11 @@ Because our CI tool is running this code, we can know which articles need compil
- Stat the changed files, which is how we know which files need to be compiled, and which files have been deleted
- Run a blame on new articles, which is how we figure out who wrote them
-- See if we are we have changed the production branch, and index new articles if so
+- See if we have changed the production branch, and index new articles if so
-Everything I've just described can be done in just ~400 lines of Rust. This is the effect of buidling simple on top of simple, _and making an effort to retain simplicity_ by making the most out of the simple building blocks.
+Everything I've described that the program can do so far can be done in just \~400 lines of Rust. This is the effect of buidling simple on top of simple, _and making an effort to retain simplicity_ by making the most out of the simple building blocks. (P.S: Our Rust code now also generates a title card image for each article, so they look better on platforms like Twitter and Discord. By using the same stradegy, I only needed to add \~230 lines to our Rust code)
-![Google cosplay is not business-critical](https://programming.dev/pictrs/image/e69b09e9-3ef6-40ff-b47b-e2ba2b4b633a.png)
+[![Google cosplay is not business-critical](assets/google_cosplay.jpg)](https://twitter.com/garybernhardt/status/1344341213575483399)
My Rust code makes heavy use of git, a very simple yet amazing tool for adding functionality to plain text.
diff --git a/templates/article.html b/templates/article.html
index 901e1fb..309a512 100644
--- a/templates/article.html
+++ b/templates/article.html
@@ -1,44 +1,65 @@
-
+