diff --git a/change/@microsoft-fast-element-508f24cc-5d36-4192-9b5b-b342f60bad5d.json b/change/@microsoft-fast-element-508f24cc-5d36-4192-9b5b-b342f60bad5d.json new file mode 100644 index 00000000000..26a98be64ac --- /dev/null +++ b/change/@microsoft-fast-element-508f24cc-5d36-4192-9b5b-b342f60bad5d.json @@ -0,0 +1,7 @@ +{ + "type": "none", + "comment": "chore: add DESIGN.md and fix architecture doc errors", + "packageName": "@microsoft/fast-element", + "email": "7559015+janechu@users.noreply.github.com", + "dependentChangeType": "none" +} diff --git a/packages/fast-element/ARCHITECTURE_FASTELEMENT.md b/packages/fast-element/ARCHITECTURE_FASTELEMENT.md index e227474a2bf..d6e451a1205 100644 --- a/packages/fast-element/ARCHITECTURE_FASTELEMENT.md +++ b/packages/fast-element/ARCHITECTURE_FASTELEMENT.md @@ -42,7 +42,7 @@ flowchart TD The rendering of the template on the `ElementController` is by the `renderTemplate` method which is called during the `ElementController.connect` method which is triggered by `HTMLElement`s `connectedCallback` lifecycle. -The `renderTemplate` identifies the Custom Element, and the shadow root associated with the Custom Element. This then places a rendering of the template (an `ElementView`) onto the internal `view` of the controller. When creating the `ElementView`/`HTMLView` using the `ViewTemplate.render`, the `Compile.compile()` method identifies a `DocumentFragment` either by using an existing `