Tailwind classes used in canvas code components are compiled to a file in sites/default/files/canvas/*.css.
When the flex class was used, it overrides the hidden class used in the navbar component.
Byte/mercury compile tailwind utility classes to the @utilities layer.
This issue is related: https://www.drupal.org/project/canvas/issues/3549628
There are styles in ckeditor, but not when displayed.
With aggregation enabled, the loader is not displayed.
Seems to be an issue with importing the core css into my file.
Update ajax loader theming.
This page was using the CSS Grid Layout module to place the image thumbnail inline with the content.
https://inventory.mantra.network/collections
There's a patch for adding media query support, but it hasn't been reviewed in a while.
I would like to use a custom template that is more integrated with the theme.
The starterkit theme provides a list-item stylesheet for the core item-list template.
Where is it being used?
Should it be recreated as a component?
Some theme issues are posted on theme.mantra.network.
How can I sync them with this site so they are visible?
Should I separate front end/theme issues on that site, and site building tasks on this one?
Or post issues here to get help with them.
How to build a shared theming stack?
The updated parts block on the home page has the date changed and title, but can have layout issues.
When the vite dev server is running, ajax dialogs don't open.
Trying to work on styles for the media library widget, which is shown in a modal after uploading items.
Clicking on one of these add widgets isn't working either.
https://inventory.mantra.infonet/snapshots
This might be the issue: Ajax form API adds Vite CSS-in-JS modules as CSS
I posted some findings in the issue above.
I created utility styles for .section-header that sticky the header as you scroll through a list.
