-
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
[Crum/Flashcards] Organize the HTML #233
Comments
We split the page into sections represented by `<div>` tags. This will make the HTML prettier (tidy handle `<div>` tags intelligently). It will also come in handy in the future when we want to extract specific sections from the HTML, as we want to do in #229. Notice that the use of `<div>` tags makes a lot of `<br>` tags idempotent, so we remove them.
This will make it possible to produce cleaner search text for Xooxle. Similar classes were added to the main HTML in 907c378. They should've been added to the derivations table in that commit. We should perhaps centralize our HTML generation.
This has an open TODO. We should implement it.
|
This existed, but was mistakenly removed in f9c7165, perhaps under the assumption that the use of `<div>` tags would render the line breaks unnecessary. It's necessary to have two line breaks, not just one, when the images are absent; in order for the horizontal line to avoid conflict with the "dictionary" division.
We would like to expand the Tidy config to the following:
NOTE: The Tidy config was set up as part of #213. |
The `word` class is now essential for highlighting.
The `word` class is now essential for highlighting.
Assign IDs and classes more extensively. Use more appropriate tags.
The text was updated successfully, but these errors were encountered: