generated from theradcoza/Laravel-Docker-Dev-Template
1.2 KiB
1.2 KiB
Template Improvement Suggestions
This document contains suggestions for improving the template based on recurring development issues.
1. Mandatory Module Settings Page
Rule: When creating a new module, the AI agent must always create a corresponding settings page within the admin panel.
Minimum Requirements: This settings page must, at a minimum, allow an administrator to configure which user roles have Create, Read, Update, and Delete (CRUD) permissions for that module.
Rationale: This has been a recurring issue. Automating the creation of a permission management UI for each module makes the template more robust, secure, and user-friendly out-of-the-box. It prevents situations where new modules are added without any way for an admin to control access to them.
Example Implementation:
- When a
Blogmodule is created, aBlog Settingspage should also be created. - This page should contain a form with checkboxes or a multi-select dropdown for each CRUD permission (
blog.view,blog.create,blog.edit,blog.delete). - An administrator can then select which roles (e.g., 'admin', 'editor', 'viewer') are granted each of these permissions.