The data at Inform 7 - #3 by trashHeap is very complete, so I’m gonna use it to model front matter, see what should be strings and what should be referenced elsewhere in the site. I plan to load up more front matter over time, and this will let me add more quests to add new sections that expand on the data we capture here. 
Name: Inform 7
title, will base URL/slug off this
Status: Inconsistent
We have a list: Dead/Healthy/Abandoned/Maintained/Security Patches Only
We’ll stick with just those, open to refinement (and text search/replace) later.
Release Schedule/Cycle: Inconsistent
We’ve discussed using VCS data to show updated info; we just updated allthe.codes so we can list commit info straight from our mirrors! Aside from that tidbit, though, I think this is best free form. In my experience, projects that talk about release schedules either have one specific model in mind, or change it often enough it is discussed.
Big aside: always looking for prior art, so if some other directory is using a “standard” or common set of attributes, please point it out!
License: The core compiler is (currently) proprietary and is planned to shift to Artistic 2.0 with planned Bison like code generation clause. The various OS specific IDEs are GPLv3.
I’m definitely collecting licenses! I’ve noted the various license lists, with their initialisms, and we’ll figure it out here. But I’m leaning towards the verbose. And each one will eventually generate a link to a data page of that license, and the license text will be published somewhere on interi.
Is license OSI/FSF/DFSG approved ? Not today.
This will be programmatically resolved from license data. Meaning I may forget it, but it will be an easy add later.
Runtime: Inform 7 executes as native code but outputs Glulxe or ZMachine VM.
…
@trashHeap, are runtimes… platforms? 
What is a generalized list of runtimes, with five examples?
Widgets: Output is text based. IDE is Gtk3 / Cocoa / Windows Forms.
Platforms: GNU/Linux (badly supported) , Windows , Mac OS X.
Not sure if it will be called “platforms”, but somemthing that will generate a different directory. What do other directories call these? OS?
Build System: Unknown
This is like GCC/make? (cribbing from SGDK)
Website: http://inform7.com
Hahaha, this one is gonna be weird. Not because of inform, but because of how I’m gonna handle this. Basically, any URLs that are shown are either non-linked strings (easy to copy and paste), or links to a profile page for said link, on interi. Because I’m going to exhibit URIs. And rate them on safety. It’s gonna be a whole thing!
I also intend to have a DNS section, with domain breakdowns in the path (ie a page will be at https://interi.org/dns/org/interi, https://interi.org/dns/xyz/talkgroup, etc.)
Not sure how that will interact, but I wouldn’t mind do entire domain manipulations; for instance, for each page in the .org domains, link to the EFF page about the .org sale, that kinda thing. Or link to a domain’s country page, so folks know the meaning behind their “cool” .ly or .io domains.
Repository: Somewhere near: ganelson (Graham Nelson) · GitHub
Not all pages will have repos, and for those that do we’ll have a “home” repo, but only link to a mirror if we are hosting it. If we identify other VCS hosts, we can mark them approved links as well.
Function: Compiler / Programming Language / Natural Language Processor
@trashHeap: free form, or we make a big ol’ list?
Online Required: No
DRM & Type of DRM: None
I wonder if these could be “features”, a “tag” taxonomy. They won’t apply to all warez, but when they do it is very important.
Last known price: Gratis
I’d love to do some kind of price comparison, but only because I think such data is available. But I’m not sure I care or find it useful; I don’t pay directly for code, I’m not sure how it all works. Open to suggestions for how this should be structured in data form (a number, a number and currency, a description [gratis, cheap, shareware, holy shit enterprise]).
Publisher: N/A
When filled out this should be a full group name, which will link to the groups directory.
Studio / Lead Dev: Graham Nelson
Might use nested front matter to do something like:
people:
leaddev:
groups:
publisher:
studio:
We aren’t “tagging” these pages, per se. But we are relating data that exists, and then linking to it where appropriate.
Package types available: Flatpak is the only option for most GNU/Linuxes currently.
Huh, I didn’t know inform7 was available via flatpak, and I sought out such info.
warez packaging will be fun to document! We will even list stuffit eventually!
Initial year it became available: 2006 for Inform 7 , 1993 for all prior versions of Inform. Inform 7 is a very different programming language though than from what came before.
Inform may also have a place in the languages exhibit. And some of this info will be applicable there. Language evolution between versions feels like a language specific thing, aside from “warez”.
Governance Model: Dictator for life.
We got a list of models?