DML repositories and how they connect

DML repositories and how they connect An architecture diagram generated by Archify.Microsoft Teams · service-requests channel · Architecture component Microsoft Teamsservice-requests channelservice repos · one per request · Architecture component service reposone per requestdml-content-publisher · AI authoring skill · Architecture component dml-content-publisherAI authoring skillGitHub Pages · published site · Architecture component GitHub Pagespublished siteDML service request · Microsoft Form · Architecture component DML service requestMicrosoft FormPower Automate · intake flows · Architecture component Power Automateintake flowsservice-desk · one issue per request · Architecture component service-deskone issue per requestiat-dml.github.io · the website · Architecture component iat-dml.github.iothe websiteiat-dml@zalf.de · shared mailbox · Architecture component iat-dml@zalf.deshared mailboxdml-brand-yml · colours, fonts, logos · Architecture component dml-brand-ymlcolours, fonts, logostemplates · branded document templates · Architecture component templatesbranded document templatesknowledge-management · source of truth for documents · Architecture component knowledge-managementsource of truth for documentsZenodo · citable DOI · Architecture component Zenodocitable DOIGitHub issue form · issue template · Architecture component GitHub issue formissue templatetraining · educational materials · Architecture component trainingeducational materialsproject-management · internal planning, private · Architecture component project-managementinternal planning, privateembeds the formsubmissionnew messagenotifiescreates issueopens issuegets its own reporequest contextwork to publishdrafts pages, via PRpublish.yml, babelquartobrandingpull-docs, nightlyzenodo-publish.ymlbrandingagendas, minutes, reportsslides, handoutsplans our own workLegendFrontendBackendDatabaseCloudMessage busExternal

Intake

  • • Form, mailbox and GitHub issue form all become one service-desk issue

Doing the work

  • • Each request gets its own repo; the publisher drafts pages as pull requests

Documents

  • • Branding feeds templates; knowledge-management is the source of truth

Publication

  • • Nightly pull to the website, GitHub Pages build, Zenodo DOI