Merge pull request #36 from dotkernel/issue-27

Issue 27 - fixed

Author: arhimede

config/autoload/.gitignore

@@ -1,2 +1,3 @@
 local.php
 *.local.php
+local.test.php

public/css/app.css

@@ -1,20 +1,20 @@
 ---
-title: "DotKernel API 1.0.0 Released"
-description: "Announcement of the DotKernel API 1.0.0 release, a Zend Expressive 3 application for quickly building APIs, including the libraries it uses and the features it offers out of the box."
+title: "Dotkernel API 1.0.0 Released"
+description: "Announcement of the Dotkernel API 1.0.0 release, a Zend Expressive 3 application for quickly building APIs, including the libraries it uses and the features it offers out of the box."
 author: "Alex Karajos"
 date_published: "2019-12-15"
 canonical_url: "https://www.dotkernel.com/dotkernel-api/dotkernel-api-1-0-0-released/"
 category: "Dotkernel API"
 language: "en"
 ---
 
-# DotKernel API 1.0.0 Released
+# Dotkernel API 1.0.0 Released
 
 > Note: Dotkernel API has come a long way since this post was created; a newer version is documented separately.
 
-DotKernel API 1.0.0 was just released.
+Dotkernel API 1.0.0 was just released.
 
-## What is DotKernel API?
+## What is Dotkernel API?
 
 It is a Zend Expressive 3 application aiming to help developers quickly and efficiently develop an API.
 
@@ -36,7 +36,7 @@ Under the hood, it uses the following libraries:
 
 ## What Does It Offer?
 
-Out-of-the-box, DotKernel API provides the following features:
+Out-of-the-box, Dotkernel API provides the following features:
 
 - Secure authentication via OAuth2
 - Two user roles: admin and member
@@ -46,18 +46,18 @@ Out-of-the-box, DotKernel API provides the following features:
 
 ## FAQ
 
-**Q: What is DotKernel API?**
+**Q: What is Dotkernel API?**
 A: It is a Zend Expressive 3 application aiming to help developers quickly and efficiently develop an API.
 
-**Q: What key libraries does DotKernel API 1.0.0 use?**
+**Q: What key libraries does Dotkernel API 1.0.0 use?**
 A: Among others, it's built on the `ezimuel/zend-expressive-api` skeleton, and uses `dotkernel/dot-annotated-services` for dependency injection, `dotkernel/dot-console` for console applications, `dotkernel/dot-errorhandler` for error logging, `dotkernel/dot-mail` for SMTP email, `zend-expressive-authentication-oauth2` for OAuth2 authentication, `zend-expressive-authorization-rbac` for role-based permissions, and `swagger-api/swagger-ui` for OpenAPI 3 documentation.
 
-**Q: What features does DotKernel API 1.0.0 offer out of the box?**
+**Q: What features does Dotkernel API 1.0.0 offer out of the box?**
 A: Secure authentication via OAuth2, two user roles (admin and member), where admins can manage any user account and members can manage only their own, plus OpenAPI 3 documentation with an interactive interface developers can use to integrate the API.
 
 ## Resources
 
-- [DotKernel API 1.0.0 release on GitHub](https://github.com/dotkernel/api/releases/tag/v1.0.0)
+- [Dotkernel API 1.0.0 release on GitHub](https://github.com/dotkernel/api/releases/tag/v1.0.0)
 - [ezimuel/zend-expressive-api](https://github.com/ezimuel/zend-expressive-api)
 - [dotkernel/dot-annotated-services](https://github.com/dotkernel/dot-annotated-services)
 - [dotkernel/dot-console](https://github.com/dotkernel/dot-console)

public/llms-content/dotkernel-api/dotkernel-api-1-0-0-released.md

@@ -1,16 +1,16 @@
 ---
-title: "DotKernel API Client Side Authorization"
-description: "How a client application authorizes against a backend built with DotKernel API, from the authorization request to using the access token."
+title: "Dotkernel API Client Side Authorization"
+description: "How a client application authorizes against a backend built with Dotkernel API, from the authorization request to using the access token."
 author: "admin"
 date_published: "2019-08-05"
 canonical_url: "https://www.dotkernel.com/dotkernel-api/dotkernel-api-client-side-authorization/"
 category: "Dotkernel API"
 language: "en"
 ---
 
-# DotKernel API Client Side Authorization
+# Dotkernel API Client Side Authorization
 
-This article covers the basic authorization of a Client application which uses a backend built using DotKernel API.
+This article covers the basic authorization of a Client application which uses a backend built using Dotkernel API.
 
 ## Authorization Request
 
@@ -55,4 +55,4 @@ A: When sending API requests to an endpoint that requires authorization, include
 
 ## Resources
 
-- [DotKernel API on GitHub](https://github.com/dotkernel/api)
+- [Dotkernel API on GitHub](https://github.com/dotkernel/api)

public/llms-content/dotkernel-api/dotkernel-api-client-side-authorization.md

@@ -1,22 +1,22 @@
 ---
-title: "DotKernel API Server Side Authorization"
-description: "How to configure server-side authorization in DotKernel API, covering no-auth, authentication and authorization access levels, role inheritance, and route permissions."
+title: "Dotkernel API Server Side Authorization"
+description: "How to configure server-side authorization in Dotkernel API, covering no-auth, authentication and authorization access levels, role inheritance, and route permissions."
 author: "Alex Karajos"
 date_published: "2019-09-05"
 canonical_url: "https://www.dotkernel.com/dotkernel-api/dotkernel-api-server-side-authorization/"
 category: "Dotkernel API"
 language: "en"
 ---
 
-# DotKernel API Server Side Authorization
+# Dotkernel API Server Side Authorization
 
 ## TL;DR
 
-DotKernel API endpoints can be protected at three levels: no-auth, authentication, and authorization.
+Dotkernel API endpoints can be protected at three levels: no-auth, authentication, and authorization.
 Access is configured in `config/autoload/authorization.local.php` under the `zend-expressive-authorization-rbac` key, using a `roles` section for role inheritance and a `permissions` section for route access.
 Authentication endpoints require a valid Bearer token and return `401 Unauthorized` if it's missing, while authorization endpoints additionally check role permissions and return `403 Forbidden`.
 
-This article covers the basic authorization of a Server Side application built using [DotKernel API](https://github.com/dotkernel/api).
+This article covers the basic authorization of a Server Side application built using [Dotkernel API](https://github.com/dotkernel/api).
 
 ## Protecting an Endpoint
 

public/llms-content/dotkernel-api/dotkernel-api-server-side-authorization.md

@@ -1,5 +1,5 @@
 ---
-title: "DotKernel API versus Laminas API Tools"
+title: "Dotkernel API versus Laminas API Tools"
 description: "A feature-by-feature comparison of Laminas API Tools and Dotkernel API, showing why Dotkernel API is a solid alternative now that Laminas API Tools is archived."
 author: "Florin Bidirean"
 date_published: "2024-06-03"
@@ -8,15 +8,15 @@ category: "Dotkernel API"
 language: "en"
 ---
 
-# DotKernel API versus Laminas API Tools
+# Dotkernel API versus Laminas API Tools
 
 ## TL;DR
 
 This article compares the basic features of Laminas API Tools and Dotkernel API side by side, covering architecture, versioning, documentation, authentication, and more.
 It highlights that Dotkernel API is a solid alternative now that Laminas API Tools has been archived, since Dotkernel API uses a modern middleware architecture, MIT license, and evolution-based deprecations instead of traditional versioning.
 
-Below is an analysis of the basic features available in Laminas API Tools and DotKernel API.
-It's intended to highlight the differences between the two and also to showcase why DotKernel API is a good alternative for Laminas API Tools, especially considering the latter's archived status.
+Below is an analysis of the basic features available in Laminas API Tools and Dotkernel API.
+It's intended to highlight the differences between the two and also to showcase why Dotkernel API is a good alternative for Laminas API Tools, especially considering the latter's archived status.
 
 > The table below refers to [Dotkernel API V7](https://github.com/dotkernel/api/tree/7.0).
 

public/llms-content/dotkernel-api/dotkernel-api-versus-laminas-api-tools.md

@@ -1,21 +1,21 @@
 ---
-title: "How to implement MailChimp in DotKernel API"
-description: "A step-by-step guide to integrating MailChimp into a DotKernel API instance using the drewm/mailchimp-api library, from installation to wiring up a factory in the ConfigProvider."
+title: "How to implement MailChimp in Dotkernel API"
+description: "A step-by-step guide to integrating MailChimp into a Dotkernel API instance using the drewm/mailchimp-api library, from installation to wiring up a factory in the ConfigProvider."
 author: "Alex Karajos"
 date_published: "2020-01-04"
 canonical_url: "https://www.dotkernel.com/dotkernel-api/how-to-implement-mailchimp-in-dotkernel-api/"
 category: "Dotkernel API"
 language: "en"
 ---
 
-# How to implement MailChimp in DotKernel API
+# How to implement MailChimp in Dotkernel API
 
 ## TL;DR
 
-This is a step-by-step guide to adding MailChimp support to a DotKernel API instance using the `drewm/mailchimp-api` library.
+This is a step-by-step guide to adding MailChimp support to a Dotkernel API instance using the `drewm/mailchimp-api` library.
 It covers installing the library, creating a MailChimp config file, building a factory that returns a `DrewM\MailChimp\MailChimp` instance, and registering that factory in `ConfigProvider.php` so it can be injected wherever needed.
 
-This article will walk you through the process of implementing MailChimp into your instance of [DotKernel API](https://github.com/dotkernel/api) using [drewm/mailchimp-api](https://github.com/drewm/mailchimp-api).
+This article will walk you through the process of implementing MailChimp into your instance of [Dotkernel API](https://github.com/dotkernel/api) using [drewm/mailchimp-api](https://github.com/drewm/mailchimp-api).
 
 Step 1: Add the library to your application using the following command:
 

public/llms-content/dotkernel-api/how-to-implement-mailchimp-in-dotkernel-api.md

@@ -56,11 +56,11 @@ It's even more beneficial if the documentation is integrated with a developer po
 This helps maintain existing functionality when changes are implemented.
 - Helps troubleshooting: it defines the correct functionality that helps developers and maintainers find and fix bugs more effectively.
 
-## OpenAPI in DotKernel API
+## OpenAPI in Dotkernel API
 
-DotKernel API has full support for OpenAPI, from describing the endpoints and generating the documentation, to rendering and testing the endpoints.
+Dotkernel API has full support for OpenAPI, from describing the endpoints and generating the documentation, to rendering and testing the endpoints.
 
-Each module (Admin, App, User) in DotKernel API contains a file named `OpenAPI.php`.
+Each module (Admin, App, User) in Dotkernel API contains a file named `OpenAPI.php`.
 In this file you must document all of the endpoints from `RoutesDelegator.php`.
 The entries in `OpenAPI.php` have several descriptive items, the most important being method, request and response.
 These are used to generate a documentation file from the command line.
@@ -81,7 +81,7 @@ These are below:
 Read more details about the above [here](https://docs.dotkernel.org/api-documentation/v5/openapi/initialized-components/).
 
 Once you have your basic components defined, you can begin work on the endpoints.
-The endpoints already made available in DotKernel API are documented, so you must do the same for the new endpoints you create in your project.
+The endpoints already made available in Dotkernel API are documented, so you must do the same for the new endpoints you create in your project.
 This is done by defining these items:
 
 - the request object (Get, Post, Patch, Put, Delete)

public/llms-content/dotkernel-api/openapi-implementation-in-dotkernel-api.md

@@ -1,6 +1,6 @@
 ---
 title: "Adding a CORS implementation to Zend Expressive"
-description: "A guide on how to add a CORS implementation to an existing DotKernel3 project using Tuupola's Cors Middleware package."
+description: "A guide on how to add a CORS implementation to an existing Dotkernel3 project using Tuupola's Cors Middleware package."
 author: "Gabi DJ"
 date_published: "2019-04-08"
 canonical_url: "https://www.dotkernel.com/dotkernel/adding-a-cors-implementation-to-zend-expressive/"
@@ -12,7 +12,7 @@ language: "en"
 
 ## TL;DR
 When a client-side request is blocked with a "No 'Access-Control-Allow-Origin' header" error, it's because the server isn't sending the header that allows a browser to access its data (most common when fetching JSON to process with JavaScript).
-This guide adds CORS support to a Zend Expressive / DotKernel3 project using Tuupola's Cors Middleware package.
+This guide adds CORS support to a Zend Expressive / Dotkernel3 project using Tuupola's Cors Middleware package.
 
 ## The issue
 

public/llms-content/dotkernel/adding-a-cors-implementation-to-zend-expressive.md

@@ -1,22 +1,22 @@
 ---
-title: "Adding Composer support in your DotKernel project"
-description: "The steps needed to add Composer support to a DotKernel 1.x project, or 'composify' it."
+title: "Adding Composer support in your Dotkernel project"
+description: "The steps needed to add Composer support to a Dotkernel 1.x project, or 'composify' it."
 author: "Gabi DJ"
 date_published: "2016-04-04"
 canonical_url: "https://www.dotkernel.com/dotkernel/adding-composer-support-in-your-dotkernel-project/"
 category: "Dotkernel"
 language: "en"
 ---
 
-# Adding Composer support in your DotKernel project
+# Adding Composer support in your Dotkernel project
 
 ## TL;DR
 Composer is an application-level package manager that auto-loads dependencies (and custom classes) on demand.
-This article covers the steps needed to add a composer.json file to a DotKernel project, run `composer update`, and safely require the generated autoloader so the project works whether or not Composer is present.
+This article covers the steps needed to add a composer.json file to a Dotkernel project, run `composer update`, and safely require the generated autoloader so the project works whether or not Composer is present.
 
 ## First things first
 
-The DotKernel project must have a **composer.json** file so that Composer can work.
+The Dotkernel project must have a **composer.json** file so that Composer can work.
 It should look like this:
 
 ```json
@@ -41,15 +41,15 @@ This file makes sure:
 
 The dependencies provided in the `require` section are also loaded for development purposes if not provided in `require-dev`.
 
-In order to have these components installed, run the following command in your DotKernel root path:
+In order to have these components installed, run the following command in your Dotkernel root path:
 
 ```shell
 composer update
 ```
 
 If the `vendor` folder is present, Composer will check for updates and update the packages as needed. If the `vendor` folder does not exist, Composer will create it, containing all the requested packages, along with an autoload file used to load the dependencies/packages.
 
-## Adding Composer Support to DotKernel
+## Adding Composer Support to Dotkernel
 
 The autoload file created by Composer is used to load the packages:
 
@@ -85,15 +85,15 @@ $myDependency = new MyDependency($neededArguments);
 $myDependency->doSomething();
 ```
 
-This article works for any **DotKernel 1.x** version if your server is running **PHP >5.4.0**.
+This article works for any **Dotkernel 1.x** version if your server is running **PHP >5.4.0**.
 
 ## FAQ
 
 **Q: What does Composer do?**
 A: Composer is an application-level package manager.
 It auto-loads dependencies on demand and can also auto-load custom classes.
 
-**Q: What must a DotKernel project have before Composer can be used?**
+**Q: What must a Dotkernel project have before Composer can be used?**
 A: A composer.json file, for example requiring zendframework/zendframework1 at 1.12.* and mobiledetect/mobiledetectlib at 2.8.*, plus PHP >=5.4.0 listed under require-dev.
 
 **Q: What happens when you run composer update?**
@@ -103,10 +103,10 @@ If it doesn't exist, Composer creates the vendor folder containing all requested
 **Q: How do you safely load the Composer autoloader in case Composer isn't present?**
 A: Check whether vendor/autoload.php exists using file_exists() before calling require_once() on it, and handle the case gracefully (for example by loading fallbacks) if the path is missing.
 
-**Q: Which DotKernel versions does this apply to?**
-A: The article states it works for any DotKernel 1.x version, as long as the server is running PHP greater than 5.4.0.
+**Q: Which Dotkernel versions does this apply to?**
+A: The article states it works for any Dotkernel 1.x version, as long as the server is running PHP greater than 5.4.0.
 
 ## Resources
 
 - [Composer install / PHP dependency manager tutorial](https://www.codementor.io/php/tutorial/composer-install-php-dependency-manager)
-- [Using DotKernel with Composer dependencies](http://www.dotkernel.com/dotkernel/using-dotkernel-…ser-dependencies/)
+- [Using Dotkernel with Composer dependencies](http://www.dotkernel.com/dotkernel/using-dotkernel-…ser-dependencies/)