check the sidebar

content/action/overview.md

@@ -4,7 +4,7 @@ weight = 1
 +++
 
 * Actions are used when you want to execute something on certain events (broadcast everyone when the player clicked the button, etc).
-* There are many built-in types of actions. There will be listed in the sections below. A developer can also create his own action and register to this plugin.
+* There are many built-in types of actions (Check the sidebar). A developer can also create his own action and register to this plugin.
 
 ## Example
 ```yaml
@@ -18,17 +18,3 @@ hello:
   POSITION-X: 1
   POSITION-Y: 1
 ```
-
-## Built-ins
-* [Back Menu]({{% ref "menu-back" %}})
-* [Close Menu]({{% ref "menu-close" %}})
-* [Open Menu]({{% ref "menu-open" %}})
-* [Update Menu]({{% ref "menu-update" %}})
-* [Console Executor]({{% ref "console" %}})
-* [Player Executor]({{% ref "player" %}})
-* [OP Executor]({{% ref "op" %}})
-* [Permission Executor]({{% ref "permission" %}})
-* [Broadcast Message]({{% ref "broadcast" %}})
-* [Tell Message]({{% ref "tell" %}})
-* [Play Sound]({{% ref "sound" %}})
-* [Delay]({{% ref "delay" %}})

content/argument/overview.md

@@ -6,7 +6,7 @@ weight = 1
 * Argument Processor is a special unit that handles the arguments of a menu, mainly from [Open Menu Command]({{% ref "basic/command" %}}) and [Open Menu Action]({{% ref "action/menu-open" %}})
 * The arguments are splitted and handled by multiple processors in the configured order.
 * The processors are specified in the `argument-processor` section of the `menu-settings`.
-* There are many built-in types of processors. There will be listed in the sections below. A developer can also create his own processor and register to this plugin.
+* There are many built-in types of processors (Check the sidebar). A developer can also create his own processor and register to this plugin.
 
 ## Example
 ```yaml
@@ -38,11 +38,3 @@ button:
 * Each processor provide its own variable to be used in the menu.
 * The format: `{arg_<processor_name>}`
 * For example: `{arg_hello}`, `{arg_message}`
-
-## Built-ins
-* [Store]({{% ref "store" %}})
-* [Player]({{% ref "player" %}})
-* [Number]({{% ref "number" %}})
-* [Decimal]({{% ref "decimal" %}})
-* [Material]({{% ref "material" %}})
-* [Entity]({{% ref "entity" %}})

content/button/overview.md

@@ -6,7 +6,7 @@ weight = 1
 * A button is what is shown in the menu.
 * When the player clicks a button, some actions are executed.
 * A button can also be updated.
-* There are many built-in types of button. A developer can make his own button and register to the plugin.
+* There are many built-in types of button (Check the sidebar). A developer can make his own button and register to the plugin.
 * You can specify the type of button by setting the `type` option.
 
 ## Example

content/menu/overview.md

@@ -4,7 +4,7 @@ weight = 1
 +++
 
 * Menus are what BetterGUI is for. It's the thing displayed to the player.
-* There are many built-in types of Menu. A developer can also make his own menu and register to the plugin.
+* There are many built-in types of Menu (Check the sidebar). A developer can also make his own menu and register to the plugin.
 * Generally, a menu contains 2 sections: `menu-settings` and [**Button**]({{% ref "../button/overview" %}})
 * You can set the type of menu by setting the `menu-type` value in the `menu-settings` section
 

content/modifier/overview.md

@@ -4,7 +4,7 @@ weight = 1
 +++
 
 * Item Modifier is the property of an item. It describes what the final item should be.
-* There are a lot of built-in modifiers for items. A developer can also make his own modifier and register to the plugin.
+* There are a lot of built-in modifiers for items (Check the sidebar). A developer can also make his own modifier and register to the plugin.
 
 ## Example
 ```yaml

content/requirement/overview.md

@@ -5,7 +5,7 @@ weight = 1
 
 * Requirement is one of the interesting parts of the plugin.
 * It is used when you want to check if the player meets some sort of requirements before doing anything (Check the level before opening the menu, etc).
-* There are many built-in types of requirements, which will be listed below. A developer can also make his own requirement type and register it to the plugin.
+* There are many built-in types of requirements (Check the sidebar). A developer can also make his own requirement type and register it to the plugin.
 
 {{% notice info %}}
 What you see in the examples & set in your [Menu]({{% ref "menu/overview" %}}) is actually [**Requirement Set**]({{% ref "set" %}}).