mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
fix docs build (#113948)
This commit is contained in:
parent
226b8e86a0
commit
e9fc5196ab
1 changed files with 4 additions and 4 deletions
|
@ -17,13 +17,13 @@ already existing applications. Did you know that almost everything you see in th
|
|||
Kibana UI is built inside a plugin? If you removed all plugins from Kibana, you'd be left with an empty navigation menu, and a set of
|
||||
developer tools. The Kibana platform is a blank canvas, just waiting for a developer to come along and create something!
|
||||
|
||||

|
||||

|
||||
|
||||
## 1,000 foot view
|
||||
|
||||
At a super high-level, Kibana is composed of **plugins**, **core**, and **Kibana packages**.
|
||||
|
||||

|
||||

|
||||
|
||||
**Plugins** provide the majority of all functionality in Kibana. All applications and UIs are defined here.
|
||||
|
||||
|
@ -51,7 +51,7 @@ We try to put only the most stable and fundamental code into `Core`, while optio
|
|||
|
||||
Today it looks something like this.
|
||||
|
||||

|
||||

|
||||
|
||||
"Platform plugins" provide core-like functionality, just outside of core, and their public APIs tend to be more volatile. Other plugins may still expose shared services, but they are intended only for usage by a small subset of specific plugins, and may not be generic or "platform-like".
|
||||
|
||||
|
@ -91,7 +91,7 @@ A plugin may register many applications, or none.
|
|||
|
||||
Applications are top level pages in the Kibana UI. Dashboard, Canvas, Maps, App Search, etc, are all examples of applications:
|
||||
|
||||

|
||||

|
||||
|
||||
A plugin can register an application by
|
||||
adding it to core's application <DocLink id="kibPlatformIntro" section="registry" text="registry"/>.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue