Priority list

Launch checklist

Discussions

• [Landing] Hero: What's a sensible way to add the GitHub + Twitter data to the hero? (look at Bootstrap and other projects)
• [Landing] Realtime intro: Should we speed up the realtime animation?
• [Landing] Use cases: review copy with Slava
• [Landing] Features: consider lightening + saturating the feature images, darkening the text
• [Landing] Features: review copy + links with Slava

General styles

• The monospace font isn't loaded from Google Web Fonts or Typekit, so it needs to be delivered properly.
• Lists within lists
• Lists: line-height should be 2.8rem (applies to both blog + docs, abstract it away)
• Lists: p tags in li tags have too much padding (e.g. 'Limitations') -- it should match the blog style (abstract it away)
• Blockquotes should use GitHub quote styles (border-left, grey bar, grey text). Example: /docs/rethinkdb-vs-mongodb (docs + blog)

Landing page

• Mailing list: actually accept signups
• Use cases: create a new image for 'connected devices'
• Use cases: test responsive layout with five elements
• Logos: Add a logo wall
• Features: Resize the feature images using CSS to match the draft @ahrugyt put together

Scalability:

• Make sure the "Learn more" link actually goes to docs (discussion: which doc makes the most sense to link to?)

Community:

• "All news" needs to link to a specific page (discussion: what page?)
• discussion: what should go in "latest news"? (ideas: blog posts, events, etc.)

Support banner

• discussion: decide on copy for the support banner

Footer

• Match the number of users on the landing page (100,000+)
• discussion: design the footer layout

Docs

General styles:

• Lists should be the same size as paragraphs, paragraphs should have a line-height of 3rem (matching the blog posts, abstract the styles away).
• Blockquotes should match the new blog blockquotes (github style) -- abstract them away

Images:

• Broken images:
  • Table joins
  • Administration tools
  • Secondary indexes
  • Sharding and replication
  • Failover
  • Secure your cluster article is huge
  • Deploying with a PaaS

Byline:

• The language switcher doesn't work well on a responsive site. It should be moved to a byline.
• The 'contribute or edit' should be moved to the byline
• discussion: We could add 'last updated on XXX' to the byline

Navigation:

• 'Full text search' links to the wrong article.
• Broken accordions (the nav-data may just need to be updated to match the docs include):
  • Limitations
  • Start a cluster
  • Data exploration -- shows up in two places (should only be in 'RethinkDB in Practice')
  • SQL to ReQL cheatsheet
• Sub-items need to be indented (e.g. example projects)

Index:

• discussion: design the docs index layout and copy

Quickstart:

• Infobox is broken, fix it.

Install (CentOS):

• Broken header

Install drivers:

• Clojure button is broken NOT OBSERVED
• All three drivers: Opening infobox is unattractive

Cookbook:

• Wufoo forms are broken (they're both open when the page loads, rather than hidden). Drop them, and replace them with an infobox asking to open an issue on GitHub.

Watts' comments:

A few multi-language articles go to the section index page that lets you choose languages, rather than jumping to the last selected or default language like the old site does. Ones I've noticed: 'Cookbook', 'RabbitMQ', 'Publish-Subscribe'

SQL to ReQL:

• The image is the wrong size
• Headers are malformed Markdown
• The table is so long, that the page may need to be redesigned, and it may require updating table styles pre-launch

Failover:

• Remove the title "About automatic failover"

API

• The blue of the "read more about this command" is a bit harsh -- it should match the blog style for 'read more' links

Blog

• Videos for release posts should link to YouTube for now, include an alias for previous video pages so they don't 404.
• Screenshots are broken on the RethinkDB vs. MongoDB article (pick the Data Explorer screenshot, crop it, and remove the others)

---

Remaining issues for triage

General styles

• Tables could be improved (background colors + fine-tune the padding). Example: /docs/comparison-tables
  • Watts suggests, "Tables might look better with slightly smaller fonts, and possibly with cells vertically aligned to the top rather than left to default centering. (See the "Technical comparison table" page.)"
• Should we consider making the font color darker? (example -- rethinkdb vs. mongodb article, compare the blockquotes on GitHub <-> paragraphs on GitHub with blockquotes on our site <-> paragraphs on our site).

Documentation

• Example apps needs a redesign.
• Watts says, "We might want to use a special table style for the SQL cheat sheet page to get more data visible to readers without scrolling. They're huge tables."
• Watts says, "The Troubleshooting page needs a TOC block but the {% toctag %} looks awkward there; we probably need to come up with a different style, possibly closer to the straightforward one we have on the current website."
• "Start RethinkDB at system startup" -- changed to match the article title, but it seems long.

Language switcher

• Language switcher seems like it's the wrong height.
• Should the language switcher be simplified?

Byline

• Should we style the contribute or edit box?

Footer

• discussion: tentative columns: product, documentation, community, services
• Can we add social channels to the footer?

Blog

Sidebar:

• Should 'share this item' go on the side, or at the bottom of the post?
• Should the RethinkDB + 'read more posts' boxes be swapped?
• Add RSS feed
• Add a link for RSS
• Mailing list should actually work

Support

• Example support site: GigaOM
• Color bands per section?
• discussion: sections for support: operational support, consulting, training

About

• Choose an image for the header
• Update typography on the secondary nav
• Intro image (400x400): should it be a photo or illustration?
• People boxes: wider, GitHub profiles?
• People boxes: remove contributors?
• Try making the action item a callout bar
• Source for inspiration: Meteor's about page
• discussion: revise the wording for about to indicate the company's reliability
• Add a press kit (requested by Method)
• Consider dropping the People section

---

Post-launch checklist

General styles

• Buttons should transition more smoothly, consider not flashing the entire button
• Some pages don't need separate directories with index.md files (e.g. community & about)
• Add a fallback font in case Typekit is down (#52)

Videos

• All videos should load asynchronously and have an image swap (Google+ style).
• Play buttons should be added to thumbnails via CSS.
• Video modals should open to a fullscreen video on iPhone / Android, rather than popping the modal open
• YouTube videos should always use the HD option

Landing page

• Clean up the icons in the use cases section: the "web and mobile" icon is too busy

Site structure

• Sticky footer on short pages

Docs

Navigation:

• Decide on a new docs ontology

---

Slava TODO

• FAQ has to be written -- linked to from "Learn how it works" (landing page intro)
• Run final numbers on users (e.g. the "community section")
• Update the technical comparison tables
• Update the stability report
• discussion: consider rewriting the quickstart around realtime apps (at least add a section for feeds, and link to realtime examples)