r1 - 28 Jun 2007 - 19:46:35 - SheilaMooneyYou are here: OSAF >  Journal Web  >  ContributorNotes > SheilaMooneyNotes > GettingStartedGuideDiscussion20070628

Preview Getting Started User Guide Discussion

Attendees: Pieter, Mimi, Katie, Sheila

Agenda

  • Review Pieter's plan for the Getting Started Guide - talk about specific content and sections

Notes

  • Basis for list of things Pieter has compiled so far
    • Feature discussions with Mimi - Top ten things that are interesting
    • How to...
      • Install
      • Setup accounts
      • Share
    • Editing in detail view and adding updates
    • Each chapter is about 1-2 pages
    • Use screenshots, callouts
    • Get the highlights of what you can do with Chandler
    • Understand the state of the application
    • Beginnings of a user manual
    • Import/export
    • Bookmarkable URLs
    • Clear documentation - if I am using Google calendar, how do I get my information into Chandler

Chapter Review

I omitted the chapter numbers since we are trying to figure out if they are the right ones or not. I will simply identify that there is a chapter devoted to this topic.

  • Chapter: Glossary - Chandler terminology and icon definition
    • Sidebar, triage status etc
  • Chapter: Download and install
    • New user section and a migration section
  • Chapter: Setting up accounts
    • Sharing, email and password protection
    • Tell them how to setup email and point to more lengthy explanation in subsequent sections
  • Importing data and exporting
    • Address what we are focusing on for Preview - importing static data - not synching
    • Details around iCal and Outlook and other clients need to be on the wiki not in this document
    • Point to the main wiki page or some page which specifically talks about this client
    • We don't need to resolve whether or not this is one page or several pages for now - we will continue the wiki work and figure that out
    • Mimi - separate out email as a separate chapter and talk about what it means to download mail and setup the special folders. How this works.
    • Separate chapter vs separate section in the email chapter. Probably a separate chapter is better.
  • Chapter: Sharing collections from Chandler
  • Chapter: Collaborating with others - flexible and allows you to share with others, they may or may not be using Chandler
    • Mimi - in the vision document we do not differentiate between collaborating with Chandler or non-Chandler users
    • Conflate Ch 5,6,7 from Pieter's original document
    • Talk about them in sections
    • Do we want to talk about other CALDAV servers and other CALDAV clients - No, not in too much detail in this document
    • Could mention that we interop with CALDAV standards - link to wiki page. We will come back to this later.
    • We are not going to talk about running your own Chandler Server * Chapter: Triage workflow and stamping * Managing, processing, organizing - 3 diff information management workflows * Mimi can send Pieter the latest draft of the vision document so we can structure it similarly * Suggestion: We have two chapters on collaboration * Collection level vs item level * Item level collaboration can address edit/update workflows * Chapter: Troubleshooting * Backup, dump files, troubleshooting issues * Linking to known bug pages when they are finished * We could also link to the FAQs
  • Conflict management goes under collaboration chapter - make sure we add screen shots of the conflct UI dialog
  • Bunch of misc features - we could have a couple of paragraphs about this stuff * Minical/preview area * Overlays * Timezones * Tools menu * Demo menu * Pluggins (just one section) * All-day and anytime events (and @time events) * Alarms
  • We could have a calendaring chapter that addresses most of the stuff listed above
  • Tools menu * Future features we are hacking on but aren't done * Tools for testing * Tools for debugging * Not really something we want to focus on prominently - experiment at own risk * Decision: Table the tools menu - just stick with a caveat statement and we could put it in the
  • We could have a specific chapter for listing out all the other menus
  • Visual syntax for icons - goes in glossary (pieter can find this info in the stamping spec)
  • Define behavior around mine/not mine in collaboration chapters
  • Do we want to use HTML for the quick start guide vs on the wiki * This sounds fine

Screencasts

  • More work to do screencasts than narrative with screenshots
  • Pick something small or some example workflow
  • Focus on quick start guide first and wait on screencasts
  • The guide is more important than the screen casts and we should do this first
  • Not a requirement for Preview

Next actions

  • Sheila send out notes to the list
  • Pieter redraft chapter structure and work on wiki page we could send out to the users list
  • Pieter to meet with Philippe

-- SheilaMooney - 29 Jun 2007

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.