Task

These modules:

• Structure Sync
• Default Content

… appear to be useful.

Enable and configure Content Moderation module.

Not much of a point otherwise.

Preferably using core comment module. Plus Inline Entity References (and possibly entity prepopulate) for changing the parent action when a comment is posted.

Also edit link in table.

Something broadly similar to the 'Status', 'Priority', and 'Category', select lists in the Drupal issue tracking system (example).

Schema.org has the rather unsatisfactory actionStatus property, with a measly four ActionStatusType values to pick from. I can get around that by categorising each of our longer list of values as one of those four (or none, if necessary). That's actually a good general solution for extending the spec.

So actionStatus is a select list which applies to entities (terms) in that bundle (vocabulary).

Quite a bit done in the last few days:

commit d6f14f38160aa5cc62f8ff36a7255f9c2d18bb17 (HEAD -> main, origin/main, origin/HEAD)
Author: Katy Swain <katy@katyswain.me>
Date:   Wed Jun 10 11:25:46 2026 +1000

    Changes to action content type, fields, views, blocks, etc.

commit 5ed217768eb2a3b156a8a71455ab5edd052647cf
Author: Katy Swain <katy@katyswain.me>
Date:   Tue Jun 9 16:30:20 2026 +1000

    Installed cer and schemadotorg_cer. A lot of tearing my hair out over views.

commit b1b6be4bef56a77cb4419fbb2347218835eacb34
Author: Katy Swain <katy@katyswain.me>
Date:   Tue Jun 9 11:16:04 2026 +1000

    Installed inline_entity_form and used it in the user → person relationship.

commit 25c6f7a018592b8d2b0834f806b2a6c21bff9141
Author: Katy Swain <katy@katyswain.me>
Date:   Mon Jun 8 12:39:00 2026 +1000

    Installed/configured pathauto, subpathauto, redirect.

commit ee4e678ab81cb03ebea60b542e131042250c8f0a
Author: Katy Swain <katy@katyswain.me>
Date:   Mon Jun 8 11:59:53 2026 +1000

    Installed/enabled diff, revision_log_default. A whole bunch of permissions granted.

commit 36ef6ce14549ba291cca67d8a0535560d40454fb
Author: Katy Swain <katy@katyswain.me>
Date:   Mon Jun 8 10:11:56 2026 +1000

    A bunch of new fields, mostly references.

commit 22343054e170cc3fb6a20fb1c1a4e55e9c8e9228
Author: Katy Swain <katy@katyswain.me>
Date:   Sun Jun 7 15:47:26 2026 +1000

    Made a start on organisation, person, project, action content types.

commit 5a9f4ccff40bae4f1049e4a92ae248628c995dd7
Author: Katy Swain <katy@katyswain.me>
Date:   Tue Jun 2 13:27:49 2026 +1000

    Point upgrades to Drupal core and Book module.

These are all modules that Jacob depends on with his Schema.org Blueprints Demo modules. As that is supposed to showcase the sort of large scale information management site we're building, it's worth me looking through to avoid wheel-reinvention. Most are new to me, some I've heard of but not used, a few I used occasionally, and fewer I used almost always. Will probably save time to review them ASAP rather than struggle to remember what they were called when I realise they might be useful.

Key:

• ✓: Next to test.
• ✓✓: Tested
• ✓✓✓: Tested and committed.
• x : Dismissed.

Probably Useful

• Content Moderation (core): Not used it before, but I like. It's in. ✓✓✓
• Inline Entity Form: Absolutely essential for the user → person relationship. ✓✓✓
• Diff: Absolutely. ✓✓✓
• Entity Prepopulate: Almost certainly.
• Address: For organisations and people.✓
• Contextual Links (core): Use it on my own site, but worried it might be more a distraction than a convenience here.✓✓✓
• Media (core): Definitely, but I need to look into complementary modules. Best case scenario is using media for handling all file types (local or remote). ✓
• Media Library (core): Need something like it, at least. I believe there are some drop-in replacements that claim to have some advantage. ✓
• Path (core) and Pathauto: Definitely. Also Redirect and Sub-pathauto. ✓✓✓
• Automatic Entity Label: Almost certain to be useful somewhere.
• Corresponding Entity References: Probably desirable. For each possible use, I really have to think about whether this is better than embedding a view of back references in the rendered content. Something in me says this is a kludge at the db and business logic level that should be implemented in the UI. Mind you it makes for simpler/faster db queries.✓✓✓
• Field Group: Simplest/oldest/most tested solution. Can fiddle with fancier layout stuff at some point in the future.
• OpenAPI: A requirement of JSON:API, which we will probably eventually want to use.
• Entity Usage: Very likely.
• Revision Log Default: Brilliant idea. Why didn't I think of that? ✓✓✓
• Views Bulk Operations (VBO): I imagine will come in handy at some point.
• Views Data Export: Especially the JSON export.

Maybe Useful

• Settings Tray (core): Been around for a while, but I've never used it.
• Shortcut (core): Never used it.
• Admin Dialogs: Looks nice.
• File Delete: Probably pretty essential once a site gets to a certain size. There's also Media File Delete, but I prefer the way this one sounds.
• Moderated Content Bulk Publish: I really don't know if we have a need for a user role that can create but not publish.
• Simple OAuth (OAuth2) & OpenID Connect: Largely depends on whether we want a full CRUD API.
• CKEditor Anchor Link: Overkill? Probably not for academic writing, but is there a better solution for references/footnotes?
• CKEditor CodeMirror: Maybe. If it worked for rendered code elements, rather than just HTML source view in CKEditor I'd be sold.
• CKEditor 5 Paste Filter: Because users do what users do, I suppose.
• Autosave Form: Massively useful if it works smoothly as advertised. The lack of conflict resolution (specially for large text fields) is a significant limitation.
• Entity Print: Seems almost sure to be useful. If it works nicely, it would save having to manually generate PDFs of content authored on-site.
• Field Validation: Nice, but not urgent.
• Entity Reference Override: Cool. Can't think of a use for it yet.
• Entity Reference Revisions: I think I will need it, I just don't know where yet.
• Entity Reference Tree Widget: Maybe.
• Entity Embed: Seems to be the best solution to putting arbitrary rendered entities in text fields.
• Convert Bundles: I can think of possible uses for this.
• Entity Clone: Cute.
• Link Attributes Widget: Maybe for Indieweb style markup.
• Masquerade: Possibly, but only for testing, obvs.
• Redirect: If the need arises.
• Trash: Because users gonna use. Adds maintenance work, though.
• Type Tray: If we end up with a lot of different content types maybe.
• Chosen: Quite possibly.
• Better Exposed Filters: Worth trying out.
• Views Reference Field: Makes me anxious, though.

Hmm…

• History (core)
• Local Tasks More: Look at it as and when necessary.
• Duration Field: Can't think of a use for it just yet, but it's jolly impressive. Date/time stuff is hard.
• Time Field: More time/date stuff.
• Content Model & Site Documentation: Looks nice, but needs something more than the "ooh" factor to be compelling.
• CKEditor Accordion: I really don't think so.
• CKEditor(5) Emoji: Do I have to?
• Embedded Content: Maaaaybe. Embedding rendered entities would be useful, but surely there's another solution for this? Oh, look…
• Custom Field: Not sure what the use case is in this context, or why we would use it rather than either field groups or entity references.
• Markup: No-code solution to something I used to do in code.
• Mermaid Diagram Field: Really nice. Hardly essential, but worth investigating eventually.
• Office Hours: Maybe not that relevant.
• Smart Date: Maybe if core's date widgets are lacking in some crucial way.
• Geolocation Field: Impressive, but probably not relevant.
• DropzoneJS: I don't think so.
• Entity Browser Enhance(d|r): Nope. Probably.
• Focal Point: Probably not.
• Existing Values Autocomplete Widget: Nice if needed.
• Menu Select: Unlikely.
• Moderation Dashboard: Probably not, but something custom in the same vein will be required.
• Moderation Sidebar: Seems a bit unnecessary to me.
• Scheduler: Meh.
• Ultimate Cron: If the site gets big maybe.
• Login Destination: Unlikely.

What Was He Thinking?

• Block field: This seems like asking for trouble.