-
Notifications
You must be signed in to change notification settings - Fork 82
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
New layout for Working Group pages #615
Comments
It would be fairly straight forward to change sizes for the font - feel free to test out and then give some a try (or others reading to do the same!) |
Also there is nothing special about the working group pages - they are blank canvases for whatever you want them to be. So this issue is more about header sizes, which would be for across the site. |
Thanks for the quick response @vsoch. I believe our conversation was geared towards creating a common layout between all working group pages. As we somewhat envisioned there would be consistency throughout them. However, if we want to have the layouts be independent for each working group, then I agree this is definitely a more generic website change we could employ. |
That would work too! It would definitely require conversation between different groups about what is needed - I figured markdown (and control of the entire page) would make sense to allow this flexibility. I wonder if it would make sense for working groups to create includes (e.g., components you add like):
and then mix and match what is desired. But again, I'm not sure about overlap of needs. Please feel free to take the reins on this one! |
The DEI-WG was going over the PR for adding a page to represent the group and noticed the layout is a bit hard to read. Specifically, the headers (h2,h3,h4) all seem comparable in size and hard to distinguish between levels of hierarchy.
We didn't come up with any solutions, but wanted to have a discussion about improving the layout for the WG pages in general/
The text was updated successfully, but these errors were encountered: