7 files changed, 318 insertions, 17 deletions
diff --git a/2026/talks/anju.md b/2026/talks/anju.md
new file mode 100644
index 00000000..033837a5
--- /dev/null
+++ b/2026/talks/anju.md
@@ -0,0 +1,26 @@
+[[!meta title="Revisiting Emacs Mouse Interactions with Anju"]]
+[[!meta copyright="Copyright &copy; 2026 Charles Y. Choi"]]
+[[!inline pages="internal(2026/info/anju-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Revisiting Emacs Mouse Interactions with Anju
+Charles Y. Choi - IRC: kickingvegas, Website: <http://yummymelon.com/devnull/> Mastodon: @kickingvegas@sfba.social, <mailto:kickingvegas@gmail.com>
+
+[[!inline pages="internal(2026/info/anju-before)" raw="yes"]]
+
+Anju (안주) is a project to align mouse interactions in Emacs with contemporary expectations in 2026. Effort towards this alignment is made in the areas of context-sensitive menus, de-emphasis of middle mouse button usage, support for direct manipulation, and re-organization of the main menu bar. The features offered by Anju are opinionated, but avoids unconventional behavior. Anju aspires to bring a calmer mouse experience to Emacs.
+
+This talk will present an overview of Anju (<https://kickingvegas.github.io/anju/>), describing its design decisions and implementation.
+
+About the speaker: Charles Choi is a Computer Engineer and Emacs enthusiast.
+
+
+
+[[!inline pages="internal(2026/info/anju-after)" raw="yes"]]
+
+[[!inline pages="internal(2026/info/anju-nav)" raw="yes"]]
+
+
diff --git a/2026/talks/bone.md b/2026/talks/bone.md
new file mode 100644
index 00000000..06e67545
--- /dev/null
+++ b/2026/talks/bone.md
@@ -0,0 +1,74 @@
+[[!meta title="BONE and gnaw.el: tracking what matters"]]
+[[!meta copyright="Copyright &copy; 2026 Bastien Guerry"]]
+[[!inline pages="internal(2026/info/bone-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# BONE and gnaw.el: tracking what matters
+Bastien Guerry (he) - IRC: bzg, <https://bzg.fr>, <mailto:bzg@bzg.fr>
+
+[[!inline pages="internal(2026/info/bone-before)" raw="yes"]]
+
+Most free software projects use three communication channels: one for
+general feedback, one for bug reports, and one for contributions.
+Projects that use patches instead of pull/merge requests (e.g. Emacs)
+can reduce this to two channels: a discussion list and a bug tracker.
+Some opinionated projects (e.g. Org mode) use only one channel: a
+mailing list for general discussions, bug reports and patches. This
+makes it easy for everyone to track everything. However, this requires
+a tool to help filter all the input. The Org mode tracker uses BONE
+for this filtering, and Org mode contributors can use gnaw.el as a
+BONE client.
+
+BONE (Backlog Of Notable Emails) is a bug tracker written in Clojure
+that watches a project's mailing list. An email whose subject starts
+with [BUG], [PATCH] or [FR] becomes a report. Replies update it with a
+small, fixed vocabulary: "Confirmed.", "Acked.", "Owned.", "Closed.",
+plus the usual review trailers like Reviewed-by:. Nobody creates an
+account, nobody fills a form, nobody leaves their mail client. The
+mailbox stays the single source of truth: the tracker database can be
+rebuilt from the archive at any time. BONE then exports the reports as
+static HTML, RSS, Org and, most importantly, plain reports.json files
+that anyone can fetch and reuse.
+
+gnaw.el is the Emacs client for BONE. M-x gnaw opens a report browser
+listing the bugs, patches and feature requests of the sources you
+follow, across projects. From that buffer you can search reports, read
+the underlying emails in Gnus, notmuch or mu4e, view and apply patches
+directly into a local git repository, open attachments, and organize
+your own work with local sticky and dismiss marks.
+
+The talk will:
+
+-   show BONE in action on a real mailing list, from the tagged email to
+    the exported reports;
+-   demo gnaw.el: browsing, searching, reading, applying a patch, all
+    from Emacs;
+-   discuss the pros and cons of using this tool for Org mode.
+
+The audience is anyone who maintains or contributes to a project
+through a mailing list, anyone who is tired of forge accounts, and
+anyone curious about what a tracker looks like when it is derived from
+the conversation instead of replacing it.
+
+Links:
+
+-   [BONE - Reports - Org mode ML](https://tracker.orgmode.org)
+-   BONE: <https://codeberg.org/bzg/bone>
+-   gnaw.el: <https://codeberg.org/bzg/gnaw.el>
+-   The essay behind the idea:
+    <https://bzg.fr/en/notes/the-issue-with-issue-trackers/>
+
+About the speaker:
+
+Bastien Guerry has been maintaining Org mode from 2011 until 2025.
+
+
+
+[[!inline pages="internal(2026/info/bone-after)" raw="yes"]]
+
+[[!inline pages="internal(2026/info/bone-nav)" raw="yes"]]
+
+
diff --git a/2026/talks/hyperbole.md b/2026/talks/hyperbole.md
new file mode 100644
index 00000000..c899dfd1
--- /dev/null
+++ b/2026/talks/hyperbole.md
@@ -0,0 +1,80 @@
+[[!meta title="Hyperbole, My Dear Watson"]]
+[[!meta copyright="Copyright &copy; 2026 Charlie Holland"]]
+[[!inline pages="internal(2026/info/hyperbole-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Hyperbole, My Dear Watson
+Charlie Holland (he/him/his) - <https://chiply.dev>, <https://github.com/chiply>, <https://reddit.com/u/misterchiply>, <mailto:mister.chiply@gmail.com>
+
+[[!inline pages="internal(2026/info/hyperbole-before)" raw="yes"]]
+
+In the talk, I want to build the same set of notes twice, once in plain Org
+and once in Org + GNU Hyperbole, and this talk will demonstrate the utility
+of adding Hyperbole to the typical org workflow. The subject matter (the
+thing I'm taking notes on in the demo) is the Sherlock Holmes canon, which
+I selected deliberately as it contains sixty public-domain stories, on
+Project Gutenberg as plain text.  This avoids copyright issues and also
+allows users to follow along with a note taking workflow on a complex
+resource for free.
+
+The thesis is that Org simply 'reads' text, while Hyperbole's added value
+is that it 'recognizes' text. In Org, a link is markup you have to
+explicitly type into a document, whereas in Hyperbole it is a pattern
+already in the text you read or type, and becomes live in any buffer (org,
+markdown, eww, epud, etc&hellip;).
+
+My contrived note taking on the Sherlock canon will make the benefits of
+Hyperbole clear.
+
+-   In my notes, concepts and character names will be noted as CamelCase
+
+WikiWords.  Once created, these will show up highlighted in any EPUB file,
+EWW page, etc&hellip;.
+
+-   HyWiki links these for free in my personal notes, but in Doyle's text
+
+they are not written in CamelCase, so a simple alias extension to
+Hyperbole's HyWiki makes it as so that "Sherlock Holmes" will show up as a
+match for the "SherlockHolmes" WikiWord in any buffer, which will serve as
+an extensibility demo that resolves a common pain point with HyWiki.
+
+-   Other elements of the canon are WikiWords already in-place.  Sherlockians
+
+have cited the stories by four-letter code since 1947, so I will define a
+button with `defil` that makes every "(SCAN)", for a example, a live
+citation.
+
+-   The Gutenberg text must stay untouched, so annotations I create will live
+
+in an explicit-button file beside it.
+
+-   Holmes's docketed index of "men and things" will be an additional demo
+
+for HyRolo.
+
+Act I shows four frictions with Org alone, and Act II removes them one
+Hyperbole mechanism at a time. I close with what Org does better, which
+alternatives to Hyperbole address each friction (org-roam, org-remark,
+denote, org-transclusion), and why Hyperbole's uniform mechanism over all
+text in every buffer is still a differentiator. The idea is that I'm
+promoting Org plus Hyperbole, not Org versus Hyperbole.
+
+About the speaker:
+
+Charlie Holland writes
+about Emacs and knowledge management at [chiply.dev](https://chiply.dev), where this talk caps a
+four-part series on GNU Hyperbole. Charlie builds the same notes on the
+Sherlock Holmes canon twice, in Org and then in Org plus Hyperbole, to show
+the value that a mature hypertext system can bring to your note taking
+workflow.
+
+
+
+[[!inline pages="internal(2026/info/hyperbole-after)" raw="yes"]]
+
+[[!inline pages="internal(2026/info/hyperbole-nav)" raw="yes"]]
+
+
diff --git a/2026/talks/koutliner.md b/2026/talks/koutliner.md
new file mode 100644
index 00000000..d6f9c6bf
--- /dev/null
+++ b/2026/talks/koutliner.md
@@ -0,0 +1,45 @@
+[[!meta title="Hyperbole Koutliner: The Best Autonumbered, Hyperlinking Outliner for Emacs"]]
+[[!meta copyright="Copyright &copy; 2026 Bob Weiner"]]
+[[!inline pages="internal(2026/info/koutliner-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Hyperbole Koutliner: The Best Autonumbered, Hyperlinking Outliner for Emacs
+Bob Weiner - Pronunciation: Wine-urr, <https://gnu.org/s/hyperbole/man/hyperbole.html#Koutliner>, <mailto:rsw@gnu.org>
+
+[[!inline pages="internal(2026/info/koutliner-before)" raw="yes"]]
+
+The Koutliner (pronounced Kay-outliner) is a powerful, easy-to-use
+multi-level autonumbered outliner for producing structured documents
+in Emacs.
+
+Learn how to use the Koutliner for critical outlines that must have
+unique, legal-style autonumbering for each section, simple
+cross-references, automatic permanent hyperlink anchors and outline
+view control via single alpha characters.
+
+Learn when to use the Koutliner and when to use Org mode for outlining.
+
+The Koutliner is just one part of the extensive Hyperbole package
+designed to handle many of your everyday information management and
+hyperlinking needs.  See: <https://gnu.org/s/hyperbole/man/hyperbole.html>.
+
+About the speaker:
+
+Bob Weiner is a software developer who designs powerful, flexible
+easy-to-use systems that work out of the box with few dependencies.
+
+He developed the the Koutliner as part of the Hyperbole package prior to
+the advent of Org mode, when he needed an Emacs-based outliner with
+legal-styled numbering.  Let's see how it differs from Org mode and
+how it can help you in rapidly structuring thoughts or notes.
+
+
+
+[[!inline pages="internal(2026/info/koutliner-after)" raw="yes"]]
+
+[[!inline pages="internal(2026/info/koutliner-nav)" raw="yes"]]
+
+
diff --git a/2026/talks/os.md b/2026/talks/os.md
new file mode 100644
index 00000000..3ded2bac
--- /dev/null
+++ b/2026/talks/os.md
@@ -0,0 +1,45 @@
+[[!meta title="Emacs everywhere: A fun romp through esoteric operating systems"]]
+[[!meta copyright="Copyright &copy; 2026 Aaron Grothe"]]
+[[!inline pages="internal(2026/info/os-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Emacs everywhere: A fun romp through esoteric operating systems
+Aaron Grothe (he/him) - Pronunciation: Grow-Thee, <https://www.grothe.us> LinkedIn: <https://www.linkedin.com/in/aaron-grothe/>, <mailto:ajgrothe@yahoo.com>
+
+[[!inline pages="internal(2026/info/os-before)" raw="yes"]]
+
+One of the greatest running jokes and truest philosophies in the tech world is that Emacs isn’t just a text editor; it’s an operating system that happens to lack a good text editor. But a corollary to this philosophy is that the real Emacs can run on virtually any operating system ever conceived.Or can it?
+This talk is a lighthearted, deeply technical, and fun exploration of running full, uncompromised GNU Emacs on some of the most esoteric, vintage, and fringe operating systems in existence. If you have ever wondered whether a legendary text editor from the 1970s can comfortably coexist with modern hobbyist kernels or forgotten platforms, this is the session for you.
+
+The Journey Across the Fringe
+
+We will kick off our adventure by looking past the usual Linux, macOS, and Windows environments to explore how Emacs behaves in the wild. Our tour will take us across a fascinating spectrum of platforms, including:
+
+-   Haiku OS: The spiritual successor to BeOS, known for its incredible snappiness and unique interface design.
+-   ReactOS: The open-source effort to build an operating system binary-compatible with Windows NT.
+-   AROS (Amiga Research Operating System): Keeping the legendary Amiga spirit alive on modern hardware.
+-   GNU Hurd: The long-standing microkernel-based alternative to the Linux kernel, staying true to the core GNU philosophy.
+-   Termux on Android: Bridging the gap between pocket mobile computing and serious Unix environments.
+
+By examining these systems, the goal isn't just to marvel at technical trivia, but to discover the genuine boundaries of where Emacs succeeds, where it struggles, and what these edge cases reveal about portability and modern software design.The Redox OS Frontier and the WASM StopgapNo exploration of modern alternative operating systems would be complete without looking at Redox OS, an innovative, microkernel-based operating system written entirely in Rust. Currently, Redox OS cannot run a native version of Emacs out of the box.
+
+However, necessity is the mother of invention. To ensure nobody leaves without their text editor fix, we will demonstrate running Emacs compiled to WebAssembly (WASM) directly inside a browser on Redox OS. While we anticipate native Redox OS support arriving in the next 18 to 24 months, WASM serves as a brilliant, functional stopgap in the meantime.
+
+Conclusion
+
+Emacs in the 2020s is entirely a choice, just as choosing to daily-drive or tinker with an esoteric operating system is a choice. Together, they form an unexpectedly delightful combination for hackers, hobbyists, and digital archaeologists alike.Attendees will leave this talk with a fresh appreciation for software portability, a smile on their faces, and perhaps a new spark of inspiration to find a weird operating system for their own weekend tinkering.
+
+About the speaker:
+
+Welcome, brave souls, to an eccentric journey into digital omnipresence! While others debate modern IDEs, true enlightenment lies in the extensible glory of Emacs. But why stop at mainstream systems? Today, we boldly venture where few dare to tread: running Emacs on obscure, esoteric operating systems Haiku, ReactOS and others.  Prepare for a delightfully chaotic exploration of stubborn survival and our ultimate, unstoppable blueprint for total world domination—one bizarre kernel at a time. Resistance is futile!  Aaron Grothe has been a developer for years and has been an Emacs users for a very long time.  It was his first full screen editor and it will probably be his last :-)
+
+
+
+[[!inline pages="internal(2026/info/os-after)" raw="yes"]]
+
+[[!inline pages="internal(2026/info/os-nav)" raw="yes"]]
+
+
diff --git a/2026/talks/portable.md b/2026/talks/portable.md
index 762b17be..7f502be2 100644
--- a/2026/talks/portable.md
+++ b/2026/talks/portable.md
@@ -11,27 +11,19 @@ Mohammed Ismail Ansari - <https://myterminal.me>, <mailto:mail@myterminal.me>
 
 [[!inline pages="internal(2026/info/portable-before)" raw="yes"]]
 
-In the talk, I plan to cover my entry
-into the world of Emacs, a high-level series of events that shaped my
-experience and learning, and a few takeaways from someone coming from an
-entire different toolset and mentality, eventually having a moment of
-enlightenment to never go back again. The talk will revolve around how
-it has been my companion across multiple operating platforms and will
-remain to be one of the core elements of my computing toolset no matter
-the environment or platform. I'll talk about a few highs and lows of my
-attempts of inviting friends to Emacs, a few mentions of my
-contributions to the community and hopefully some tips for inspiration
-to newcomers and fellow Emacs-ers alike. Along with these, I'll also
-walk through how and why I created super-emacs and why I think it can be
-a reasonably easy starting point for someone getting into Emacs as their
-daily driver.
+In the talk, I'll cover my brief experience using Emacs across three
+major operating systems, how it influenced the other tools within my
+toolset, my effort to share my configuration with the rest of us, and
+eventually super-emacs: my attempt at a minimal but feature-full
+starter pack for Emacs that I've been maintaining for over a decade
+now.
 
 About the speaker: I, Mohammed Ismail Ansari (aka myTerminal), come
 from an academic background in Electronics Engineering, and have been
 working professionally as a software engineer since seventeen years.
-I love to create and experimenting with all kinds of machines, not
-just computers, enjoying the exploration and tinkering process.
-In the recent years I've also discovered my interest in personal
+I love to create and experiment with all kinds of machines, not just
+computers, enjoying the exploration and tinkering process. In the
+recent years I've also discovered my interest in personal
 productivity, and pairing them with some of the core elements within
 my toolset, including Linux, Emacs, and many other open-source
 software everything fits in place as if it was supposed to be.
diff --git a/2026/talks/rau.md b/2026/talks/rau.md
new file mode 100644
index 00000000..554d1bcf
--- /dev/null
+++ b/2026/talks/rau.md
@@ -0,0 +1,39 @@
+[[!meta title="Emacs as a Window Manager and concurrency"]]
+[[!meta copyright="Copyright &copy; 2026 Thomas Koch"]]
+[[!inline pages="internal(2026/info/rau-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Emacs as a Window Manager and concurrency
+Thomas Koch - <https://blog.koch.ro>, <mailto:thomas@koch.ro>
+
+[[!inline pages="internal(2026/info/rau-before)" raw="yes"]]
+
+Rau is one of three different Wayland Window Manager projects active right now
+and the only one written only in Elisp (at the moment).
+
+I'll present the current state of Rau, compare it with the other two projects
+(Reka, EWM) and discuss some difficulties encountered with a focus on
+concurrency and Emacs.
+
+Rau is already fully functional for daily use. The single threaded nature of
+Emacs however is a major issue that will require to move the major part of Rau
+from Elisp into an Emacs module and thus into another language.
+
+<https://github.com/thkoch2001/rau>
+
+About the speaker:
+
+Thomas Koch has a preference for logic, correctness and elegance.
+Therefore, he likes Haskell, Emacs, Nix, Postgres and tries to help the success of <https://github.com/axiosoph/axios>.
+He deeply values open, respectful discussions with people of diverse perspectives.
+
+
+
+[[!inline pages="internal(2026/info/rau-after)" raw="yes"]]
+
+[[!inline pages="internal(2026/info/rau-nav)" raw="yes"]]
+
+