Repository navigation
Conversation
|
If we remove files like public/css/milligram.min.css how does bake work? One possibility is that bake is improved to include a 'default' theme, and we have hooks for the bake theme to generate layout files, css and javascript required for that application theme. |
@markstory the css includes replacement css so bake templates render correctly - see the application styles screenshot. Not happy about the looks of it though, its better than the miligram version but still a bit in-cohesive so ill attempt to iterate on this in the coming weeks |
The welcome page and application layouts still depend on Milligram and bundled fonts. This replaces them with handwritten CSS and redesigns the CakePHP 6 welcome page without adding frontend dependencies, configuration, or a build step.
The welcome page shares resets, theme colors, typography, buttons, and accessibility styles with
public/css/cake.css, while loading its specific layout and animations frompublic/css/home.cssthrough the HTML helper. It introduces a responsive hero with the inline Cake logo, an animated gradient background and version number, grouped development checks, and a simpler footer with Discord. Reduced-motion and forced-colors preferences are supported.Default and error layouts use the same stylesheet, including forms, tables, and Bake layouts. Flash messages gain keyboard-accessible dismiss buttons. Unused CSS and font assets are removed, and the README describes the new styling approach. Welcome-page tests cover successful and failed connections, escaped exception details, optional DebugKit, view blocks, and the production guard.
Dependency
This draft is stacked on #1109 and targets
prepare/6.x-skeletonso the diff contains only the styling and welcome-page changes. Retarget to6.xafter that PR merges. PHP 8.5 requirements, CI, and attribute-resolver configuration comments remain in #1109.Validation
git diff --checkpass.Welcome/home dark and light
Application styles
Error pages