docs: module federation webcomponents#53
Closed
priyankaSandeepRade wants to merge 3 commits intoonecx:mainfrom
Closed
docs: module federation webcomponents#53priyankaSandeepRade wants to merge 3 commits intoonecx:mainfrom
priyankaSandeepRade wants to merge 3 commits intoonecx:mainfrom
Conversation
…ion-webcomponents' into docs/module-federation-webcomponents
priyankaSandeepRade
changed the title
rogocoffee
suggested changes
Apr 9, 2026
|
|
||
| As stated in xref:./microfrontend-content-loading.adoc[Microfrontend content loading documentation], every method of Microfrontend's content exposal has an impact on the OneCX platform behavior for both module and Remote Component loading. The adaptations made by OneCX to work with Web Components were briefly mentioned in the Web Components preview, however depending on the content type, the behavior varies. | ||
|
|
||
| // TODO: Link to guide of Webcomponent expose method |
Contributor
Author
There was a problem hiding this comment.
from legacy docs. addressed in this PR - #55
|
|
||
| This section explains how the Shell UI loads and renders Microfrontend modules using the Webcomponent expose method. It describes how routing, module federation, and Web Components work together, where the Shell loads the module and Web Components handle rendering through custom elements. | ||
|
|
||
| // TODO: Link to guide of Webcomponent expose method |
Contributor
Author
There was a problem hiding this comment.
from legacy docs. addressed in this PR - #55
|
|
||
| * *Web Components Binding* - Then Web Components using Custom Elements technology bounds the Microfrontend's module to the created element. | ||
|
|
||
| // Add new guide from oneCx section here |
There was a problem hiding this comment.
What is the purpose of this comment?
Contributor
Author
There was a problem hiding this comment.
As document was divided new link has to be added in this doc. Linking is done
|
|
||
| * *Webcomponent Method Difference* - The difference with the Webcomponent method is that, from the OneCX platform's perspective, no component needs to be created. Instead, a "host" element must be created to allow Web Components' Custom Elements to display desired content. | ||
|
|
||
| // Add new guide from oneCx section here |
There was a problem hiding this comment.
What is the purpose of this comment?
Contributor
Author
There was a problem hiding this comment.
As document was divided new link has to be added in this doc. Linking is done
| [#onecx-adaptation-to-webcomponent-method] | ||
| = OneCX Adaptation to Webcomponent Method | ||
|
|
||
| As stated in xref:./microfrontend-content-loading.adoc[Microfrontend content loading documentation], every method of Microfrontend's content exposal has an impact on the OneCX platform behavior for both module and Remote Component loading. The adaptations made by OneCX to work with Web Components were briefly mentioned in the Web Components preview, however depending on the content type, the behavior varies. |
There was a problem hiding this comment.
is this xref working? (cannot see the adoc in this folder)
| == Expose Microfrontend's Content as Web Components | ||
| OneCX platform offers different ways of xref:../../../architecture/mfe.adoc[exposing Microfrontend's content]. One of them is **Webcomponent method**. | ||
|
|
||
| When exposing content with Webcomponent method, it is required to ensure the correct setup. For exposing Angular content, there are functionalities provided via the <<onecx/angular-webcomponents, @onecx/angular-webcomponents>> library. For a detailed guide on how to expose Microfrontend's content via Webcomponent method, please refer here. |
There was a problem hiding this comment.
Is the last sentence intended? If yes can we make the reference clearer?
Contributor
Author
There was a problem hiding this comment.
yes linked relevant document
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.