Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up mainpage data layout Deadlock #5219

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

Kanopedia
Copy link
Collaborator

Summary

Setting up the data for the Deadlock Mainpage revamp:

How did you test this change?

https://liquipedia.net/deadlock/User:Kanoodles/TestTest

Copy link
Collaborator

@hjpalpha hjpalpha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems reasobable, assuming it is tested

return {
main = {
{ -- Left
size = 6,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider to assign more space to the right side and reduce this to e.g. 5, as otherwise (depending on the display resolution) there isn't really enough space for the tournaments list:
image
That one could also benefit of removed padding on it's panel.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mbergen Which panel specifically did you mean to have removed padding?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

5 doesn't work I think, has to be a number dividable by 12 (1, 2, 3, 4, 6, 12)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you mean 12 dividable by it ;)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which panel specifically did you mean to have removed padding?

The tournaments list panel, the padding looks weird anyways since the header bars for upcoming/ongoing/concluded don't extend to the edge

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

5 doesn't work I think, has to be a number dividable by 12 (1, 2, 3, 4, 6, 12)

Sure it does, you can choose any number between 1 and 12. You just have to see that the total of all columns you want in the row is less or equal to 12, as otherwise they are wrapped to another row.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I did look at it with removing the padding, however to me it then seems pretty off / fall out of the design. (Moreso noticeable on darkmode
image

children = {
{
mobileOrder = 1,
content = CONTENT.aboutEsport,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This content doesn't seem to exist

},
},
{
mobileOrder = 4,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's two things with mobile order 4

padding = true,
boxid = 1510,
},
specialEvents = {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why no boxid on special events? Makes it non collaps-able

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Testing this live here; https://liquipedia.net/deadlock/Module:MainPageLayout/data Added a boxid but it doesn't seem to add a collapse to the special event box. (In this case special event is just the heroes)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants