-
Notifications
You must be signed in to change notification settings - Fork 1
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
Restructure tasks #91
Conversation
- [x] merge everything to one page, not enough content for several, also facilitates navigation - [x] use `details` for each submitting procedure - [x] shorten WG titles, use description for details - [ ] some example of WG3 activities missing
@ruthlorenz @jonasjucker @mjaehn @AnnikaLau This is a proposition reflecting personal taste, it's not (much) about content. Please tell if you disagree. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some spelling corrections.
Also: Do we want to add a TOC at the top of the page?
Co-authored-by: Michael Jähn <[email protected]>
Co-authored-by: Michael Jähn <[email protected]>
Co-authored-by: Michael Jähn <[email protected]>
Co-authored-by: Michael Jähn <[email protected]>
Co-authored-by: Michael Jähn <[email protected]>
I was not sure it's big enough of a page for it but I can add a collapsible one. |
Found no way to control the depth of TOC so manually added {: .no_toc} to low-level headings
Just did that, have a look. Not sure it adds a lot and it's rather large compared to the rest of the page. I mean nothing is far away by just scrolling. |
No need for a "note" title in the box
Actually I like it a lot, it is a good overview and folks can jump directly to a certain topic / WG. Plus it is collapsible. Two more suggestions from @jonasjucker and me:
|
The motivation is that "below" doesn't say much. Maybe I try to find other words if I remove the link.
That was for correct typography but it seems it's not necessary anymore. However it needs a comma after. |
Well actually that's fine. I removed the links and kept "below". The page is not big enough for these sort of links to be useful. |
also write "three" in word and slightly rephrase the part about issues to avoid repetitions.
Which I would argue also holds for the table of content ;-). But that's fine, it's fancy collapsible, we can keep it |
@mjaehn seems like you'r estill requeting changes but I can't figure out where. |
details
for each submitting procedure