Improve H1 and H2 Distinctiveness
under review
Wihanga Kumara
Please Improve H1 and H2 Distinctiveness.
Suggestion - allow the user to customize H1 and H2 to differentiate.
Log In
S
Sven Erik Larsen
Right now the sizes are
H1 20px | H2 18px | P 16px
These differences are too small (1.125x per increment)
I suggest
H1 25px | H2 20px | P 16px
which is 1.250x per increment.
Tested in Taskade with CSS, and I think it looks good:
John at Taskade
under review
We will review this as we work on support for mixed-formatting to improve legibility and distinctiveness of H1, H2, etc.
John at Taskade
Merged in a post:
¶ Paragraph - additional H1, H2, H3, H4, H5, H6 text formatting
jack-s
Can also be used with H1, H2, H3, H4, H5, H6 ...
John at Taskade
Thanks for the suggestion, if we get enough requests for this, we will look into adding a few more options including H3. Note we will soon be introducing mixed-formatting and quick-formatting, which may unlock more formatting options soon.
jack-s
At least
H1 - H3
Possibly
H1 - H4
Use Markdown and type # for H1, ## for H2, or ### for H3, then press space.
#(Space)
##(Space)
###(Space)
####(Space)
Idea: Notion
John at Taskade
jack-s: Thanks for the suggestion, we will review after we introduce mixed-formatting into Taskade.
D
Dawid Bednarski
jack-s: H1-H4 would be ideal. Just enough granularity to structure all kinds of documents without using highlights.
bkonia
Agreed. Currently, there's no way to structure a document by assigning heading styles at different levels. You can only assign a heading to a top-level item. Once you start indenting below the top-level, you only have the option to make it a paragraph, not a heading. For example, I'm creating a training manual and I want to have chapters at the top level in H1, then sub-chapters indented under each chapter using H2, H3, etc... This behavior seems arbitrary. We should be able to make any item at any level into a heading and we should have more headings to choose from than just H1 and H2.
John at Taskade
bkonia: Thank you for the detailed feedback and description, we will look into this more as we start introducing mixed-formatting. Stay tuned!
CC ryantaskade
Artemis Fowl
Would be great to create rules for this by yourself - which Formation should a project use like "§" or H2 or just • - like small Settings for projects or files
John at Taskade
Artemis Fowl: Noted, thanks for the feedback.