-
Notifications
You must be signed in to change notification settings - Fork 0
Style Guide
Martin Mendoza edited this page Jun 5, 2025
·
3 revisions
This page outlines the principles and standards for UI/UX design and code style within the StateForce project.
- Consistency in layout and interactions.
- Accessibility best practices.
- Responsive design for multiple device sizes.
- Primary colors and their usage.
- Secondary/supporting colors.
- Accessibility considerations (contrast ratios, etc.).
- Fonts used (families, sizes, weights).
- Usage guidelines for headers, body text, etc.
- List of reusable UI components (buttons, forms, modals, etc.).
- Example usage and appearance for each component.
- Icon library used (if any).
- Guidelines for using images, illustrations, and icons.
- Structure of CSS/SCSS or Tailwind utility classes.
- Naming conventions for classes and IDs.
- Ruby/Rails style conventions.
- Naming and organization of files, modules, and classes.
- ES6+ standards.
- Naming conventions and structure for Stimulus controllers.
- Tools used (Rubocop, ESLint, Prettier, etc.).
- How to run linters and fix issues.
- ARIA attributes and semantic HTML.
- Keyboard navigation support.
- Screenshots or code snippets demonstrating best practices.
- Links to external design systems, style guides, or documentation for further reading.
We are always looking for feedback and contributions to improve StateForce. Feel free to open issues, suggest edits, or submit pull requests to the repository.
- Repo: StateForce GitHub
- Contact: martinmendozadev@gmail.com
If you encounter issues or need assistance, please reach out via:
- Email: martinmendozadev@gmail.com
- GitHub Issues: Submit an Issue
This documentation and the StateForce platform are licensed under the Apache License 2.0.
Thank you for using StateForce! π¨
Together, we are improving emergency response operations in real-time.
Welcome to the StateForce Wiki! Use this sidebar to navigate through the documentation.
This sidebar provides quick access to all the documentation pages. For detailed information, click on the desired section.