Homeview masonary to sections (#247)

Updates view creation to leverage sections for improved layout control, especially on the home view.
The home view now uses a grid layout via sections.
This change makes it easier to create complex layouts and improves responsiveness.
Previously, the card creation logic was embedded directly within each view, leading to code duplication and difficulty in customizing layouts.

The changes introduce the concept of sections, which are distinct areas within a view that can contain multiple cards.

The home view is updated to use sections for the persons, areas, and quick access cards.
This makes it easier to create responsive layouts that adapt to different screen sizes.

Author: DigiLive

.codacy.yml

@@ -0,0 +1,48 @@
+---
+engines:
+  # Modern Linting & Security
+  eslint9:
+    enabled: true
+  opengrep:
+    enabled: true
+
+  # Logic & Quality Metrics
+  lizard:
+    enabled: true
+  pmd7:
+    enabled: true
+
+  # CSS & Web Standards
+  stylelint:
+    enabled: true
+
+  # Documentation & Config
+  markdownlint:
+    enabled: true
+  spectral:
+    enabled: true
+  jackson-linter:
+    enabled: true
+
+  # Dependency Scanning (since you have package.json)
+  trivy:
+    enabled: true
+
+  # Explicitly disable Legacy
+  eslint:
+    enabled: false
+  tslint:
+    enabled: false
+  csslint:
+    enabled: false
+  pmd:
+    enabled: false
+  checkov:
+    enabled: false
+
+# Your specific exclusions
+exclude_paths:
+  - "dist/**"
+  - "src/types/homeassistant/**"
+  - "src/types/lovelace-mushroom/**"
+  - "node_modules/**"  # Standard practice to ensure speed

.github/PULL_REQUEST_TEMPLATE/documentation.md

@@ -28,12 +28,12 @@ Explain why this change is needed and the impact it has on the project or users.
 
 Please check off the following tasks that apply to your change:
 
-* [ ] I have **reviewed the existing documentation** to ensure my changes are consistent with the current style and
+- [ ] I have **reviewed the existing documentation** to ensure my changes are consistent with the current style and
   tone.
-* [ ] I have checked for and fixed any **broken links** (internal or external).
-* [ ] I have confirmed that the new/updated content is **technically accurate**.
-* [ ] I have ensured any **code snippets or examples** are properly formatted and valid.
-* [ ] I have tested that the documentation **builds and displays correctly** (if applicable, by running the local
+- [ ] I have checked for and fixed any **broken links** (internal or external).
+- [ ] I have confirmed that the new/updated content is **technically accurate**.
+- [ ] I have ensured any **code snippets or examples** are properly formatted and valid.
+- [ ] I have tested that the documentation **builds and displays correctly** (if applicable, by running the local
   documentation server).
 
 ---

.markdownlint.jsonc

@@ -1,6 +1,9 @@
 {
   "$schema": "https://raw.githubusercontent.com/DavidAnson/markdownlint/main/schema/markdownlint-config-schema-strict.json",
   "default": true,
+  "MD004": {
+    "style": "dash"
+  },
   "MD013": {
     "line_length": 120,
     "code_block_line_length": 120,

CODE_OF_CONDUCT.md

@@ -12,19 +12,19 @@ sexual identity and orientation.
 
 Examples of behavior that contributes to a positive environment for our community include:
 
-* Demonstrating empathy and kindness toward other people.
-* Being respectful of differing opinions, viewpoints, and experiences.
-* Giving and gracefully accepting constructive feedback.
-* Accepting responsibility and apologizing to those affected by our mistakes and learning from the experience.
-* Focusing on what is best not just for us as individuals, but for the overall community.
+- Demonstrating empathy and kindness toward other people.
+- Being respectful of differing opinions, viewpoints, and experiences.
+- Giving and gracefully accepting constructive feedback.
+- Accepting responsibility and apologizing to those affected by our mistakes and learning from the experience.
+- Focusing on what is best not just for us as individuals, but for the overall community.
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or advances.
-* Trolling, insulting or derogatory comments, and personal or political attacks.
-* Public or private harassment.
-* Publishing private information of others, such as a physical or email address, without their explicit permission.
-* Another conduct which could reasonably be considered inappropriate in a professional setting.
+- The use of sexualized language or imagery, and sexual attention or advances.
+- Trolling, insulting or derogatory comments, and personal or political attacks.
+- Public or private harassment.
+- Publishing private information of others, such as a physical or email address, without their explicit permission.
+- Another conduct which could reasonably be considered inappropriate in a professional setting.
 
 ## Our Responsibilities
 

CONTRIBUTING.md

@@ -56,7 +56,7 @@ If you then still feel the need to ask a question and need clarification, we rec
 
 - Open a new discussion or issue.
 - Provide as much context as you can about what you're running into.
-- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
+- Provide project and platform versions (Node.js, npm, etc.), depending on what seems relevant.
 
 We will then take care of the issue as soon as possible.
 

README.md

@@ -8,7 +8,7 @@
 
 **Effortlessly create stunning Home Assistant Dashboards with the Mushroom Dashboard Strategy!**
 
-* Are you tired of manually configuring your Home Assistant dashboards?
+- Are you tired of manually configuring your Home Assistant dashboards?
   Do you love the elegant design of Mushroom cards but wish for a simpler way to organize your entities,
   devices, and areas?
 
@@ -20,10 +20,10 @@ leveraging the power and aesthetics of Mushroom cards with minimal configuration
 
 ## ⭐ **Why Choose Mushroom Dashboard Strategy?**
 
-* **⚡️ Automatic Dashboard Generation:** Go from zero to a beautiful dashboard with just a few lines of YAML.
-* **🏡 Intelligent Organization:** Automatically creates intuitive views for your devices, areas, and entities.
-* **🎨 Highly Customizable:** Tailor your dashboard to your unique smart home setup with extensive options.
-* **📈 Integrated Insights:** Seamlessly displays mini graph cards for your sensor data.
+- **⚡️ Automatic Dashboard Generation:** Go from zero to a beautiful dashboard with just a few lines of YAML.
+- **🏡 Intelligent Organization:** Automatically creates intuitive views for your devices, areas, and entities.
+- **🎨 Highly Customizable:** Tailor your dashboard to your unique smart home setup with extensive options.
+- **📈 Integrated Insights:** Seamlessly displays mini graph cards for your sensor data.
 
 ---
 
@@ -47,13 +47,13 @@ The **Mushroom Dashboard Strategy** is available through HACS (Home Assistant Co
 
 We welcome contributions and feedback!
 
-* Have questions or need help?
+- Have questions or need help?
   Check out our [Discussions](https://github.com/DigiLive/mushroom-strategy/discussions) page.
 
-* Found a bug or have an idea?
+- Found a bug or have an idea?
   Open an [Issue](https://github.com/DigiLive/mushroom-strategy/issues).
 
-* Enjoying the Mushroom Strategy?
+- Enjoying the Mushroom Strategy?
   Consider giving our project a ⭐ [star on GitHub](https://github.com/DigiLive/mushroom-strategy) and exploring ways
   to ❤️ [sponsor the project](https://github.com/sponsors/DigiLive) to support its continued development!
   Your support helps us grow and improve.

dist/mushroom-strategy.js

@@ -8,8 +8,8 @@ Want to get your hands dirty with the code? Awesome! We appreciate all code cont
 
 3. **Test Your Changes:** Thoroughly test your changes to ensure they work as expected and don't introduce new issues.
 
-     * You can build the strategy with `npm run build` (for production) or `npm run build-dev` (for development/testing).
-     * Copy the built files to your Home Assistant's `www/community/mushroom-strategy` directory for testing.  
+     - You can build the strategy with `npm run build` (for production) or `npm run build-dev` (for development/testing).
+     - Copy the built files to your Home Assistant's `www/community/mushroom-strategy` directory for testing.  
        **Remember to clear the cache of your Home Assistant client** to see the changes.
 
     !!! info
@@ -19,8 +19,8 @@ Want to get your hands dirty with the code? Awesome! We appreciate all code cont
 
 4. **Format and Lint Your Changes:**
 
-    * Run the formatter with `npm run ts:format`.
-    * Build the strategy with `npm run build`.
+    - Run the formatter with `npm run ts:format`.
+    - Build the strategy with `npm run build`.
 
      Both of these tasks should result without errors.
 

docs/contributing/code.md

@@ -11,7 +11,8 @@ The entire documentation lives in the `docs/` folder of this repository.
 1. **Follow the [Workflow](workflow.md):**
 
 2. **Serve the Documentation Locally**:
-   Start the local development server. This task needs to be run from the **project root** (where the `mkdocs.yml` file is):
+   Start the local development server.<br>
+   This task needs to be run from the **project root** (where the `mkdocs.yml` file is):
 
     ```bash
     mkdocs serve
@@ -54,7 +55,7 @@ The entire documentation lives in the `docs/` folder of this repository.
     ```bash
     npm run md:lint-fix
     ```
-   
+
    This task should result without errors.
 
 8. **Commit Your Changes.**
@@ -69,7 +70,7 @@ The entire documentation lives in the `docs/` folder of this repository.
 
 Our documentation uses `mike` to manage multiple versions of the documentation:
 
-- **The main version**: Every time a Pull Request is merged into the main branch, the documentation at /main/ is 
+- **The main version**: Every time a Pull Request is merged into the main branch, the documentation at /main/ is
   updated.  
   This represents the "development" or "upcoming" version.
 

docs/contributing/documentation.md

@@ -25,11 +25,11 @@ Found a bug? That's not ideal, but your report helps us squash it!
    a [new issue](https://github.com/DigiLive/mushroom-strategy/issues/new?template=bug_report.yml).
 3. **Provide details:** In your report, please follow the instructions and template to include:
 
-   * A clear and concise description of the bug.
-   * Steps to reproduce the behavior.
-   * Expected behavior.
-   * Screenshots or animated GIFs (if applicable).
-   * Your Home Assistant version and Mushroom Strategy version.
+   - A clear and concise description of the bug.
+   - Steps to reproduce the behavior.
+   - Expected behavior.
+   - Screenshots or animated GIFs (if applicable).
+   - Your Home Assistant version and Mushroom Strategy version.
 
 ---