1. rapid release culture at mozilla

    Congratulation to firefox team on the rapid release cycle at mozilla
    [http://blog.mozilla.com/futurereleases/2011/07/19/every-six-weeks/] . Recent comments in http://bit.ly/nJ5KVB and even the bug details:
    https://bugzilla.mozilla.org/show_bug.cgi?id=678775 is plain out of
    context. Here- http://pcworld.com/businesscenter/article/238412/firefox_numbering_debate_is_…

    Familiarity and user experience is very different through any context.
    Familiarity can never demand a great experience. Rapid release cycle is very much necessary to the present web
    development as adopted by all the browsers standards. I must
    congratulate the teams who can keep our experience clean.

    My concern towards a better version upgrade and content strategy. The content should find relevance always. A
    prompt to the previous/latest release may (not) be a pertinent
    solution in this context. This case study suggests an “offline and
    delay” strategy, based on the user ‘preference’ / setting.

    Any notification prompt should be avoided,
    considering the annoying feature towards explicit user notification or
    install prompts. It rarely holds any relevance in this context. Suggestion-

    “Version” details provides same context as ‘about’ menu. A separate
    element invite the user to check the details. Elements-

    1. Offline session doesn’t hold the ‘version’ element in the menu.
    2. Settings > preference should hold the user immediacy status(twin state).
    3. And you knock only once for Online users i.e on release day. I have prioritized the notification without any urgency notices.

  2. content first out of the bag

    Within any context; content is the first focus of attention;
    Content is king. Kristen halvorsan’s ‘content first’ strategy at AEA2011 event in minneapolis burned a hole in the design community. Really.. @zeldman: There it is again! @Malarkey just cited a “Content First” approach. #aea / Notes of the talk are available in LukeW design/ideation blog:: http://lukew.com/ff/entry.asp?1372

    Kristem’s ‘content first’ approach against LukeW ‘mobile first’ is celebrated @halvorson: Content should serve the user wherever they are, no matter the context or device. It’s not mobile first. It’s content first.- @beep #aea /

    @zeldman: “Content first” is not “copy first.” @halvorson #aea / further I really need some more explanation..
    @happycog: A content strategy model from @halvorson: substance, structure, (content components), workflow and governance (depending on people). #aea

    Most shout- out to content strategist to focus the integral part of any design process. Rule of web content strategy: “Get the writer in the room early and empower her, because she can help you.” @halvorson #aea

    Minneapolis office of BrainTraffic content-strategy apprentice role is up for grabs. For cakes and more http:// braintraffic.com/jobs/content-strategy-apprentice.html