[Feature Request] Two "row styled groups" next to each other

[bassterror]

Description

Hello awesome people,
I'm sorry if this request isn't appropriate/necessary, but I couldn't figure out if this is currently possible.
Is there a way we can put two groups (style: row; columns: 2) next to each other?
From this:

To this (bad photoshop):

Other

No response

[glime-ai[bot]]

Based on the context provided, it seems you are looking to customize the layout of the Homepage dashboard to place two groups side by side, each with a configuration of style: row and columns: 2.

From the information available in the context, there is a discussion (#2852) where a user figured out how to display two topics side by side by adjusting the indentation in their YAML configuration. Here is the solution they provided:

layout:
  Administration:
    style: row
    columns: 2

Media:
    style: row
    columns: 4

AdBlocking:
    style: row
    columns: 4

However, this solution seems to be for different column sizes and may not directly apply to your case. To achieve your specific layout, you may need to adjust the number of columns for each group to match your desired outcome. If the groups you want to place side by side are named differently, you can try configuring them in your settings.yaml file like so:

layout:
  Group1Name:
    style: row
    columns: 2
  Group2Name:
    style: row
    columns: 2

Make sure that Group1Name and Group2Name are replaced with the actual names of your groups. Also, ensure that the indentation is correct, as YAML is sensitive to indentation.

If this does not achieve the desired result, or if you encounter any issues, you may need to experiment further with the layout configuration or seek assistance from the Homepage community, as suggested in the GitHub discussions and issues provided in the context.

Please note that the images you provided in your request are not accessible (the links are broken), so I cannot see the exact layout you are aiming for. If you need further assistance with the exact YAML configuration or have specific requirements, please provide more details or correct links to the images.

---

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

This comment was generated by Glime.

[Vigrond]

The answer is that you need to omit style: row. Unfortunate that this is nowhere to be found in the documentation, in addition to the AI bot above being completely wrong and suggesting malformed yaml.

In technical terms, style: row forces basis-full in the tailwind css responsive design for a group. Without it, it falls back to a flex grid based on your screen size.

columns will have no effect here either, since it is dependent on style: row

The design logic here seems to be that you have a flex grid for non style: row groups dependent on your screen size, with the max columns being 4 for services and 6 for bookmarks.

Then when you want to "break" the flex layout, you put a new group with style: row.

[SrOlalau]

He is right, here you have how i have the settings.yaml configured:

And this is how i see it:

[NWBx01]

This doesn't really achieve what OP is asking about, does it? It just allows groups to be next to one another, instead of being able to have groups next to one another and specifying their number of columns. This already is the default behavior because the default style is column, so the following two layouts are identical in appearance.

layout:
  group-1:
  group-2:

layout:
  group-1:
    style: column
  group-2:
    style: columm

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.