3.2.1

.github/CONTRIBUTING.md

@@ -2,49 +2,18 @@
 
 Follow these guidelines if you'd like to contribute to the project!
 
----
 
-## Table of contents
-
-Read through these guidelines before you get started:
-
-1. [Questions & Concerns](#questions--concerns)
-2. [Issues & Bugs](#issues--bugs)
-3. [Feature Requests](#feature-requests)
-4. [Submitting Pull Requests](#submitting-pull-requests)
-5. [Code Style](#code-style)
-
-## Questions & concerns
+## Questions
 
 If you have any questions about using or developing for this project, reach out to @bugfishtm.
 
-## Issues & bugs
+## Issues
 
 Submit an issue or pull request with a fix if you find any bugs in
-the project. When submitting an issue or pull request, make sure you're as detailed as possible and fill in all answers to questions asked in the templates. For example, an issue that simply states "X/Y/Z isn't working!" will be closed.
-
-## Feature requests
-
-Submit an issue to request a new feature. Features fall into one of two
-categories:
-
-1. **Major**: Major changes should be discussed via email. I'm
-   always open to suggestions and will get back to you as soon as I can!
-2. **Minor**: A minor feature can simply be added via a pull request.
-
-## Submitting pull requests
-
-Before you do anything, make sure you check the current list of pull requests 
-to ensure you aren't duplicating anyone's work. Then, do the following:
+the project. When submitting an issue or pull request, make sure you're as detailed as possible.
 
-1. Fork the repository and make your changes in a git branch: `git checkout -b my-branch base-branch`
-2. Read and follow the code style guidelines.
-3. Make sure your feature or fix doesn't break the project! Test thoroughly.
-4. Commit your changes, and be sure to leave a detailed commit message.
-5. Push your branch to your forked repo on GitHub: `git push origin my-branch`
-6. Submit a pull request and hold tight!
-7. If any changes are requested by the project maintainers, make them and follow this process again until the changes are merged in.
+## Features
 
-## Code style
+Submit an issue to request a new feature. 
 
-Please mark your changes by comments inside the code structure.
+🐟 Bugfish <3

.github/ISSUE_TEMPLATE.md

@@ -1,26 +1,7 @@
-# Submit a feature request or bug report
+Issues & Features:
 
-Before you submit an issue, check to see if it has already been reported!  
-Any questions should be directed to @bugfishtm.
-
----
-
-
-## Information
-
-- Operating System: X
-- Browser: X
-- Software Version: X
-- Software Build: X
-
-## Description
+- Include screenshots if possible and describe the issue you have or the feature you want to have included.
+- Add steps if possible to reproduce your issue, that the support can better understand whats going on if you post an issue.
+- Add relevant Software / Server or Device Information to solve your issue.
 
-Include screenshots if possible and describe the issue you have or the feature you want to add. If you are adding a bug report, try to add upper information like software version and operating system, so we can better understand your issue. This is a general issue template, in some repositories some requested information may not be necessary or required.
-
-## Steps to reproduce
-
-Add steps if possible to reproduce your issue, that the support can better understand whats going on.
-
-## Other relevant information
-
-Add any other relevant information about this issue.
+Any questions should be directed to @bugfishtm.

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,32 +1,12 @@
-# Submit a pull request
+Please provide information:
 
-Thank you for submitting a pull request! To speed up the review process, please ensure that everything below
-is true:
+- Details: Provide details about your pull request and what it adds, fixes, or changes.
+- Issues fixed: Enter the issue numbers resolved by this pull request below, if any.
+
+Please check your request:
 
 1. This is not a duplicate of an existing pull request.
 2. No existing features have been broken without good reason.
 3. Your commit messages are detailed.
-4. The code style guidelines have been followed.
-5. Documentation has been updated to reflect your changes.
-6. Tests have been added or updated to reflect your changes.
-7. All tests have passed.
 
 Any questions should be directed to @bugfishtm.
-
----
-
-## Pull request details
-
-Provide details about your pull request and what it adds, fixes, or changes.
-
-## Breaking changes
-
-Describe what features are broken by this pull request and why, if any.
-
-## Issues fixed
-
-Enter the issue numbers resolved by this pull request below, if any.
-
-## Other relevant information
-
-Provide any other important details below.

CHANGELOG.md

@@ -1,14 +1,3 @@
 # Changelog
 
-## [3.2.0] - 2024-08-22
-### Release - "Enhanced Performance and Versatility"
-
-**Description:**
-Version 3.2 marks a significant milestone for our software. With no known bugs and a commitment to answer support requests promptly, we are delivering a robust and reliable tool. It's worth noting that no further features are planned for this software, as our focus remains on refining and perfecting the existing functionalities.
-
-### Key Features:
-- **Performance Boost:** Enjoy faster execution and smoother operations across the board.
-- **Enhanced Compatibility:** This release ensures compatibility with a wider range of systems and configurations.
-- **Improved User Interface:** A more user-friendly interface provides a smoother and more intuitive experience.
-
-Upgrade to version 3.2 to experience these enhancements and benefit from a software version that's fine-tuned to perfection.
+See _changelogs folder to get insights into different version changes.

CONTRIBUTING.md

@@ -2,49 +2,18 @@
 
 Follow these guidelines if you'd like to contribute to the project!
 
----
 
-## Table of contents
-
-Read through these guidelines before you get started:
-
-1. [Questions & Concerns](#questions--concerns)
-2. [Issues & Bugs](#issues--bugs)
-3. [Feature Requests](#feature-requests)
-4. [Submitting Pull Requests](#submitting-pull-requests)
-5. [Code Style](#code-style)
-
-## Questions & concerns
+## Questions
 
 If you have any questions about using or developing for this project, reach out to @bugfishtm.
 
-## Issues & bugs
+## Issues
 
 Submit an issue or pull request with a fix if you find any bugs in
-the project. When submitting an issue or pull request, make sure you're as detailed as possible and fill in all answers to questions asked in the templates. For example, an issue that simply states "X/Y/Z isn't working!" will be closed.
-
-## Feature requests
-
-Submit an issue to request a new feature. Features fall into one of two
-categories:
-
-1. **Major**: Major changes should be discussed via email. I'm
-   always open to suggestions and will get back to you as soon as I can!
-2. **Minor**: A minor feature can simply be added via a pull request.
-
-## Submitting pull requests
-
-Before you do anything, make sure you check the current list of pull requests 
-to ensure you aren't duplicating anyone's work. Then, do the following:
+the project. When submitting an issue or pull request, make sure you're as detailed as possible.
 
-1. Fork the repository and make your changes in a git branch: `git checkout -b my-branch base-branch`
-2. Read and follow the code style guidelines.
-3. Make sure your feature or fix doesn't break the project! Test thoroughly.
-4. Commit your changes, and be sure to leave a detailed commit message.
-5. Push your branch to your forked repo on GitHub: `git push origin my-branch`
-6. Submit a pull request and hold tight!
-7. If any changes are requested by the project maintainers, make them and follow this process again until the changes are merged in.
+## Features
 
-## Code style
+Submit an issue to request a new feature. 
 
-Please mark your changes by comments inside the code structure.
+🐟 Bugfish <3

_changelogs/3.2.0.html

@@ -0,0 +1,13 @@
+    <h1>Version 3.2 Release Notes</h1>
+    <p>
+        Version 3.2 marks a significant milestone for our software. With no known bugs and a commitment to answer support requests promptly, we are delivering a robust and reliable tool. It's worth noting that no further features are planned for this software, as our focus remains on refining and perfecting the existing functionalities.
+    </p>
+    <h2>Key Features:</h2>
+    <ul>
+        <li><strong>Performance Boost:</strong> Enjoy faster execution and smoother operations across the board.</li>
+        <li><strong>Enhanced Compatibility:</strong> This release ensures compatibility with a wider range of systems and configurations.</li>
+        <li><strong>Improved User Interface:</strong> A more user-friendly interface provides a smoother and more intuitive experience.</li>
+    </ul>
+    <p>
+        Upgrade to version 3.2 to experience these enhancements and benefit from a software version that's fine-tuned to perfection.
+    </p>

_changelogs/3.2.1.html

@@ -0,0 +1,6 @@
+    <h1>Version 3.2.1 Release Notes</h1>
+    <h2>Key Features:</h2>
+    <ul>
+        <li><strong>Minor Optimizations:</strong> Minor Optimizations for the Software.</li>
+        <li><strong>Ignore "." Domain Fix:</strong> Does now ignore unvalid . domain on DNS Server Retrieval of Domains.</li>
+    </ul>

_changelogs/README.md

@@ -0,0 +1,5 @@
+📑 **Changelog Archive**
+
+This directory serves as a repository for historical changelogs documenting various releases of the software. While certain versions may be absent or inaccessible due to obsolescence or irrelevance for current distribution, it functions as a comprehensive record of the software's significant release modifications.
+
+🐟 Bugfish <3

_images/README.md

@@ -10,5 +10,4 @@ To incorporate these images in the repository's readme file, utilize the followi
 
 Replace Alt Text with a descriptive text for the image and image_path with the relative path to the image file within this folder.
 
-Happy coding and have a great one!  
 🐟 Bugfish <3

_source/README.md

@@ -1,6 +1,9 @@
-📑 **Source Folder**
+📁 **Website Source Code**
 
-This folder contains the primary source code for the project. The code here is intended to be copied, modified, or integrated into other projects by the end-user. Ensure to review any dependencies or configurations needed to run the code effectively.
+Welcome to the Root Directory of your website! This folder contains the complete website code that should be uploaded to your web server to make your website operational.
 
-Happy coding and have a great one!  
-🐟 Bugfish <3
+Upon deploying this website code to your web server, MySQL tables will be installed automatically. These tables are essential for storing and managing dynamic data required by your website, such as user information, content, and settings.
+
+Developers are advised to visit our documentation at https://bugfishtm.github.io/suitefish-cms
+
+🐟 Bugfish <3  

_source/_cronjob/daily.php

@@ -1,11 +1,31 @@
 <?php
-	/*
-		__________              _____.__       .__     
-		\______   \__ __  _____/ ____\__| _____|  |__  
-		 |    |  _/  |  \/ ___\   __\|  |/  ___/  |  \ 
-		 |    |   \  |  / /_/  >  |  |  |\___ \|   Y  \
-		 |______  /____/\___  /|__|  |__/____  >___|  /
-				\/     /_____/               \/     \/  Daily Cronjob to Reset IP BLacklist */
+	/* 
+		 ____  __  __  ___  ____  ____  ___  _   _ 
+		(  _ \(  )(  )/ __)( ___)(_  _)/ __)( )_( )
+		 ) _ < )(__)(( (_-. )__)  _)(_ \__ \ ) _ ( 
+		(____/(______)\___/(__)  (____)(___/(_) (_) www.bugfish.eu
+			 _______ ______ _______ ______  
+			(_______|_____ (_______|______) 
+			 _  _  _ _____) )     _ _     _ 
+			| ||_|| |  __  / |   | | |   | |
+			| |   | | |  \ \ |___| | |__/ / 
+			|_|   |_|_|   |_\_____/|_____/  
+											
+		Copyright (C) 2024 Jan Maurice Dahlmanns [Bugfish]
+
+		This program is free software: you can redistribute it and/or modify
+		it under the terms of the GNU General Public License as published by
+		the Free Software Foundation, either version 3 of the License, or
+		(at your option) any later version.
+
+		This program is distributed in the hope that it will be useful,
+		but WITHOUT ANY WARRANTY; without even the implied warranty of
+		MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+		GNU General Public License for more details.
+
+		You should have received a copy of the GNU General Public License
+		along with this program.  If not, see <https://www.gnu.org/licenses/>.
+	*/
 	// Configurations Include
 		require_once(dirname(__FILE__) ."/../settings.php");