Bump the ci-dependencies group across 1 directory with 4 updates

Bumps the ci-dependencies group with 4 updates in the / directory: [actions/checkout](https://github.com/actions/checkout), [actions/setup-node](https://github.com/actions/setup-node), [actions/cache](https://github.com/actions/cache) and [rlespinasse/github-slug-action](https://github.com/rlespinasse/github-slug-action).


Updates `actions/checkout` from 6 to 7
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v6...v7)

Updates `actions/setup-node` from 6 to 7
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](https://github.com/actions/setup-node/compare/v6...v7)

Updates `actions/cache` from 5 to 6
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/v5...v6)

Updates `rlespinasse/github-slug-action` from 5.6.0 to 5.7.0
- [Release notes](https://github.com/rlespinasse/github-slug-action/releases)
- [Commits](https://github.com/rlespinasse/github-slug-action/compare/v5.6.0...v5.7.0)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: ci-dependencies
- dependency-name: actions/checkout
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: ci-dependencies
- dependency-name: actions/setup-node
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: ci-dependencies
- dependency-name: rlespinasse/github-slug-action
  dependency-version: 5.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: ci-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>

.github/workflows/build-preview.yaml

@@ -11,17 +11,17 @@ jobs:
     runs-on: ubuntu-latest
     name: Build Preview
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
       - name: Setup Node
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v7
         with:
           node-version: 22
 
       - name: Cache dependencies
-        uses: actions/cache@v5
+        uses: actions/cache@v6
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
@@ -29,7 +29,7 @@ jobs:
             ${{ runner.os }}-node-
 
       - name: Cache Quartz plugins
-        uses: actions/cache@v5
+        uses: actions/cache@v6
         with:
           path: .quartz/plugins
           key: ${{ runner.os }}-plugins-${{ hashFiles('quartz.lock.json') }}

.github/workflows/ci.yaml

@@ -19,17 +19,17 @@ jobs:
     permissions:
       contents: write
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
       - name: Setup Node
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v7
         with:
           node-version: 24
 
       - name: Cache dependencies
-        uses: actions/cache@v5
+        uses: actions/cache@v6
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
@@ -37,7 +37,7 @@ jobs:
             ${{ runner.os }}-node-
 
       - name: Cache Quartz plugins
-        uses: actions/cache@v5
+        uses: actions/cache@v6
         with:
           path: .quartz/plugins
           key: ${{ runner.os }}-plugins-${{ hashFiles('quartz.lock.json') }}
@@ -64,11 +64,11 @@ jobs:
     permissions:
       contents: write
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
       - name: Setup Node
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v7
         with:
           node-version: 24
       - name: Get package version

.github/workflows/deploy-v5.yaml

@@ -16,17 +16,17 @@ jobs:
     runs-on: ubuntu-latest
     name: Deploy v5 to Cloudflare Pages
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
       - name: Setup Node
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v7
         with:
           node-version: 24
 
       - name: Cache dependencies
-        uses: actions/cache@v5
+        uses: actions/cache@v6
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
@@ -34,7 +34,7 @@ jobs:
             ${{ runner.os }}-node-
 
       - name: Cache Quartz plugins
-        uses: actions/cache@v5
+        uses: actions/cache@v6
         with:
           path: .quartz/plugins
           key: ${{ runner.os }}-plugins-${{ hashFiles('quartz.lock.json') }}

.github/workflows/docker-build-push.yaml

@@ -21,11 +21,11 @@ jobs:
           echo "OWNER_LOWERCASE=${OWNER,,}" >> ${GITHUB_ENV}
         env:
           OWNER: "${{ github.repository_owner }}"
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 1
       - name: Inject slug/short variables
-        uses: rlespinasse/github-slug-action@v5.6.0
+        uses: rlespinasse/github-slug-action@v5.7.0
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v4
       - name: Set up Docker Buildx

.gitignore

@@ -11,3 +11,4 @@ replit.nix
 .quartz/
 quartz/cli/tui/dist/
 .obsidian/workspace.json
+.trash/

.obsidian/app.json

@@ -4,5 +4,7 @@
     "public/",
     "quartz/",
     "node_modules/"
-  ]
+  ],
+  "showUnsupportedFiles": false,
+  "promptDelete": false
 }

.obsidian/appearance.json

@@ -1,5 +1,5 @@
 {
   "cssTheme": "Retroma",
-  "textFontFamily": "",
+  "textFontFamily": "Sono",
   "monospaceFontFamily": ""
 }

.obsidian/community-plugins.json

@@ -1,5 +1,6 @@
 [
   "dataview",
   "quartz-syncer",
-  "obsidian-style-settings"
+  "obsidian-style-settings",
+  "obsidian-excalidraw-plugin"
 ]

.obsidian/plugins/obsidian-excalidraw-plugin/manifest.json

@@ -0,0 +1,12 @@
+{
+  "id": "obsidian-excalidraw-plugin",
+  "name": "Excalidraw",
+  "version": "2.25.2",
+  "minAppVersion": "1.8.7",
+  "description": "Sketch Your Mind. Edit and view Excalidraw drawings. Enter the world of 4D Visual PKM.",
+  "author": "Zsolt Viczian",
+  "authorUrl": "https://excalidraw-obsidian.online",
+  "fundingUrl": "https://ko-fi.com/zsolt",
+  "helpUrl": "https://github.com/zsviczian/obsidian-excalidraw-plugin#readme",
+  "isDesktopOnly": false
+}

.obsidian/plugins/obsidian-style-settings/data.json

@@ -1,5 +1,5 @@
 {
-  "retroma-obsidian-theme@@theme-font-selection": "retroma-font-w95font",
+  "retroma-obsidian-theme@@theme-font-selection": "default",
   "retroma-obsidian-theme@@theme-color-scheme-selection": "cs-monochromatic-colors",
   "retroma-obsidian-theme@@theme-variant": "Groovy",
   "retroma-obsidian-theme@@window-border-radius": "6px",

.obsidian/types.json

@@ -0,0 +1,8 @@
+{
+  "types": {
+    "aliases": "aliases",
+    "cssclasses": "multitext",
+    "tags": "tags",
+    "date": "date"
+  }
+}

.space/waypoints.json

@@ -0,0 +1 @@
+[{"name":"Home","sticker":"ui//home","paths":["/"]},{"sticker":"lucide//folder-git-2","name":"Site","paths":["content"]}]

content/fnn/.space/def.json

@@ -0,0 +1 @@
+{"_joins":[],"_contexts":[],"_links":[],"_sort":{"field":"rank","asc":false,"group":false,"recursive":false},"_template":"","_templateName":"","defaultSticker":"","defaultColor":"","readMode":false,"fullWidth":false}

content/fnn/BARQ Public Statement.md

@@ -0,0 +1,76 @@
+---
+date: 2026-07-15
+publish: true
+tags:
+  - furry
+  - barq
+  - babyfurs
+  - furry-drama-cycle
+  - anthrocon-2026
+---
+
+Full text of the public statement, as posted to Twitter July 15, 2026, at 10:14 AM EDT:
+
+> Apologies for the long wait.
+> We want to give some clarification on what happened last week with the posting and removal of our statements regarding Flame and the babyfur community.
+> 
+> At Anthrocon, the BARQ!Cast held a panel where Flame was invited as a guest. After that panel we saw Flame making hateful comments toward the babyfur community on X. Because this goes against everything BARQ! stands for, we decided to quickly put out a statement distancing ourselves from Flame.
+> 
+> This was agreed upon by our social media team and directors. Looking back at the first statement, we felt it was too vague. We decided to post a second one, which was also agreed upon by all involved.
+> 
+> A day later we found out the second statement was only posted on Bluesky. We tried to fix that apparent mistake by posting it on X too. When our social media team noticed the new posts, they told us they hadn't posted it to X on purpose and in a panic, they deleted both statements from X and Bluesky.
+> 
+> What followed was a lot of confusion, both within the team and our community. We decided to pause posting anything on this matter and discuss / reflect on what happened first. We found the biggest factor in this was that we never talked about who is responsible for what, and that some decisions were made without consulting the others who are involved. 
+> 
+> We want to make it clear we still stand behind both statements, and that babyfurs are part of the community and welcome on BARQ! just as every other furry. We agreed on clearer responsibilities and clear lines of communication to make sure this will not happen again.
+> Discrimination has no place on BARQ!
+> 
+> - BARQ! Directors
+
+Some things of note:
+
+> Looking back at the first statement, we felt it was too vague. ==We decided to post a second one, which was also agreed upon by all involved.==
+
+Was the *decision to make a post* agreed upon or the *content of the post itself*?
+
+> A day later ==we found out the second statement was only posted on Bluesky. We tried to fix that apparent mistake by posting it on X too.==
+
+So you okayed the post with the social media team, gave them the go-ahead on posting, but they independently chose to only post to Bluesky...
+
+> \[... the social media team] told us ==they hadn't posted it to X on purpose== ... 
+
+...why? Were they attempting to tailor different messages for each platform? Why not just post the same message to both? It's a public statement disavowing a person with negative views toward a sizable segment of the community...wouldn't you want to post this literally everywhere?
+
+> \[...] we ==never talked about who is responsible for what== ...
+
+If I were working for your company on the social media team, I would think my team would be the ones responsible for...social media. Including making and releasing public statements that affect the company's public image. Otherwise, if there were a Public Relations person or department or a designated public company spokesperson, I'd defer to them. 
+
+> \[...] some decisions were made ==without consulting the others who are involved==.
+
+Social media team's director went rogue and decided to only post the message to Bluesky because they didn't want to moderate the potential wave of negativity that posting the same exact message on X might cause? 
+
+p.s. Who is Flame anyway?
+
+![](https://x.com/Beykick125/status/2073130143644602431)
+
+https://x.com/flamethefawn
+- 20
+
+> this is the last time i'm going to speak on this issue, anything i have said is not a reflection on @barqOfficial as a company, it is strictly my own opinion.
+> 
+> i stated in my initial apology that i regretted my wording and calling for violence, which is true i do regret that. i also would like to say that yes, i have made generalizations in response to generalizations and personal attacks made against me which was also not right. the world isn't black or white and i believe that i was wrong for letting that worldview bleed into my comments
+> 
+> fuck pedophilia, wherever it lays. i see a glaring issue within the furry community with how we turn a blind eye to these predators that prey on our own community members. they are terrible people and it deeply upsets me. 
+> 
+> not every person who has an abdl kink or who is a babyfur is a bad person and i don't believe we should be violent towards people who are into things that you may not be into. i want to make my position clear on that.
+> 
+> i am not sorry for having my own opinions, if you dissent them then that is totally fine as well. babyfurs and furries as a whole need to do better rooting out pedophilia, \[zoophilia], and other aspects of our community that are morally abhorrent
+> [source](https://x.com/flamethefawn/status/2077426761751756988)
+
+> i think people don't realize how influential this new young wave of furries my age are, and how awesome the changes we are going to bring will be :3
+
+not sure what this even means, but not sure i want to be here for it either.
+
+i can see why there's a trend recently for new conventions to be 21+.
+
+as long as you're not a puritanical dickhead, I think we'll get along fine. that "morally abhorrent" language veers mighty close to "degenerate" if you ask me. *but that's just my opinion.*

content/fnn/TailTag App Discussion.md

@@ -0,0 +1,76 @@
+---
+publish: true
+aliases:
+  - tailtag
+created: 2026-07-12T17:55:57.560-04:00
+modified: 2026-07-12T18:24:12.896-04:00
+tags:
+  - furry
+  - AI
+  - vibe-coding
+description: "tl;dr: TailTag (fursuit \"catching\" app to promote socialization with suiters) had backend access open to normal users, some of whom were able to view other users' email addresses and private posts. The app is offline until patches can be applied."
+---
+
+> [!warning] Update - 7/13/2026
+> Finn posted a [final response](https://x.com/FinnThePanther/status/2076675644755505535) and a [postmortem report](https://docs.google.com/document/d/17dEvlj6qy71u9dNB_yyk9bH6ywOdj5PpET3bqc8X-RI/edit?pli=1&tab=t.0#heading=h.8gfmgngubb2w) detailing what happened and the steps that will be taken to delete the app data. Finn says he will not move forward with rebuilding the application unless members of the community help out.
+
+not a journalist, just a dog who went to school for it (kind of) and collated the work done by several others; links included with information as well as in footnotes below the article
+
+[**TailTag**](https://www.playtailtag.com), a recently released furry social app, was breached on July 11, 2026, leading app creator Finn the Panther to shut down the app temporarily while security issues are being addressed.
+
+> [!tip]+ sources, yo
+> super props & excellent thread discussing this incident: 
+> [quat's (@highlysuspect.agency) thread about TailTag on bsky](https://bsky.app/profile/highlysuspect.agency/post/3mqhuc6bwds2r)
+
+users were first made aware of the breach when they received a strange push notification from the app titled "IMPORTANT ANNOUNCEMENT" with the message body consisting primarily of "meows" and other cat noises.
+
+![the notification in question](https://cdn.bsky.app/img/feed_fullsize/plain/did:plc:ulpgvc4gwpwrkyojtvkgp6bx/bafkreigbvhubsqqjvshaooffh543vbruyehxuyn6xam4tyvyayf6usy7ey)
+
+Finn's response:
+
+![finn's response](https://x.com/FinnThePanther/status/2076144492558872939)
+
+![second response](https://x.com/FinnThePanther/status/2076237596028723583)
+
+twitter user **@twnlink** did a lot of digging on this and discovered backend access was not entirely restricted to admins:
+
+![](https://x.com/twnlink/status/2076177625433731536)
+
+twitter user [**@Benaclejames**](https://x.com/Benaclejames) posted the following technical write-up of the vulnerabilities discovered on their Notion page: https://app.notion.com/p/TailTag-Vulnerabilities-39bd16d9d17180fa9279ec92bbe19549
+
+[**@FloppyMinty**](https://x.com/FloppyMinty) was able to confirm the app's backend information was still publicly accessible as of June 12th.[^2] Finn did later state in a separate post that the applied fix to the notifications issue should have fixed the access control issues as well.[^6] while no user passwords were compromised, just about every other bit of personally identifiable information that users entered into the application is publicly accessible, including email addresses and photos.[^1] as of writing, other than the publicly disclosed accesses of backend information already mentioned, there is no evidence any others have accessed or posted any data from the application.
+
+on July 12, 2026, Finn posted the following response:
+
+> On July 11, 2026, an unauthorized individual created several TailTag accounts and exploited an overly permissive profile-access rule to retrieve their full user profile records via the publicly accessible TailTag domain. This profile-access rule, originally designed so you could see the profile of whose fursuit you caught, included general profile information, along with account and app preferences, and technical identifiers used to deliver push notifications. In addition, a separate control requiring server authorization before notifications could be delivered that was assumed to be on by default had not been enabled. Together, these issues allowed the individual to send an unauthorized notification that appeared to come from TailTag itself. Once the incident was identified, I disabled all notification delivery, enabled the additional authorization requirement, rotated the relevant credential, blocked the accounts involved, revoked their sessions, and restricted profile access. Based on my investigation, I found no evidence that passwords or login credentials were accessed or that the individual gained access to other users' accounts to remove or otherwise manipulate user data. Notifications remain disabled while I complete longer-term security improvements.
+>
+> As benign as the notification content was, this was still a serious design oversight that will not be taken lightly, and I personally apologize for both the unintended app behavior, but more importantly, the loss of trust in the security of TailTag. I got caught up in the excitement of getting this project out for all of you to play that I overlooked some important details regarding account access control that resulted in this compromise. I suggest changing your password if you haven't already and be wary of any emails that look suspicious or ask for you to log in with TailTag credentials. If you choose to delete your account due to this, your data will be removed with no questions asked.
+>
+> I am still confident in the value that TailTag brings to the community and do not have any immediate plans to shut it down. However, I will be moving much more carefully in its development, including pausing any feature work until I am confident in account security. If you have any questions, please reach out and I will answer them for you.
+>
+> Many valuable lessons were learned this weekend. I will be doing my best to not only prevent something like this from happening again, but to gain your trust back for this project. [^3]
+>
+> \[in later tweets in reply to this original image post]:
+> If you would like to assist with future security, access control, or any other parts of the app, please reach out. I am happy to discuss how you can help.[^4]
+
+in the interim, TailTag has been **taken offline** until further notice.[^5]
+
+most of the comments in response to Finn's own statement were questions about the amount of AI assistance used in the creation of the app. Finn did say "LLMs were involved in the implementation of designs \[he] wrote in English."[^7]
+
+TailTag's website is still online as of writing. Updates to both the site and application are likely, though no timetable has been announced.
+
+change your passwords, folks, you'll be alright.
+
+[^1]: @BenacleJames: _TailTag Vulnerabilities_ - https://app.notion.com/p/TailTag-Vulnerabilities-39bd16d9d17180fa9279ec92bbe19549
+
+[^2]: @FloppyMinty: "PSA: If you used TailTag, your email among other metadata has been compromised." https://x.com/FloppyMinty/status/2076320147233493306
+
+[^3]: @FinnThePanther, X: "About yesterday's incident." https://x.com/FinnThePanther/status/2076351285415276672
+
+[^4]: https://x.com/FinnThePanther/status/2076351646662345102
+
+[^5]: https://x.com/FinnThePanther/status/2076401056414900312
+
+[^6]: Finn said "the fix should have addressed this as well" a [couple of hours later](https://x.com/FinnThePanther/status/2076357929083801789)
+
+[^7]: https://x.com/FinnThePanther/status/2076378180840239389

content/fnn/fnn.md

@@ -0,0 +1,5 @@
+---
+publish: true
+---
+
+idk. someone's gotta write this shit down, eh?

content/hopefully helpful/Dragon Con map.md

@@ -9,7 +9,7 @@ description: compiled by the generous users of r/dragoncon (particularly u/ghost
 ---
 ![[dragon con map.png]]
 
-### Good to know:
+# Good to know:
 - MARTA runs from the airport to the hotel district, coming up through Peachtree Center Mall.
 - the CVS in Peachtree Center Mall will likely be open later during Dragon Con due to the increased foot traffic
 - "Coke Fish Rights Park" is:

content/index.md

@@ -4,6 +4,7 @@ title: hi
 description: a digital garden, but it might be full of weeds
 created: 2026-07-07T22:59:17.843-04:00
 modified: 2026-07-07T23:02:06.833-04:00
+sticker: ""
 ---
 > [!tip]- oh look
 > the [[Dragon Con map]]
@@ -16,5 +17,7 @@ there exists, somewhere on this planet of ours, a group of individuals i'd call
 
 all i know is that i'd like to meet them some day. i hope i do. i know i've already met some.
 
-[[tv]]
+[[tv]] shows i'm keeping up with
+
+or maybe you'd like to talk about [[Dune]]
 

content/movies/Dune/Butlerian Jihad.md

@@ -0,0 +1,15 @@
+---
+publish:
+tags:
+  - dune/lore
+---
+
+> Thou shalt not make a machine in the likeness of a human mind.
+> *Orange Catholic Bible*
+
+Ask Gurney Halleck about what the OCB says about thinking machines. Remember, he's supposed to be a "warrior-poet" type character - equally skilled in combat and literature - with one of his favorite tomes being the *Orange Catholic Bible*, naturally. Of all the characters we interact with, he's the one who can quote entire passages verbatim. 
+
+It was the Butlerians who led the charge in the ancient war against the thinking machines. Remember: Paul's story begins in the year **10,191 A.G.** - that is, nearly 10,200 years *after* the formation of the Spacing Guild. Humanity's ability to exist in the vastness of space *relies* on the Spacing Guild's existence. 
+
+> The eye that looks ahead to the safe course is closed forever.
+

content/movies/Dune/Dune.md

@@ -36,3 +36,10 @@ the third, Denis Villeneuve's *Dune*, *Dune: Part Two*, and upcoming *Dune: Part
 Villeneuve was honestly smart to cut the first movie in half so he could add more content, but the scenes he chooses to focus on are markedly different from the first two adaptations. both Lynch's and Sci-Fi's adaptations spend at least *some* time in the early story going over Shaddam IV's very obvious plan to send the Atreides to Arrakis with the intent of getting rid of them. Villeneuve chooses not to show the Emperor *at all* until the second film. we make a lot more out of the ceremony handing title and fief over to Leto than either of the other adaptations - and we name drop Kynes as Judge of the Change but don't explain what that means. Kynes also shuffles off this mortal coil more or less as depicted in the novel, which i definitely give props for. it seems at least somewhat *implied* that Chani is Liet's daughter, and that Liet was extremely high up in Fremen society, but not much is made of this, at least in the first two installments.
 
 Villeneuve does manage to get a lot more out of Duncan Idaho and Gurney Halleck than other adaptations, but i think that was tied pretty heavily to both actors' star power. we don't get as much time with Dr. Yueh to establish that he's supposedly incapable of rendering his noble lords harm...so it's more of a betrayal and more shocking when he turns out to be the saboteur later on. we also get maybe one or two scenes with our Mentat, which is honestly a damn shame, both given the missed opportunity *and* the lost dramatic tension between him and Jessica. (he initially suspects her to be the Harkonnen spy, without knowing she is herself Harkonnen in ancestry)
+
+# thoughts
+Paul is many things, most of which are thrust upon him by his parents. Chalumet's portrayal really does highlight the sheer weight of responsibility that *both* of his parents are laying on him - his father's desperate need for Paul to take responsibility for leading the house, and his mother's insistence he *master* the Bene Gesserit practices she thinks he'll need to stay alive. Both things do wind up benefitting him in the end, be it his seemingly innate ability to inspire others to his cause...or his Spice-enhanced prescience and reflexes making him extremely formidable in combat.
+
+But it truly is that looming vision of roaming hoards of warriors chanting his name and burning the stars that keeps him up at night. It makes Villeneuve's Paul reluctant to take *any* responsibility in the sietch with his new Fremen tribe out of fear he'll wind up inspiring zealots. Stilgar proves this to be an inevitability, though I'll also point out that Villeneuve's adaptation is the only one I know of that actually portrays him as the religious fundamentalist zealot he really is. It's mainly through Chani's first few interactions with Paul that we come to understand just how radical Stilgar and his close followers can be. 
+
+I've also got quite a few thoughts about Villeneuve & Zendaya's Chani. I honestly think it's a breath of fresh air to have a Chani who actually *isn't* okay with the guy she fell in love with going all tyrannical and seizing power just like Arrakis' past oppressors. Paul's promises of "transforming the face of Arrakis" – by realizing the *actual* Fremen agenda of terraforming the planet and making it rain – *never come to fruition* because doing so would rob him of two things at once: spice and leverage. While Arrakis produces spice, all the Great Houses and Organizations of the Imperium are beholden to him and his whims. Without that stranglehold on such a crucial resource, Paul would only have the zealots to fight for him, and the rest of the Imperium wouldn't hesitate to wipe him out. 

quartz.config.yaml

@@ -1,6 +1,6 @@
 # yaml-language-server: $schema=./quartz/plugins/quartz-plugins.schema.json
 configuration:
-  pageTitle: "pax.ad"
+  pageTitle: pax.ad
   pageTitleSuffix: ""
   enableSPA: true
   enablePopovers: true
@@ -16,8 +16,9 @@ configuration:
     fontOrigin: googleFonts
     cdnCaching: true
     typography:
-      header: Corben
+      title: Corben
-      body: Corben
+      header: Sono
+      body: Sono
       code: IBM Plex Mono
     colors:
       lightMode:
@@ -111,10 +112,10 @@ plugins:
   - source: github:quartz-community/fonts
     enabled: true
     options:
-      useThemeFonts: false
       fontOrigin: googleFonts
+      useThemeFonts: false
       header: Sono
-      title: Sono
+      title: Corben
       interface: Sono
       code: IBM Plex Mono
   - source: github:quartz-community/remove-draft