What changed this week (September 7 to 11, 2026)

Here is what landed this week.

Community

• A community can offer more than one kind of membership. Access used to come in two words, everyone or members. A community now names its own levels and gates any item to the one it chooses.
• People can say they are coming to an event, and see who else is. An event could say when and where but nothing about who, which is most of what makes somebody decide to turn up.
• Members can put pictures in a discussion post or a reply, as many as they like.
• Every published item can carry a conversation. An article, video or resource shows "Discuss this" with a reply count.
• Pinned posts appear in the community rail. A post pinned because everybody should read it used to stay invisible outside the one group it lived in.

Publishing

• Authors can put pictures in a post or a page, and place each one: centred, floated left or right with the text wrapping around, or full width. Pictures go through the same checks as everything else uploaded, so they are resized and stripped of their location data on the way in.
• An organization chooses what it publishes. Every organization used to be handed every content type, so a woodworking club got a podcast archive and a jobs board whether it wanted them or not.
• The fields a content type declares now show up, on the web and in email. They had always been collected and validated, then displayed nowhere. Types can also describe more: a choice from a list, a picture, a file, a date and time, and repeating rows.
• Content can live inside other content. A recipe card belongs in the article that discusses it. A lesson belongs to its course.
• An author can pull another published item into a body, or the latest few of a type, instead of linking out and hoping the reader comes back. A video link on a line of its own becomes a player.
• Archives are a grid of cards with a category filter above them. Categories carry a colour and an icon, and a category can hold the skeleton its items start from.
• An author edits a published item from the item itself, rather than leaving it to find it again in a list.
• Every archive publishes RSS and Atom feeds, and the site publishes a sitemap so search engines can find what is there. A feed lists exactly what its archive lists, so a members-only item shows its title and never its body.

Bug fixes

• Video, embed and feed directives work on bodies written in the editor. They worked from seeds and scripts, which is how they passed review and then failed on the first article somebody wrote.
• A preview stays on the draft it is showing. Clicking the navigation used to carry you off it with no warning.
• Discussion cards show a post's text instead of its Markdown. A post that opened with a link used to display the link's syntax.

For operators

• An organizer can hand a locked-out member a one-time link to choose a new password. It works once, lasts a day, and is the way back in on an installation with no email configured.
• An installation says when it has fallen behind. Once a day it checks whether a newer version has been published and tells whoever administers the installation, who is the only person who can do anything about it.
• An installation can tell you which version and build it is running.
• Every email carries the look of the community it came from. Everything except the newsletter used to go out as plain text, with nothing to say who was writing.