Merge branch 'main' into testing-docs

Author: rdeutz

.drone.yml

@@ -34,9 +34,13 @@ steps:
     when:
       branch:
         - main
+      status:
+        - success
+      event:
+        - push
 
 ---
 kind: signature
-hmac: e6468d58ea392aa80b1b56fb50e5d2774fc255844c55bdb8073b05ac7b4e8859
+hmac: 348c8ac11879e5515a5b167c9af1a7d6bba2f3bd66408a291f4f9f6ff27d8204
 
 ...

docs/general-concept/the-lifecycle

@@ -0,0 +1,8 @@
+Joomla's Lifecycle
+============
+Detailed walkthrough of the lifecycle of the Joomla's different applications
+:::caution TODO
+
+This page is unfinished, please use the **Edit this Page** link at the bottom of this page to help make it more useful.
+
+:::

docs/get-started/codestyle.md

@@ -4,16 +4,16 @@ sidebar_position: 5
 Coding Style Guide
 =======================
 
-Since Joomla version 4.2 Joomla is using the [PSR-12](https://www.php-fig.org/psr/psr-12/) coding standard. You can enable the coding standard in your IDE to get hints when you're violating the rules or can use an auto fix, too.
-We recommend that you follow this standard also when developing your own extensions to stay compatible always with core and that you don't have to switch when working with core.
+Since Joomla version 4.2, Joomla uses the [PSR-12](https://www.php-fig.org/psr/psr-12/) coding standard. You can enable this coding standard in your IDE and get hints if you're not following the coding standard or use an auto fix, too.
+We recommend that you follow this standard when developing your own extensions to stay compatible with core and to ensure your code will hopefully work with future versions.
 
 ## Install code style checker
 :::caution TODO
 Copy from https://docs.joomla.org/Joomla_CodeSniffer and update to the new version
 :::
 
 ## Use integrated checker
-The Joomla core system is shipping a so called "code sniffer" and a "code fixer" to check for code standard violations and to fix most (but sometimes not all) of them. This only works if you're using the full developer version from GitHub, not when you're working with a installation zip package.
+If you download the full developer version from GitHub of Joomla (not the downloadable installation zip package), you will find a so called "code sniffer", to check for coding standard violations, and a "code fixer" to fix most (but, sometimes, not all) of them. 
 
 To run the code sniffer/fixer you need to start a terminal, navigate to your Joomla root folder (the folder where your Joomla is installed) and run one of the following commands (don't forget the "."):
 

docs/get-started/ide/index.md

@@ -3,17 +3,17 @@ sidebar_position: 1
 ---
 IDE
 ===
-To develop a Joomla extension we recommend to use an Integrate Development Environment (IDE). An IDE has many benefits:
+To develop a Joomla extension we recommend that you use an Integrated Development Environment (IDE). An IDE has many benefits:
 - Code completion
-  - Getting suggestions for code to save reseaching code and avoid errors
-  - Auto-implement namespace usage
+  - Getting suggestions for code completion which saves researching existing code and helps avoid errors
+  - Auto-implementing namespace usage
   - Type hinting when using well documented classes, methods and functions
-  - Auto comments for classes/methods/functions
+  - Building auto comments for classes/methods/functions
 - Code analyser
   - Automate code style feedback
   - Hints for "smelling code" to improve the code quality
 - Project/Folder management for extension projects
-- many addons/support for daily coding
+- Many addons/support for daily coding
 
 The two current leading IDEs are [Visual Studio Code](get-started/ide/visual-studio-code.md) and [phpStorm](get-started/ide/phpstorm.md)
 

docs/get-started/index.md

@@ -5,7 +5,7 @@ sidebar_position: 1
 Get Started
 ===============
 ## Welcome to the Joomla Developers Manual
-The purpose of this guide is to give developers an upto date guide showing best practice in
+The purpose of this guide is to give developers an up to date guide showing best practice in
 writing and maintaining Joomla extensions.
 It also offers a migration path for extensions from older Joomla! versions to the latest standard.
 We will run through the tools and process required to set up a local development environment with
@@ -15,7 +15,7 @@ the ability to get the most out of the guide as a developer.
 - @TODO
 
 ## Community
-- Check the latest state od the Joomla CMS code at [GitHub](https://github.com/joomla/joomla-cms)
+- Check the latest state of the Joomla CMS code at [GitHub](https://github.com/joomla/joomla-cms)
 - Find the latest version at [Joomla.org](https://joomla.org)
 - Join our [Mattermost-Community](https://joomlacommunity.cloud.mattermost.com/)
 - Read the [End-User documentation](https://docs.joomla.org)
@@ -26,14 +26,13 @@ the ability to get the most out of the guide as a developer.
 The Joomla Developers Manual is written using Docusaurus, a system that can allow all users of Joomla to
 contribute to the documentation using Markdown language.
 
-A good place to start if new to Markdown is the Markdown Guide
+A good place to start, if new to Markdown, is the Markdown Guide
 https://www.markdownguide.org/
 
-The documentation is maintained via GitHub where you can anytime create/edit/delete content to improve the content
-of the documentation. Click the **Edit this Page** link at the bottom of this page to contribute via a Pull Request.
+The documentation is maintained via GitHub where you can at anytime create/edit/delete content to improve the documentation. Click the **Edit this Page** link at the bottom of this page to contribute via a Pull Request.
 
 :::caution TODO
 
 This page is unfinished, please use the **Edit this Page** link at the bottom of this page to help make it more useful.
 
-:::
+:::