Priority list

Launch checklist

• Make sure the photos on community + about are responsive
• Landing: (logos) replace CSS grayscale images with actual images (or use an SVG hack)
  • applies to hero images as well
• Logo: replace CMUNE
• Job listings
• play with yellow

Landing page

• Mailing list: actually accept signups
• Use cases: create a new image for 'connected devices'
• Use cases: test responsive layout with five elements

Docs

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

SQL to ReQL:

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

Discussions

• [Landing] Hero: What's a sensible way to add the GitHub + Twitter data to the hero? (look at Bootstrap and other projects)
• [Landing NTH] Features: Consider lightening + saturating the feature images, darkening the text -- (Slava's comments: darken the header)
• [Landing] Features: Review copy + links with Slava.
• [Landing] Scalability: The "Learn more" link should link to a documentation page. Which one makes the most sense? -- start your cluster
• [Landing] Community: What news items make the most sense to go here? (ideas: blog posts, events)
• [Landing] Community: "All news" needs to point to a specific link. Which one makes the most sense?
• [Site NTH] Support banner: Decide on the copy for the support banner.
• [Site] Footer: Design the footer layout.

---

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.)"

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."

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

Remaining content

• Should we link to the GitHub pages for examples, or include the examples back in the Jekyll build process?
• Add the jobs
  • _layout/jobs.html

Specific files:

• favicon.ico
• rss.xml

---

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)
• 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).

Community

• Redefine the community events illustration in terms of percentages (currently not responsive)

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

API:_

• Examine the DOM structure for oddities.
• Deprecate the JavaScript file that recreates headers.

Navigation:

• Decide on a new docs ontology
• Some docs don't use the JavaScript language permalink / cookie script -- some docs just use the alias field in YAML, and don't follow around with your language

YAML and Markdown:

• The js YAML flag should be removed from all documents (grep for fancybox).
• All documents should start using reference-style links.
• All document should be reflowed.
• Infoboxes need to be updated to the new version (no more HTML embeds)
• Rename the .api_command_illustration class for leading images.

Wufoo forms

• Update the CSS for the CLA:
  • /community/cla
  • /community/cla/thanks
• Update the CSS for Shirts for Stories:
  • /community/shirts-for-stories

---

Slava TODO

• 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)
• Get Mike a list of example apps you'd like to see.
• Write a post for the 2-minute "what is rethinkdb" video and alias it