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

Redesign issues!! #6

Open
1 of 7 tasks
lewisakura opened this issue Apr 11, 2023 · 4 comments
Open
1 of 7 tasks

Redesign issues!! #6

lewisakura opened this issue Apr 11, 2023 · 4 comments

Comments

@lewisakura
Copy link
Member

lewisakura commented Apr 11, 2023

This is an issue tracker specifically for the redesign and what needs to be fixed.

  • Heading line-heights are all weird. We need to find better ones.
  • Move Downloads to the right. It was cool but it screws up people's muscle memory.
  • Take a look at any style overrides and see if they should be the defaults rather than individual overrides.
  • Better icons for the plugins page. They're a bit out of place and don't really suit their meanings.
    • Whilst we're at it, add an icons key somewhere (maybe in the footer?)
    • Add more bottom padding to cards (3em should do it, see WebContextMenus for why we need to do this)
  • Vertically center pages that don't fill up 100% of the content(?)
@ggtylerr ggtylerr mentioned this issue Apr 13, 2023
@ggtylerr
Copy link
Contributor

For icons, I suggest using icomoon for any icons that aren't on FA (a bit of work to get it on the site each time you change the icon set, but completely free and allows you to use any additional icons. also based on fonts so it works in a lot of browsers.)

As for an icon key, I think it makes more sense to show it on the top of the page. It doesn't require the user to scroll all the way down for it, and it can be short and sweet:
image
(mockup I did in PDN, real implementation will have to be a bit larger and change a bit of the surrounding elements)

@refact0r
Copy link
Contributor

perhaps a different font? (inter is boring)

figtree
image

epilogue
image

@justin13888
Copy link

For icons, I suggest using icomoon for any icons that aren't on FA (a bit of work to get it on the site each time you change the icon set, but completely free and allows you to use any additional icons. also based on fonts so it works in a lot of browsers.)

As for an icon key, I think it makes more sense to show it on the top of the page. It doesn't require the user to scroll all the way down for it, and it can be short and sweet: image (mockup I did in PDN, real implementation will have to be a bit larger and change a bit of the surrounding elements)

Interesting enhancement but we should think of meaningful icons for different categorizations for plugins (e.g. some may be purely visual, some add feature enhancements)? Idk what would be exactly useful though

@justin13888
Copy link

perhaps a different font? (inter is boring)

figtree image

epilogue image

Existing font looks better than those two

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

No branches or pull requests

4 participants