Skip to content

ENH: Add first pass at a registries#1

Open
Kai-Striega wants to merge 1 commit intomainfrom
kai/add-first-pass-of-speaker-registry
Open

ENH: Add first pass at a registries#1
Kai-Striega wants to merge 1 commit intomainfrom
kai/add-first-pass-of-speaker-registry

Conversation

@Kai-Striega
Copy link

This PR includes the first pass at a speaker and talk registries. It manages each as a .toml file which contains the required data about the speaker or talk respectively. Further it includes checks that the .toml files are correctly formatted, which can also be run in CI.

@Kai-Striega Kai-Striega force-pushed the kai/add-first-pass-of-speaker-registry branch from 700dbcc to 0f80ba1 Compare January 19, 2026 07:54
This commit includes the first pass at a speaker and talk registries. It manages
each as a ``.toml`` file which contains the required data about the speaker or
talk respectively. Further it includes checks that the ``.toml`` files are
correctly formatted, which can also be run in CI.
@Kai-Striega Kai-Striega force-pushed the kai/add-first-pass-of-speaker-registry branch from 0f80ba1 to 392b454 Compare January 19, 2026 07:55
@@ -0,0 +1,5 @@
[KaiStriega]
name = "Kai Striega"
about = "Kai is a motivated, conscientious senior software developer and FOSS advocate with an educational background in mathematics. Whilst being very appreciate the beauty of Mathematics Kai prides himself on his ability to focus on pragmatic outcomes, prioritising his work effectively. This combined with his strong technical grounding have seen him succeed in his roles as a software developer and data engineer at BHP, and now as a senior software engineer at Cartesian Software. In addition to his professional work, Kai is active in the Free and Open Source community as a long-term maintainer of SciPy."
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is terrible English 😓 you can see I wrote it very late last night

@elena
Copy link
Member

elena commented Feb 5, 2026

Wondering if we should be formalising syntax or maybe even aligning the "front matter" to align with the way they use it in ssgs eg:

If we matched the syntax and semantics we could just cheaply plug in to one of these without a translation layer.

@elena
Copy link
Member

elena commented Feb 5, 2026

Like a perfectly normal person I started a comparison table:

Jekyll Zola Hugo
page.content title = "" aliases (string array)
page.title description = "" build (map)
page.excerpt date = cascade (map)
page.url updated = date (string)
page.date weight = 0 description (string)
page.id draft = false draft (bool)
page.categories render = false expiryDate (string)
page.collection slug = "" headless (bool)
page.tags path = "" isCJKLanguage (bool)
page.dir aliases = [] keywords (string array)
page.name authors = [] lastmod (string)
page.path in_search_index = true layout (string)
page.slug template = "page.html" linkTitle (string)
page.ext [taxonomies] markup (string)
page.next [extra] menus (string, string array, or map)
page.previous   outputs (string array)
    params (map)
    publishDate (string)
    resources (map array)
    sitemap (map)
    sites (map)
    slug (string)
    summary (string)
    title (string)
    translationKey (string)
    type (string)
    url (string)
    weight (int)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants