Jan 142012
 
  1. LXS36C: In http://2.loverules.info/wp-admin/options-general.php
    1. LXS36X: Site title
      1. LXS58M: fr=Temporary home for JotHere.com content
      2. LXS5AV: to=JotHere.com –Got a thought? Jot it here!™ (in <a href=”alpha”>alpha</a>)
        -didn’t work as the HTML wasn’t interpreted
      3. LXS5BE: to=JotHere.com –Got a thought? Jot it here!™ (in <a href=”alpha”>alpha</a>)
      4. LXS5BV: to=1.JotHere.com –Got a thought? Jot it here!™ (version 0.5)
      5. LXS5CJ: to=1.JotHere.com version 0.5  –Got a thought? Jot it here!™
      6. LXS5CU: to=1.JotHere.com version 0.5   –Got a thought? Jot it here!™
      7. LXS5D8: to=1.JotHere.com v0.5  —Got a thought? Jot it here!™
      8. LXS5DQ: to=1.JotHere.com version 0.5   –Got a thought? Jot it here!™
      9. LXS5E5: to=1.JotHere.com version 0.5  –Got a thought? Jot it here!™
      10. LXS6M4: to=1.JotHere.com version 0.5  –Got a thought? Jot it Here!™
      11. LXS5IP: Some reasonings:
        1. LXS5IS: include subdomain “1.” as that is technically correct and (allows tagline be specific to it, saying “via WordPress & its best extensions” instead of “via WordPress & more”)
        2. LXS5N5: add version info because it’s
          1. LXS5R3: technically correct
          2. LXS5RA: consistent with post versions
          3. LXS5RG: will show progress simply as it’s incremented even a small amount
          4. LXS5RN: it (or alpha/beta) is important to feature when in early stages
          5. LXS5RT: it’s shorter, more familiar, and more exact than saying “(alpha|beta)-test”
        3. LXS5SU: Spell out “version ” instead of say “ver” or “v” as
          1. LXS5TX: important to emphasize when version is less than <1
          2. LXS5V3: more familiar than “v” or “ver”, especially important when site is new as it is.
        4. LXS5WH: space name from slogan with html[ &nbsp;] as hmtl[ ] gets collapsed.
        5. LXS5LN: add slogan “–Got a thought? Jot it here!™” because it’s cute, memorable, appropriate, & explains domain name, and already in use for ~1yr on business card.
    2. LXS3A7: tagline
      1. LXS5AM: fr=–for user content on any topic
      2. LXS5B3: to=–a next-gen wiki for user content on any topic in <a href=”alpha”>alpha</a>
        -didn’t work as the HTML wasn’t interpreted
      3. LXS5BM: to=—a next-generation wiki, via WordPress & more, for user content on any topic
      4. LXS5CD: to=—a next-generation wiki for user content on any topic, via WordPress & its best extensions
      5. LXS5CO: to=—a next-generation wiki for user content on any topic, via WordPress & its best extensions
      6. LXS5D0: to=—for user content on any topic: a next-generation wiki via WordPress & its best extensions
      7. LXS5DN: to=—for your content on any topic: a free next-generation wiki via WordPress & its best extensions
      8. LXS5DW: to=—for your writings on any topic: a free next-generation wiki via WordPress & its best extensions
      9. LXS8JZ: to=—for your writings on any topic:  a free next-generation wiki via WordPress & its best extensions
      10. LXS5ZF: Some reasonings:
        1. LXS5ZY: put “—” instead of “–” as it’s appropriate & expected & reads better.
        2. LXS617: put “for your writings on any topic” first as
          1. LXS62Q: it conceptually matches the just-prior slogan.
          2. LXS63H: it gives the subject in the most familiar wording before (then) getting into the technical details.
        3. LXS65G: use “your” instead of “user” as it’s
          1. LXS69X: more accurate (open to all)
          2. LXS6A0: more familiar
          3. LXS6AE: much more inviting
        4. LXS66M: use “writings” instead of “content” as its
          1. LXS6AL: more accurate as we do have notably good support for publishing writings, but not notably for other media types as pictures & audio & video.
          2. LXS6CJ: much more familiar
          3. LXS6D4: more inviting
        5. LXS6E0: add “free” as this quite true & quite important & quite inviting.
        6. LXS6FV: add “next-generation wiki” as
          1. LXS6I0: it’s increasingly accurate as
            1. LXS6ZA: does full post versioning
            2. LXS6ZM: already has HTML instead of wiki-script
            3. LXS6ZZ: as all wiki have, to (very soon) be general multi-user edit when security enhanced
            4. LXS702: many more pivotal enhancements coming.
        7. LXS70W: add “via WordPress” as
          1. LXS7QZ: a big confidence builder given WordPress is the #1 user-made Web 2.0 site and open-source, and steadily increasing popularity from 2004 to 2011Q1.
          2. LXS7PV: very true & appropriate
          3. LXS7Q7 difficult/impossible to hide
        8. LXS7RS: add “& its best extensions” as
          1. LXS7SO: true & appropriate
          2. LXS7TK: compliments the extensions.
          3. LXS7U2: accurately suggests the high standards.
    3. LXS7VF: Date format
      1. LXS7WV: fr=January 14, 2012
      2. LXS7WZ: to=TY.m.dD=PST2012.01.14Sat
      3. per=Documentation on date and time formatting.
      4. as=this is new date standard I’m using (except timezone should be in lower-case but that option isn’t given)
    4. LXS872: Time format
      1. LXS87G: fr=g:i a=12:32 am
      2. LXS8OR: to=Hi=0141
        per & as as prior.
      3. LXS8OU: to=01:44
        as=more readable as time is being written by the theme “at 01:44” instead of appended to the date.

  3 Responses to “http://2.loverules.info/wp-admin/options-general.php: title & tagline & date-format: notably improve LXS32O”

  1. […] wp-utf8-excerpt is not creating fully-readable excerpts of many posts, including most recent as here, due to the fact that <sup> isn’t an […]

  2. […] on http://2.loverules.info/724  : page displays fine and refreshes in basically in 2 seconds and fully within 4, and […]

  3. Further tagline development