You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we use the plain HTML instead of markdown syntax at lexicon.md, this is not friend to contribution a bit, and the 2nd question is hard to reference a specific definition, which is a very common usage at other glossary tables.
So I'm curious why do we maintain in the HTML way, does a PR to change to markdown headings looks good if I want to contribute to?
The text was updated successfully, but these errors were encountered:
HI @yorkie I used the decription list elements since they are semantically meaningful and define a relationship between the terms and definitions. I wouldn't know how to achieve that using only markdown tags.
I really like the idea of linkable definitions, but H4's (like dt's) carry semantic meaning. These aren't actually headers so we wouldn't want to imply to search engines or assistive technologies that they are.
One thing I should clarify... The file in src is not meant to be the published document. The HTML file in docs is meant to be viewed at https://ecmatc53.github.io/lexicon. We probably need to elevate that link in the readme so it's the first thing users see.
With that in mind, we could absolutely add this kind of functionality to the published page by modifying the template file.
Hi, we use the plain HTML instead of markdown syntax at
lexicon.md
, this is not friend to contribution a bit, and the 2nd question is hard to reference a specific definition, which is a very common usage at other glossary tables.So I'm curious why do we maintain in the HTML way, does a PR to change to markdown headings looks good if I want to contribute to?
The text was updated successfully, but these errors were encountered: