updates

Author: ManuelSchneid3r

src/gettingstarted/extension/cplusplus.md

@@ -17,9 +17,7 @@ A native plugin is a [Qt Plugin](https://doc.qt.io/qt-6/plugins-howto.html#the-l
 ## CMake
 
 Having a standardized plugin project structure the `albert_plugin` macro takes care of most of the CMake boilerplate code.
-Read the documentation header of the [CMake module](https://raw.githubusercontent.com/albertlauncher/albert/main/cmake/albert-macros.cmake) before you proceed.
-Its just a few lines. 
-Do not skip this!
+Read its documentation in the header of the [CMake module](https://raw.githubusercontent.com/albertlauncher/albert/main/cmake/albert-macros.cmake) before you proceed.
 This is the standard plugin directory structure of a plugin:
 
 ```
@@ -32,7 +30,7 @@ This is the standard plugin directory structure of a plugin:
    └──  …       
 ```
 
-A basic metadata file looks like this (See also the [metadata.json files](https://github.com/search?q=repo%3Aalbertlauncher%2Fplugins+path%3A**%2Fmetadata.json&type=code) of the official plugins):
+A basic metadata file looks like this (See also the [metadata.json files of the official plugins](https://github.com/search?q=repo%3Aalbertlauncher%2Fplugins+path%3A**%2Fmetadata.json&type=code)):
 
 ```json
 {
@@ -44,7 +42,7 @@ A basic metadata file looks like this (See also the [metadata.json files](https:
 }
 ```
 
-A minimal working CMakeLists.txt (See also the [CMakeLists.txt files](https://github.com/search?q=repo%3Aalbertlauncher%2Fplugins+path%3A**%2FCMakeLists.txt&type=code) of the official plugins):
+A minimal working CMakeLists.txt (See also the [CMakeLists.txt files of the official plugins](https://github.com/search?q=repo%3Aalbertlauncher%2Fplugins+path%3A**%2FCMakeLists.txt&type=code)):
 
 ```cmake
 cmake_minimum_required(VERSION 3.16)
@@ -61,8 +59,7 @@ The relevant base classes and the `ALBERT_PLUGIN` macro takes care of this.
 Albert plugins have to inherit the [`PluginInstance`](https://albertlauncher.github.io/reference/classalbert_1_1PluginInstance.html) class.
 Usually you dont want to subclass `PluginInstance` directly but rather [`ExtensionPlugin`](https://albertlauncher.github.io/reference/classalbert_1_1ExtensionPlugin.html) which implements the [`Extension`](https://albertlauncher.github.io/reference/classalbert_1_1Extension.html) interface using the metadata of the plugin instance.
 
-
-A basic plugin looks like this (Check the [plugin header files](https://github.com/search?q=repo%3Aalbertlauncher%2Fplugins+path%3A**%2FPlugin.h&type=code) of the official plugins for reference):
+A basic plugin looks like this (See also the [plugin header files of the official plugins](https://github.com/search?q=repo%3Aalbertlauncher%2Fplugins+path%3A**%2FPlugin.h&type=code)):
 
 ```cpp
 #pragma once

src/gettingstarted/extension/index.md

@@ -21,3 +21,18 @@ A quick comparison:
   - Easy to distribute/share.
   - Only a subset of the internal API.
 
+
+## General considerations and best practices
+
+### How to version plugins
+
+If it has a public API `major.minor.patch` else `minor.patch`.
+Increase major if the API breaks.
+Increase minor if the API got some backward compatible additions or the user experiences noticable changes.
+In all other cases increase patch.
+
+### Avoiding name conflicts of extension identifiers
+
+If your plugin provides multiple extensions it's a good idea to prepend the plugin id to the extension id to avoid name conflicts of extensions, e.g. `files.root_browser`.
+The root extension is fine to match the plugin id.
+

src/gettingstarted/faq.md

@@ -46,10 +46,7 @@ albert toggle
 - [KDE documentation](https://docs.kde.org/stable5/en/khelpcenter/fundamentals/shortcuts.html)
 - You are welcome to improve this list. 
 
-
-## How to make hotkeys have less latency?
-
-Note that the above runs a new app instance, which is relatively heavy.
+The above runs a new app instance, which is relatively heavy.
 Another approach is to pipe the command you want to send directly into the albert IPC socket.
 
 ```bash
@@ -113,11 +110,3 @@ QT_LOGGING_RULES='*=true' QT_DEBUG_PLUGINS=1 albert
 # Debug DBus
 QT_LOGGING_RULES='default*=true' QDBUS_DEBUG=1 
 ```
-
-
-## How to version plugins?
-
-If it has a public API `major.minor.patch` else `minor.patch`.
-Increase major if the API breaks.
-Increase minor if the API got some backward compatible additions or the user experiences noticable changes.
-In all other cases increase patch.