HunterThinks.com

Healthcare is a right

Posted: 30 November 2014
Updated: 16 December 2017

WordPress plug-ins: ideas for markup

  1. Soft hyphenate
  2. Auto add id attribute to all h1, h2, h3 elements (and maybe other customizable elements)
  3. Disable the [censored] automatic paragraph tags
  4. HTML validator
    1. Within the text editor
    2. Universal check of only the post and page content
    3. Check what each plug-in does to the pages
    4. Universal check and the ability to find which plug-in, theme, etc, inserted which tags
    5. Ability to view the HTML as it served to the agent and before it is rendered (i.e. before JavaScript converts elements and loads more junk so we can find code that breaks validation)
  5. Other validation tools
    1. Accessibility
  6. Semantic markup for foreign words
    1. Improves markup
    2. Could auto-link to translation dictionaries
    3. Could help with machine translation, including directing the translator to not translate that word
    4. Spellcheckers should have an option in addition to “Ignore” and “Add to dictionary” to “Mark as language…” Then the spellchecker should use the correct dictionary for spellchecking that particular word.
  7. When using classes, check to make sure that a linked style sheet defines the class. This can help prevent errors from misspelled classes on unlinked style sheets.
  8. Custom cursors, especially with semantic meaning and with classes
    1. Custom cursors, especially for a:hover
      1. External links show the external icon
      2. Section top cursor
      3. Website home cursor
      4. Contact cursor
      5. Help cursor
      6. Cursors for specific external links or actions, like Facebook “Like” icon
    2. When linking to non-HTML/XML content have an icon that tells the user
      1. Maybe also warn iOS users when a linked page depends on Flash content since they cannot see Flash
  9. Microdata
    1. Schema.org markup tool
      1. Sort of like “form autofill” in a web browser, have stored objects with all possible fields
      2. For each object, store the information that is known
      3. When writing, can highlight a term and scan the schema database for values that match the term, if one is found, can use a GUI to insert the necessary HTML
      4. Once a specific object is used on a page, it is available in a side panel on the editing page. Can select properties from the side panel. Can either checkmark for hidden property, or highlight text, then checkmark to associate the property with the text.
    2. Make a good microdata tool https://support.google.com/webmasters/answer/176035?hl=en&ref_topic=4600447

Pages tagged with:

, ,