Compare commits

...
4 Commits
7 changed files with 26 additions and 16 deletions

No files matched your search

+8
View File
@@ -1,5 +1,13 @@
# Changelog # Changelog
## 0.11.3 — 2026-11-09
- README: a link to the guides and walkthroughs on Medium.
## 0.11.2 — 2026-11-08
- The ArchiMate examples' layered views put the labels of the arrows between layers in the gap between the bands, no longer on the band titles.
## 0.11.1 — 2026-11-08 ## 0.11.1 — 2026-11-08
- **The arc42 examples cover all twelve sections.** Each overview carries cards for 1.1 Requirements, 1.2 Quality goals, 1.3 Stakeholders, 2 Constraints, 4 Solution strategy, 11 Risks and technical debt and 12 Glossary; the technical context lists the domain interfaces (3); every building block has a black-box description, responsibility and interfaces (5); the deployment view places the building blocks on their nodes with a mapping (7); level 1 carries the crosscutting concepts (8); a new `1000-quality` folder draws the quality tree with its scenarios (10). Each model's description says where each section lives. - **The arc42 examples cover all twelve sections.** Each overview carries cards for 1.1 Requirements, 1.2 Quality goals, 1.3 Stakeholders, 2 Constraints, 4 Solution strategy, 11 Risks and technical debt and 12 Glossary; the technical context lists the domain interfaces (3); every building block has a black-box description, responsibility and interfaces (5); the deployment view places the building blocks on their nodes with a mapping (7); level 1 carries the crosscutting concepts (8); a new `1000-quality` folder draws the quality tree with its scenarios (10). Each model's description says where each section lives.
+2
View File
@@ -8,6 +8,8 @@ Create and view [Archify](https://github.com/tt-a1i/archify) diagrams inside VS
This is an unofficial extension. It bundles the Archify renderer (MIT, © tt-a1i) and runs it on VS Code's own Node runtime, so nothing else needs to be installed. This is an unofficial extension. It bundles the Archify renderer (MIT, © tt-a1i) and runs it on VS Code's own Node runtime, so nothing else needs to be installed.
Guides and walkthroughs, one per feature (models, decisions, graph, Source view, 3D, Sync, the arc42 and ArchiMate examples): [articles on Medium](https://medium.com/@root.at.skic).
## Supported files ## Supported files
| File | Format | What the extension does | | File | Format | What the extension does |
+2 -2
View File
@@ -1,12 +1,12 @@
{ {
"name": "archify-vscode-ext", "name": "archify-vscode-ext",
"version": "0.11.1", "version": "0.11.3",
"lockfileVersion": 3, "lockfileVersion": 3,
"requires": true, "requires": true,
"packages": { "packages": {
"": { "": {
"name": "archify-vscode-ext", "name": "archify-vscode-ext",
"version": "0.11.1", "version": "0.11.3",
"license": "MIT", "license": "MIT",
"dependencies": { "dependencies": {
"@codemirror/autocomplete": "^6.20.4", "@codemirror/autocomplete": "^6.20.4",
+1 -1
View File
@@ -2,7 +2,7 @@
"name": "archify-vscode-ext", "name": "archify-vscode-ext",
"displayName": "Archify Diagram Viewer", "displayName": "Archify Diagram Viewer",
"description": "Archify diagrams in VS Code. Write diagrams as .archify files in YAML: they open as the interactive diagram, with live updates, validation, templates and completion. Also previews Archify's own JSON files (*.architecture.json, …) and opens rendered Archify HTML.", "description": "Archify diagrams in VS Code. Write diagrams as .archify files in YAML: they open as the interactive diagram, with live updates, validation, templates and completion. Also previews Archify's own JSON files (*.architecture.json, …) and opens rendered Archify HTML.",
"version": "0.11.1", "version": "0.11.3",
"publisher": "root-at-skic", "publisher": "root-at-skic",
"license": "MIT", "license": "MIT",
"sponsor": { "sponsor": {
@@ -51,9 +51,9 @@ boundaries:
connections: connections:
- { from: onboarding-svc, to: new-hire, label: serves, variant: emphasis } - { from: onboarding-svc, to: new-hire, label: serves, variant: emphasis }
- { from: onboard, to: onboarding-svc, label: realizes } - { from: onboard, to: onboarding-svc, label: realizes }
- { from: portal, to: new-hire, label: serves } - { from: portal, to: new-hire, label: serves, labelAt: [125, 197] }
- { from: provisioning-svc, to: onboard, label: serves } - { from: provisioning-svc, to: onboard, label: serves, labelAt: [585, 197] }
- { from: iam, to: provisioning-svc, label: realizes } - { from: iam, to: provisioning-svc, label: realizes }
- { from: office-net, to: portal, label: serves } - { from: office-net, to: portal, label: serves, labelAt: [125, 397] }
- { from: sso, to: iam, label: serves } - { from: sso, to: iam, label: serves, labelAt: [355, 397] }
- { from: directory, to: sso, label: realizes } - { from: directory, to: sso, label: realizes }
@@ -51,9 +51,9 @@ boundaries:
connections: connections:
- { from: claim-registration, to: insurant, label: serves, variant: emphasis } - { from: claim-registration, to: insurant, label: serves, variant: emphasis }
- { from: handle-claim, to: claim-registration, label: realizes } - { from: handle-claim, to: claim-registration, label: realizes }
- { from: portal, to: insurant, label: serves } - { from: portal, to: insurant, label: serves, labelAt: [125, 197] }
- { from: claims-admin, to: handle-claim, label: serves } - { from: claims-admin, to: handle-claim, label: serves, labelAt: [585, 197] }
- { from: claims-app, to: claims-admin, label: realizes } - { from: claims-app, to: claims-admin, label: realizes }
- { from: dmz, to: portal, label: serves } - { from: dmz, to: portal, label: serves, labelAt: [125, 397] }
- { from: app-servers, to: claims-app, label: serves } - { from: app-servers, to: claims-app, label: serves, labelAt: [355, 397] }
- { from: db-cluster, to: app-servers, label: serves } - { from: db-cluster, to: app-servers, label: serves }
@@ -51,9 +51,9 @@ boundaries:
connections: connections:
- { from: tracking-service, to: recipient, label: serves, variant: emphasis } - { from: tracking-service, to: recipient, label: serves, variant: emphasis }
- { from: deliver-shipment, to: tracking-service, label: realizes } - { from: deliver-shipment, to: tracking-service, label: realizes }
- { from: tracking-portal, to: recipient, label: serves } - { from: tracking-portal, to: recipient, label: serves, labelAt: [125, 197] }
- { from: tracking-svc, to: deliver-shipment, label: serves } - { from: tracking-svc, to: deliver-shipment, label: serves, labelAt: [585, 197] }
- { from: tms, to: tracking-svc, label: realizes } - { from: tms, to: tracking-svc, label: realizes }
- { from: mobile-network, to: tracking-portal, label: serves } - { from: mobile-network, to: tracking-portal, label: serves, labelAt: [125, 397] }
- { from: cloud-cluster, to: tms, label: serves } - { from: cloud-cluster, to: tms, label: serves, labelAt: [355, 397] }
- { from: event-streaming, to: tracking-svc, label: serves } - { from: event-streaming, to: tracking-svc, label: serves, labelAt: [585, 397] }