diff --git a/README.md b/README.md index df6d9d7..e30f0fb 100644 --- a/README.md +++ b/README.md @@ -10,17 +10,17 @@ The generated HTML document must have a `
` tag with _at minimum_ the follo ```html - - - + + + +↔ > ```` -The `` for a link should be presented un-wrapped without any parent elements. Many implementations use `` or `` to enforce "block" styling as opposed to the default "inline" which renders the link next to the previous block instead of below it. But the nested markup adds an unnecessary layer of indirection in semantics. The best way to handle this is to include `` in the `
`. +- [ ] is the
required or desired? + +Much like the lines of a ``, the lines of `list items ` need to be wrapped in ``, indention here is not significant. Sometimes a list item is empty: `
- `. Empty lines should simply be represented as `
` this sets up `contenteditable=true` to add content to the line compared to just `
`. Take care to render `` blocks with their original formatting, DO NOT indent the generated HTML for these tags. -Much like the lines of a ``, the lines of `list items ` need to be wrapped in ``, indention here is not significant. Sometimes a list item is empty: `
- `. +- [ ] block vs inline elements + +The `` for a link should be presented un-wrapped without any parent elements. Many implementations use `
` or `` to enforce "block" styling as opposed to the default "inline" which renders the link next to the previous block instead of below it. But the nested markup adds an unnecessary layer of indirection in semantics. The best way to handle this is to include `` in the `
`. ### Optional: inline media +- [ ] what media can I inline? + If a link is consumable by ``, `