#UI Suite Initiative

I was setting it up to be composed in layout builder.

Footer is used as a layout, where you can place footer menu and aside components.

I am interpreting daisyui.com as flexible examples, not a set of limited variations.

I was going for a system that allows maximum customization, especially since we can use UI Styles for color and spacing.

I'm unsure how someone would set up the different variations, it sounds like everything will be hardcoded in page.html.twig?

Hi @mortona2k,

Thanks for your work. However, you created 3 components: footer, footer_menu, and aside.

footer_menu and aside don't exist in DaisyUI according to the documentation: https://daisyui.com/components/

Only footer is documented: https://daisyui.com/components/footer/

Moreover, looking at the templating, it seems aside is not a component but a simple HTML element:

<aside{{ attributes }}>
  {{ content }}
</aside>

And footer_menu markup doesn't look like the one of a self contained component.

Also, we don't need custom CSS here. The CSS is handled by DaisyUI. Maybe you needed to add some because of the 3 components instead of one.

What you need to do in my opinion:

1. create footer as described in the DaisyUI documentation. Nothing more, nothing less.
2. add footer_nav & footer_aside regions to theme info.yml
3. call the component from page.html.twig by mapping the regions to the slots, and setting the default footer if you want

Take a look at the footer, footer menu, and aside components I created.

Set up links in a footer menu, then add this as a block, select the menu, and the top level links should render as column headers.

You can add an aside. I haven't set up Social Links yet.

Center should be working.

I made some adjustments to the spec and commented on why in https://docs.google.com/document/d/1DJCsANcHH7lnbxfUlHnX7m_2kiWdqAN8YWM9...

I built the footer template to work as a layout section to work on it visually and swap the menu/aside position.
But the implementation has an issue - it switches visually but can't save it.

Social links needed for footer.

(There are some limitations in comparison, would be great to add those, like the options to render/link the selected parent item)

We are open to proposals: https://www.drupal.org/project/issues/ui_patterns → :)

I was experimenting with the UI Suite ecosystem and DaisyUI, this is my first time with both.

I hope you are enjoying this discovery

OH, I think I get it now.

I was able to place a menu SDC as a block in LB, and I can see how the form to select the menu/level is similar to Menu Block.

(There are some limitations in comparison, would be great to add those, like the options to render/link the selected parent item)

I'll try to align with your spec. I was experimenting with the UI Suite ecosystem and DaisyUI, this is my first time with both.

Here's another approach, using UI Styles for color, padding, and the footer class.

Thanks to the attributes prop, it will be possible to use UI styles with the footer component.

But first, we need the footer component :)

The Menu Block module lets you set the theme hook to use if you want to change footer to use something else, or use another menu.

It is already handled by the MenuSource plugin for links props. If we do this component the right way, UI Patterns 2 will plug it to many Drupal API. It is magical :)

Layout builder and DaisyUI have a ton of options for building footer variations.

Let's not thing about the display builder while authoring the component. Let's build a good component, focused on UI and implemenattion of the upstream design system documentation, and it will work on layout builder and others.

My little proposal si still relevant IMHO: https://docs.google.com/document/d/1DJCsANcHH7lnbxfUlHnX7m_2kiWdqAN8YWM9...