Skip to content
This repository was archived by the owner on Nov 27, 2025. It is now read-only.

Commit 67d707b

Browse files
Create 0003-extract-plugins.md
1 parent d9a4a0c commit 67d707b

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# 1. Externalize OpenSCD core plugins
2+
3+
Date: 2024-11
4+
5+
## Status
6+
7+
Open
8+
9+
## Context
10+
11+
For a better expandability we would like to extract all plugins in a new plugins repository.
12+
13+
## Decision
14+
15+
Participants:
16+
- ... link to github user
17+
18+
Following the architectural decision in [OpenSCD Theming](./../0001-ADR-Theming.md) we would like to extract all OpenSCD Core plugins to an external repository.
19+
Doing so we are going to streamline the OpenSCD Core and provide a clean interface and structure for plugins.
20+
Further extracting the plugins we would introduce a shared UI-Component module which provides reusable UI-Components based on Svelte.
21+
22+
Plugins would be in the repository [OpenSCD official Plugins](https://github.com/openscd/oscd-official-plugins) and the release strategy is defined [here](./0004-openscd-release-and-deploy-strategy.md).
23+
24+
## Consequences
25+
26+
- Clean Code in OpenSCD Core
27+
- Clear architectural structure of plugins
28+
- Building OpenSCD is more then building a simple repository
29+
- Clear path must be defined how to extend OpenSCD with custom plugins (full software cycle till deployment)
30+
- Release process for OpenSCD Core and OpenSCD official plugins

0 commit comments

Comments
 (0)