First, thank you for considering contributing to DemonZ Deployer. Collaborative effort is what makes open-source development powerful.
This document outlines the official process for contributing to the repository, ensuring a highly professional, organized, and efficient workflow.
By participating in this project, you are expected to uphold a standard of professional, collaborative, and respectful behavior. Unprofessional conduct will not be tolerated.
Bugs and technical issues are tracked via GitHub Issues. When creating an issue, please include the following diagnostic information:
- A concise summary of the problem.
- Exact steps to reproduce the behavior.
- Your operating system and browser version (e.g., Android 14, Chrome Mobile).
- Any relevant terminal logs or error codes presented in the Deployer UI.
Feature requests and enhancement suggestions are also tracked via GitHub Issues. When proposing a new feature, please detail:
- The specific problem your feature solves.
- A detailed description of the proposed functionality or UI change.
- Why this feature aligns with the serverless, zero-friction vision of DemonZ Deployer.
DemonZ Development welcomes pull requests for bug fixes, documentation improvements, and verified feature additions. To ensure a streamlined review process, adhere to the following steps:
- Fork the repository and create your working branch from
main. - Utilize clear, descriptive branch names (e.g.,
fix/terminal-scrollorfeat/dark-mode-toggle). - Ensure your modifications strictly adhere to the existing architectural design (zero-server, client-side only execution).
- Test your changes locally to ensure no existing functionality is broken.
- Submit a pull request containing a detailed breakdown of your modifications and the reasoning behind them.
DemonZ Deployer operates entirely on a static serverless architecture. There are no external backend dependencies, build tools, or local servers required to test the frontend interface.
- Clone your fork to your local environment.
- Open
index.htmldirectly in your preferred web browser. - Apply modifications to the HTML, CSS, or JS architecture as required.
We utilize conventional commit messaging to maintain a clean and readable repository history. Please prefix your commit messages using the following standards:
feat:(Introduction of a new feature)fix:(Resolution of a bug or error)docs:(Modifications to documentation or the README)style:(Code formatting, interface adjustments, or typographical corrections)refactor:(Code structure changes that neither fix a bug nor add a direct feature)
Thank you for contributing to DemonZ Development.