Contributing to Frakto CSS Order

August 21, 2025 · View on GitHub

First off, thank you for considering contributing to this project — your input helps make it better for everyone!

Frakto CSS Order defines a logical categorization and order for all CSS properties, inspired by browser rendering phases, developer experience, and best practices. If you'd like to contribute, please read the following guidelines.

Philosophy

Every contribution should aim to preserve the clarity, predictability, and maintainability of the transformation pipeline. Code must be written with long-term extensibility in mind, following consistent patterns and strict syntax rules.

We aim to maintain:

  • Simplicity: The structure should be easy to understand and use.
  • Clarity: Categories and order must be logically explained and consistently applied.
  • Practicality: This order should feel intuitive to real developers writing real CSS.

Contributing

We welcome community contributions. Whether it's fixing a typo or suggesting a whole new direction, you're invited to help improve this project.

Bug Reports

If you find an issue with the categorization, a missing property, or any inconsistency, please open a Bug Report. Clear examples and context will help us solve it faster.

Feature Requests

Got an idea to enhance the project? We'd love to hear it. Open a Feature Request with a short explanation of your proposal and how it could improve developer experience.

Pull Requests

Before submitting a pull request, make sure your changes are clear, purposeful, and align with the structure of the project. Always reference the related issue (if any) and explain your reasoning in the PR description. Let’s keep it clean and consistent.

Guidelines

Emoji guidelines

Emojis are strictly prohibited in all code comments, docblocks, commit messages, and documentation.
They may not be used under any circumstance. Code should remain clean, professional, and timeless.

Language guidelines

All code, comments, docblocks, commit messages, and documentation must be written in English at all times. No exceptions are allowed. Consistency in language ensures clarity and global accessibility.

License

By contributing your code, you agree to license your contribution under the MIT License.