Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Site launch checklist #17

Open
7 of 35 tasks
elipousson opened this issue Mar 10, 2016 · 0 comments
Open
7 of 35 tasks

Site launch checklist #17

elipousson opened this issue Mar 10, 2016 · 0 comments

Comments

@elipousson
Copy link
Member

elipousson commented Mar 10, 2016

from the DataMade Site Launch Checklist

Framing / Call to Action

  • Make sure that the site has a clear call to action. This should not be 'hey look at this cool tool'. Rather, it should be a way for someone to engage in a meaningful way on the issue being presented.

Some examples:

  • Join a mailing list (which means you need to create one)
  • Attend an event
  • Share on Facebook/Twitter
  • Donate to a particular organization
  • Create a Tumblr for people to share interesting findings (if it's a data access site)

Web Search Indexing

  • If you have a staging site, tell the search engine robots not to index you with a robots.txt
  • Make sure you allow indexing when you are ready to launch.

Google Analytics

Note: If we change the URL at any point we may need to re-do or revise some of these tasks.

  • Create Google Analytics account
  • Hook up the GA Tracking Code (typically in our analytics_lib.js file)
  • Set up relevant Goals and Funnels
  • Set up Google Webmaster Tools
  • Verify site in Webmaster Tools with DNS TXT record
  • Link Webmaster Tools to Google Analytics

Sharing & Rich Snippets

  • Set up general meta tags
    • <meta name=“description”>
    • <meta name=“author”>
  • Set up Facebook meta tags & validate here
    • <meta property=“og:site_name”>
    • <meta property=“og:title”>
    • <meta property=“og:type”>
    • <meta property=“og:description”>
    • <meta property=“og:url”>
    • <meta property=“og:image”>
  • Set up Twitter meta tags & validate here
    • <meta name=“twitter:card”>
    • <meta name=“twitter:site”>
    • <meta name=“twitter:creator”>
    • <meta name=“twitter:description”> (note that this needs to be under 200 characters)
    • <meta name=“twitter:title”>
    • <meta name=“twitter:url”>
    • <meta name=“twitter:image:src”>
  • Create 2-5 meme images using Canva or a similar tool

Mobile Friendliness

Test on various mobile devices:

  • scrolling is easy
  • nav bar works
  • hoverable things are tappable
  • charts/maps look ok

Page Speed

Miscellaneous Polish

Load Testing

If your site relies on a database or server-side code, it should use caching and be load tested. If it's a static HTML or Jekyll site, you can skip this section.

Testing

  • Plan for a day of bugfixing. This day should happen after you have added the last features you plan on adding.

GitHub Readme

If the site is open source, make sure the Readme.md is complete and accurate.

Here's a few good examples:

The Readme should have the following sections:

  • Overview
  • Setup
  • Running locally
  • Team
  • Errors / Bugs
  • Pull Requests
  • Copyright and License

Outreach

  • Write up press release
  • Identify who will be the primary person of contact and make their info prominent on the website and all PR
  • Identify relevant media contacts to email
  • Identify relevant social news sites (reddit, listservs, slack channels)
  • Divide & conquer - send out the media blitz!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant