events, … (…can be a lot for new users Used by all sorts / sizes of communities & companies Lots of settings and possibilities for customization Democratize online community and teamwork Focus on high standard of civilized discourse Free & open source Own your data, customize / extend the software, self host it https://www.discourse.org/about )
by big tech… Opinionated & batteries included Router, templates, components (Glimmer), … Focus on long-term stability Discourse never rewrote their frontend since 2013…
only in day to day operation Digital independence: legal requirement & political stance Stricter data protection rules than private companies Limited in software choices No vendor-lock to shiny US oligarchy-tech, "stuck" with self hosted OSS Limited financial resources Spend sustainably and locally Sluggish operational structure Took ages from kick-off to project work
Already using it and evaluated as promising candidate Client in contact with core maintainers Checked general feasibility of project Want to contribute back to community Project as initiative for more similar work in the public sector
Berlin libraries Curated by libraries and by local communities Digital space for participants & communities Library already offers physical space Save space for learning and dialogue Expand library space into digital space Tweak Discourse to this…
build around for development meta.discourse Epicentre of development & main source of information Plugins, themes, theme components Mechanisms for customization / extension … or forking as the last resort…
as a base Development of customizations all within local Discourse clone Scripts / generators for scaffolding extensions Project structure, CI for integration testing against different versions of Discourse Good setup for testing, linting and debugging Works equally for Discourse core and for extensions Downside: lots of movement on main branch Effort to keep own code compatible with past and future Discourse versions
Ideation process way beyond the boundaries of Discourse Product vision first, platform limitations second Profound modification of core Discourse UX bitcrowd's task: spikes and research Find out if ideas are technically feasible and at which effort / price
Discourse plugins Client- & server-side logic, UI components, API extensions Theme mainly done by team at ZLB Use Discourse' provided extension points Page outlets for UI, extension points for business logic Override Discourse core logic Add own routes, pages & components
code in Discourse; opt for new routes/pages Split into multiple, self-contained, configurable plugins No need for the full package at all times Test Discourse core logic and own deviation from it Test system with and without plugin enabled UI changes and components theme-agnostic Use Discourse' JS components, minimal CSS with variables for customization Document own components in styleguide Like Storybook for Discourse components
made a difference Have coding agent to exploring the gigantic codebase Conversations about feasibility and strategy for changes Would have needed to pair with core maintainers otherwise Speed boost in planning enabled project in given time & budget Tight budget (public sector…) and tight deadline (re:publica…) did not need AI to write code…
klappradla
kaen
asari194617
sansan33
atsukish
tsho
keio_smilab
databricksjapan
honyanya
oikon48
go0517go
lycorptech_jp
konakalab
lara
cassininazir
inesmontani
aleyda
trishagee
mraible
rocio
techseoconnect
addyosmani
