Drumbeat/website/project page details

From MozillaWiki
Jump to: navigation, search

Project Page: Context & Strategy

  • The Project Pages are the most important -- and difficult -- pages in the entire site. In some ways, they're the whole reason for building Drumbeat!
  • Balancing internal vs. external tools & functionality is key. This is the most important part to get right -- striking a balance between internal Drumbeat infrastructure vs. leveraging external infrastructure and third-party tools & social networks. As a general rule, we want to:
    • Allow people to EMBED or LINK to existing third-party tools & resources where they want to (e.g., a project blog, wiki, discussion forum, etc.)
    • Offer our own Drumbeat-hosted tools and functionality, if those external tools don't exists or if that's what the user prefers.
      • This Drumbeat-hosted functionality should be as "out of the box" as possible for phase one. We want to offer functionality and tools that are included natively in the Drumbeat Groups module.
  • Setting the bar at a flexible / adjustable height. We want to provide robust support & content for fleshed out projects -- but not in ways that set the bar too high for community-proposed projects.
  • Allow people to build and flesh out their page over time. Make the bar as low as possible to get started. Then encourage people to further flesh out their project page over time.


Project Tools & Content

  • "People working on this project"
  • Project Blog
    • Include "sticky at top of list"
  • Milestones
  • Calendar
  • Discussion threads / message board / forum
  • "Comments"
  • Twitter feed
  • Wiki
    • Internal
    • External
  • News articles / press coverage
  • Files
    • Internal
    • External
  • Links
    • Delicious
  • Image galleries
    • Internal
    • External
  • Video(s)
    • Internal
    • External
  • "Blog posts"
    • Internal
    • External
      • RSS / blog aggregator?
  • Facebook group
  • Messaging
    • Send message to project owner or participant (securely)
  • RSS feeds
  • "Free text field"
    • Should include ability to embed any HTML-enabled widget, etc. (consider security & legal implications)
  • Frequently Asked Questions
  • "Project Stats"
    • Number of collaborators
  • Skills needed / seeking?
    • e.g., developer, bloggers, engineers, storytellers, visualization expert, etc.
  • GitHub
    • David: How would this work?