phoenix-guidelines

Phoenix 1.8 conventions standardize LiveView layouts, routing scopes, and component usage to ensure consistency across projects. Guidelines cover avoiding unnecessary aliases, using core components for inputs, and following design-file handling practices.

To handle forms and HTTP requests in Phoenix 1.8, use core components for form inputs and the Req library for making reliable external HTTP calls. These conventions ensure consistent form handling and external data retrieval.

Audit a Phoenix app by checking component and icon usage against 1.8 guidelines, ensuring core components and hero icons are used correctly. Apply these rules to LiveView layouts and router scopes to align the project.

Yes, Phoenix 1.8 includes specific design-file handling practices to standardize layouts and assets. Following these conventions ensures that design files are managed consistently across different application layouts and LiveView templates.

The best way to organize router scopes in Phoenix 1.8 involves following routing guidelines that standardize scope aliasing and avoid unnecessary aliases. This ensures clean and scalable routing structures across the application.