Minor Changes

Author: app-generator

docs/boilerplate-code/_category_.json

@@ -1,12 +1,12 @@
 {
-	"label": "BOILERPLATE CODE",
+	"label": "Boilerplate Code",
 	"position": 6,
 	"className": "section-title",
 	"collapsed": true,
 	"collapsible": true,	
 	"link": {
 		"type": "generated-index",
 		"slug": "/boilerplate-code",
-		"description": "Here are the articles in this section"
+		"description": "Boilerplate Code & Starters actively supported by AppSeed."
 	}
 }

docs/developer-tools/flask-dynamic-api.mdx

@@ -15,8 +15,7 @@ For newcomers, **Flask** is a leading backend framework used to code from simple
 
 ## ✅ Video Presentation
 
-<YoutubeEmbed url="https://user-images.githubusercontent.com/51070104/194328733-3bdf8c70-f765-4168-983d-2a51e276239b.mp4" title="Flask Dynamic API - Open-Source tool provided by AppSeed" />
-
+<YoutubeEmbed url="https://www.youtube.com/embed/jrdwFsNLZfw" title="Flask Dynamic API - Open-Source tool provided by AppSeed" />
 
 ## ✅ Manual Build 
 

docs/technologies/django/01-getting-started.mdx

@@ -13,14 +13,14 @@ Django can help us to code from simple, one-page websites, APIs, micro-services,
 It enables developers to build robust applications rapidly while helping developers to avoid security mistakes since Django takes security seriously. 
 Django is flexible and scalable and comes with a lot of tools prebuilt into it for example, its Object relation mapper (ORM), admin dashboard, user authentication and lots more.
 
+![Getting Started with Django - Tutorial provided by AppSeed.](https://user-images.githubusercontent.com/51070104/268675023-54ea4ace-a8ad-442b-9b43-2ba12a6403ba.jpg)
+
 Django adopts the MTV (Model Template View) architectural pattern. **Model** determines the data structure and is a handler between the database and the view. 
 **Template** keeps everything the browser renders, django uses a plain text template system. **View** communicates with the database using the model and sends the data to the template to be displayed. 
 
 The framework acts as a controller sending requests to the right view based on the URL configuration. 
 Django's MVT pattern emphasizes the separation of concerns and modularity, making it easier to develop and maintain web applications with a clear separation between business logic, data access, and presentation.
 
-![Getting Started with Django - Tutorial provided by AppSeed.](https://user-images.githubusercontent.com/51070104/268675023-54ea4ace-a8ad-442b-9b43-2ba12a6403ba.jpg)
-
 ## ✅ Why Using Django
 
 * Django enables rapid development by eliminating a lot of the hassle of web development
@@ -40,7 +40,7 @@ This can help prevent dependency issues and also help in reproducibility.
 
 <br />
 
-### Creating a Virtual environment
+### 👉 Creating a Virtual environment
 
 * From the terminal, type the following commands
 
@@ -69,7 +69,7 @@ $ venv\Scripts\activate
 
 <br />
 
-### Installing Django
+### 👉 Installing Django
 
 Since our virtual environment is active we can install Django and start development. In your terminal run the following commands
 ```bash
@@ -84,7 +84,7 @@ A Django project is a collection of settings and configurations that define the
 
 <br />
 
-### Creating the Project
+### 👉 Creating the Project
 
 A Django project is created using the `django-admin` command-line tool. `django-admin startproject <project-name>` is the command used to create a new Django project.
 
@@ -107,7 +107,7 @@ After running the command above, your directory structure will look like this. T
 
 <br />
 
-### Applying initial Database configuration
+### 👉 Applying initial Database configuration
 
 Django comes with some database configurations which can be found in `core/settings.py`, the default database configuration for Django is SQLite3. 
 Django is built to integrate with a lot of popular databases like MySQL, Postgresql, Oracle and so on. 
@@ -132,26 +132,26 @@ This starts up a Django server, open `http://127.0.0.1:8000/` in your browser, y
 
 In Django, an application is a self-contained module of code that provides specific functionality to a project. It is a collection of models, views, templates, and other related files that work together to implement a particular feature or set of features. An application is typically stored in its directory within the project's directory structure. Each application contains a set of files that define its functionality, including:
 
-* Models: A model is a Python class that defines the structure of a database table and the relationships between tables. Models are used to define the data structure of the application.
+- **Models**: A model is a Python class that defines the structure of a database table and the relationships between tables. Models are used to define the data structure of the application.
 
-* Views: A view is a Python function that processes HTTP requests and returns HTTP responses. Views are used to define the logic for handling user requests and rendering the appropriate response.
+- **Views**: A view is a Python function that processes HTTP requests and returns HTTP responses. Views are used to define the logic for handling user requests and rendering the appropriate response.
 
-* Templates: A template is an HTML file that defines the layout and structure of the application's web pages. Templates are used to define the presentation layer of the application.
+- **Templates**: A template is an HTML file that defines the layout and structure of the application's web pages. Templates are used to define the presentation layer of the application.
 
-* URLs: A URL is a string that maps to a view function. URLs are used to define the routing for the application.
+- **URLs**: A URL is a string that maps to a view function. URLs are used to define the routing for the application.
 
-* Static files: Static files are files such as CSS, JavaScript, and images that are used to define the presentation layer of the application.
+- **Static files**: Static files are files such as CSS, JavaScript, and images that are used to define the presentation layer of the application.
 
 <br />
 
-### Creating a Django APP
+### 👉 Creating a Django APP
 
 Using the `django-admin` command from the terminal, we will be creating a Django application inside the project directory. `django-admin startapp <app-name>` is the command used for creating new applications.
 
-* Run the command below on your terminal to create a Django application name example
+Run the command below on your terminal to create a Django application name example
 
 ```bash
-(venv) $ django-admin  startapp example
+(venv) $ django-admin startapp example
 ```
 
 With this, a new application called `example` has been created. The new folder structure for the project will become
@@ -180,7 +180,7 @@ Although we have created an application, the Django project does not recognize o
 
 <br />
 
-### Update Settings 
+### 👉 Update Settings 
 
 To connect `example` to the Django project `core`, open the file `core/settings.py` and add `example` to the `INSTALLED_APPS` list.
 
@@ -202,7 +202,7 @@ Now our Django project recognizes the `example` application.
 
 <br />
 
-### Updating Project Routes
+### 👉 Updating Project Routes
 
 Now that the Django project can recognize the `example` application, the next step is to give the application a route. By doing this we create a generic route that when visited, Django checks this application for resources to send back to the client.
 
@@ -223,7 +223,7 @@ If your Django server was running when this change was made, you would be having
 
 <br />
 
-### Serving an HTML Page
+### 👉 Serving an HTML Page
 
 * Edit the `core/settings file by adding a route to template files for Django to use in identifying resources to be sent as the response
 
@@ -394,7 +394,7 @@ The application just built will be deployed on [Render](https://render.com) and
 
 <br />
 
-### Initial setup
+### 👉 Initial setup
 
 Before we can start deploying our project, we need to make some changes to our codebase.
 
@@ -479,7 +479,7 @@ The changes made above combine the configuration for Docker and deploying on ren
 
 <br />
 
-### Deploying Django on Render
+### 👉 Deploying Django on Render
 
 * In the root directory of your application, create a file name `build.sh` and add the following line
 ```bash
@@ -532,7 +532,7 @@ fi
 
 <br />
 
-### Running Django project on Docker
+### 👉 Running Django project on Docker
 
 The following steps will help you create a docker image and start up a docker container for your Django project
 

docs/technologies/django/01-releases.mdx

@@ -11,19 +11,27 @@ For newcomers, Django is a high-level, open-source Python web framework known fo
 
 ![Django Releases - Tutorial provided by AppSeed.](https://user-images.githubusercontent.com/51070104/268675023-54ea4ace-a8ad-442b-9b43-2ba12a6403ba.jpg)
 
-## **Django 4.2.6** (October, 2023):
+## ✅ **[Django 5](https://blog.appseed.us/django-5-release-summary-and-sample/)** `alpha 1` (September 18, 2023)
+
+- **Django 5.x** supports Python 3.10, 3.11, and 3.12
+- [Facets](https://docs.djangoproject.com/en/dev/ref/contrib/admin/filters/#facet-filters) processing updates
+- Simplified templates for form field rendering
+- Database-computed default values
+- Database generated model field
+
+## ✅ **Django 4.2.6** (October, 2023):
 
 - Django 4.2.6 fixes several bugs in 4.2.5
 - Fix Security Issue `CVE-2023-41164`
   - Potential denial of service vulnerability in django.utils.encoding.uri_to_iri()
 
-## **Django 4.2.4** (August, 2023):
+## ✅ **Django 4.2.4** (August, 2023):
 
 - Fixed a regression in Django 4.2 that caused a crash of QuerySet.aggregate() with aggregates referencing window functions (#34717).
 - Fixed a regression in Django 4.2 that caused a crash when grouping by a reference in a subquery (#34748).
 - Fixed a regression in Django 4.2 that caused aggregation over query that uses explicit grouping by multi-valued annotations to group against the wrong columns (#34750).
 
-## **Django 4.2.2** (June, 2023):
+## ✅ **Django 4.2.2** (June, 2023):
 
 BugFixes:
 
@@ -34,134 +42,134 @@ BugFixes:
 - Fixed a bug in Django 4.2 where makemigrations --update didn’t respect the --name option (#34568).
 - Fixed a performance regression in Django 4.2 when compiling queries without ordering (#34580).
 
-## **Django 4.2** (April, 2023):
+## ✅ **Django 4.2** (April, 2023):
 
 - Psycopg 3 support  
   - Django now supports psycopg version 3.1.8 or higher. To update your code, install the psycopg library, you don`t need to change the ENGINE as django.db.backends.postgresql supports both libraries.
 - Comments on columns and tables
   - The new `Field.db_comment` and `Meta.db_table_comment` options allow creating comments on columns and tables, respectively.
 
-## **Django 4.0** (December, 2021):
+## ✅ **Django 4.0** (December, 2021):
 
 - zoneinfo default timezone implementation
 - scrypt password hasher
 - Redis cache backend
 - Template based form rendering
 
-## **Django 3.2** (April 2021):
+## ✅ **Django 3.2** (April 2021):
 
 - Extended support for Python 3.9.
 - Introduced improved speed and performance enhancements.
 
-## **Django 3.1** (August 2020):
+## ✅ **Django 3.1** (August 2020):
 
 - Extended support for Python 3.8 and 3.9.
 - Introduced stricter database constraints.
 - Enhanced security features.
 
-## **Django 3.0** (December 2019):
+## ✅ **Django 3.0** (December 2019):
 
 - Dropped support for Python 3.5.
 - Added support for Python 3.8.
 - Introduced path converters in URL routing.
 
-## **Django 2.2** (April 2019):
+## ✅ **Django 2.2** (April 2019):
 
 - Extended support for Python 3.7 and 3.8.
 - Included database and performance improvements.
 
-## **Django 2.1** (August 2018):
+## ✅ **Django 2.1** (August 2018):
 
 - Added support for Python 3.7.
 - Included features like multi-database support and easier handling of static files.
 
-## **Django 2.0** (December 2017):
+## ✅ **Django 2.0** (December 2017):
 
 - Dropped support for Python 2.x.
 - Required Python 3.4 or later.
 - Included various improvements and updates.
 
-## **Django 1.11** (April 2017):
+## ✅ **Django 1.11** (April 2017):
 
 - Extended support for Python 3.6.
 - Introduced "subquery" expressions.
 - Included an easier way to format template text.
 
-## **Django 1.10** (August 2016):
+## ✅ **Django 1.10** (August 2016):
 
 - Introduced full support for Python 3.5.
 - Added features like template-based widget rendering.
 
-## **Django 1.9** (December 2015):
+## ✅ **Django 1.9** (December 2015):
 
 - Included support for PostgreSQL's "upsert" feature.
 - Improved password hashing.
 - Enhanced customizability of the admin interface.
 
-## **Django 1.8** (April 2015):
+## ✅ **Django 1.8** (April 2015):
 
 - Added support for the "Django Rest Framework."
 - Included native support for complex database types like JSON.
 - Other improvements.
 
-## **Django 1.7** (September 2014):
+## ✅ **Django 1.7** (September 2014):
 
 - Introduced the "migrations" framework as a core feature.
 - Allowed database schema changes to be version-controlled.
 
-## **Django 1.6** (November 2013):
+## ✅ **Django 1.6** (November 2013):
 
 - Brought significant improvements in testing and authentication.
 - Added support for database schema migrations.
 
-## **Django 1.5** (February 2013):
+## ✅ **Django 1.5** (February 2013):
 
 - Introduced custom user models.
 - Added a new timezone support model.
 - Configurable user authentication system.
 
-## **Django 1.4** (March 2012):
+## ✅ **Django 1.4** (March 2012):
 
 - Added timezone support.
 - Supported user-uploaded static files.
 - Improved scalability.
 
-## **Django 1.3** (March 2011):
+## ✅ **Django 1.3** (March 2011):
 
 - Added class-based views.
 - Improved file handling.
 - Better support for NoSQL databases.
 
-## **Django 1.2** (May 2010):
+## ✅ **Django 1.2** (May 2010):
 
 - Added support for multiple database connections.
 - Improved form handling.
 - Enhanced internationalization features.
 
-## **Django 1.1** (July 2009):
+## ✅ **Django 1.1** (July 2009):
 
 - Introduced features like aggregation and transaction-based testing.
 - Improved support for PostgreSQL.
 
-## **Django 1.0** (September 2008):
+## ✅ **Django 1.0** (September 2008):
 
 - First official stable release.
 - Included the admin interface, authentication, and many core features.
 
-## **Django 0.96** (March 2006):
+## ✅ **Django 0.96** (March 2006):
 
 - Focused on code quality and compatibility, laying the groundwork for future versions.
 
-## **Django 0.95** (January 2006):
+## ✅ **Django 0.95** (January 2006):
 
 - Added support for database migrations.
 - Improved documentation and template support.
 
-## **Django 0.91** (October 2005):
+## ✅ **Django 0.91** (October 2005):
 
 - Introduced features like the automatic admin interface and template inheritance.
 
-## **Django 0.90** (July 2005):
+## ✅ **Django 0.90** (July 2005):
 
 - First public release of Django.
 - Open-sourced under the BSD license.

docs/technologies/flask/01-releases.mdx

@@ -7,7 +7,14 @@ sidebar_label    : Releases
 
 This page presensts the history of Flask starting from the latest versions.
 
-## ✅ **Flask 2.3.3 (August 2023)****
+## ✅ [Flask 3](https://blog.appseed.us/flask-3-release-and-free-samples/) (September 2023)
+
+- Require Werkzeug >= 3.0.0
+- Restructure the code and Blueprint classes
+- Deprecate the version attribute
+- Remove Deprecated Code 
+
+## ✅ **Flask 2.3.3 (August 2023)**
 
 - Python 3.12 compatibility.
 - Require Werkzeug >= 2.3.7.