You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/components/client-side-operations.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -796,7 +796,7 @@ Available settings:
796
796
|`retryInterval`|`number` (milliseconds) | Retry interval for when component rendering fails | 5000 |
797
797
|`retryLimit`|`number`| Max number of retries when component rendering fails | 30 |
798
798
|`retrySendNumber`|`boolean`| Appends an `__ocRetry=(number)` to a request to mark the retry number. This is a quite powerful feature that you can handle in the server-side logic in order to make your component even behave differently in case something is going wrong | true |
799
-
|`templates`|`array`| The configuration needed for performing client-side rendering of legacy template types. ES6 templates (default) don't require configuration. |`[{"type": "oc-template-jade","externals": [{"global": "jade","url": "https://unpkg.com/[email protected]/runtime.js"}]},{"type": "oc-template-handlebars","externals": [{"global": "Handlebars","url": "https://cdnjs.cloudflare.com/ajax/libs/handlebars.js/4.0.6/handlebars.runtime.min.js"}]}]`|
799
+
|`templates`|`array`| The configuration needed for performing client-side rendering of legacy template types. ES6 templates (default) don't require configuration. |`[{"type": "oc-template-jade","externals": [{"global": "jade","url": "https://unpkg.com/[email protected]/runtime.js"}]},{"type": "oc-template-handlebars","externals": [{"global": "Handlebars","url": "https://cdnjs.cloudflare.com/ajax/libs/handlebars.js/4.0.6/handlebars.runtime.min.js"}]}]`|
800
800
|`tag`|`string`| The html tag you want to use for your components in the page |`oc-component`|
Welcome! In this section you’ll find high-level material that helps you understand _why_ OpenComponents exists and _how_ its pieces fit together. Start here if you want the big picture before diving into tutorials or code.
8
+
9
+
-**Introduction** – a birds-eye view and quick install.
10
+
-**Architecture Overview** – explore the design principles behind the Registry, Templates, and OC-Client.
Copy file name to clipboardExpand all lines: website/docs/intro.md
+18-11Lines changed: 18 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ OpenComponents is a framework for building and deploying **micro frontends** - s
9
9
## What is OpenComponents?
10
10
11
11
Think of OpenComponents as a way to break down your frontend into small, manageable pieces that can be:
12
+
12
13
-**Developed independently** by different teams
13
14
-**Deployed separately** without affecting other parts
14
15
-**Reused across** multiple applications
@@ -49,19 +50,19 @@ The framework consists mainly of three parts:
49
50
- The **[Library](#setup-a-library)** is where the components are stored after publishing. When components depend on static resources (such as images, CSS files, etc.) these are stored, during packaging and publishing, in a publicly-exposed part of the library that serves as CDN.
50
51
- The **[Registry](#setup-a-registry)** is a REST API that is used to consume, retrieve, and publish components. Since they are immutable, the registry is the entity that handles the traffic between the library and the consumers.
51
52
52
-
For a detailed technical overview, see our [Architecture Overview](miscellaneous/architecture-overview).
53
+
For a detailed technical overview, see our [Architecture Overview](concepts/architecture-overview).
|`package`| The component definition, dependencies, and more. |
61
62
|`view`| The view in charge to output the final markup. OC uses `ES6` templates by default and comes with a powerful template system to support components built with any javascript UI framework like `React`, `Angular`, `Vue`. Legacy `Handlebars` and `Jade` templates are still supported for backwards compatibility. |
62
-
|`server` (optional) | If the component need logic, including consuming services, this is the entity that will produce the view-model to compile the view. |
63
-
| static assets (optional) | Images, Javascript, and files to be uploaded to the CDN and referenced in the HTML markup. |
64
-
|\*| Any other files that will be useful for the development such as tests, docs, etc. |
63
+
|`server` (optional) | If the component need logic, including consuming services, this is the entity that will produce the view-model to compile the view. |
64
+
| static assets (optional) | Images, Javascript, and files to be uploaded to the CDN and referenced in the HTML markup. |
65
+
|\*| Any other files that will be useful for the development such as tests, docs, etc. |
65
66
66
67
After publishing, components are immutable and semantic versioned.
67
68
@@ -117,6 +118,7 @@ You don't need Node.js to consume components on the server-side. The registry ca
117
118
When published, components are immutable and semantic versioned. The registry allows consumers to get any version of the component: the latest patch, or minor version, etc.
118
119
119
120
**When to use OpenComponents:**
121
+
120
122
- Building micro frontends with multiple teams
121
123
- Need for independent deployment of UI components
122
124
- Sharing components across different applications
@@ -259,23 +261,28 @@ For the registry configuration's documentation, [look at this page](/docs/regist
259
261
**Choose your path based on your role:**
260
262
261
263
### 🚀 **I'm new to OpenComponents**
264
+
262
265
Start with the [Quick Start Tutorial](quick-start-tutorial) for a complete hands-on introduction.
0 commit comments