User:Ricardo Vidal/workshed: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
Line 8: Line 8:
* Seamless layout that allows one to go from wiki to blog '''without''' too much graphic difference. Try not to make it look like the users are leaving OWW when reading a blog. (Ex: http://wiki.shift.pt/doku.php )
* Seamless layout that allows one to go from wiki to blog '''without''' too much graphic difference. Try not to make it look like the users are leaving OWW when reading a blog. (Ex: http://wiki.shift.pt/doku.php )
* [[OpenWetWare:Software/Ideas|Software ideas for blogs]]
* [[OpenWetWare:Software/Ideas|Software ideas for blogs]]
===Brand Management Considerations===
The following list has been copied from [http://www.brandingstrategyinsider.com/2008/02/key-brand-manag.html Branding Strategy Insider] (my comments in italic)
What are the most important considerations in brand management?
* Deeply understand the target customer
** ''This is a topic of discussion and related to the future "business model"''
* Promise one or two benefits that are unique, compelling and believable
**
* Capture your brand’s promise in a tagline or slogan
* Aggressively build awareness
* Deliver on the brand promise at each point of customer contact
* Market to your employees first – turn them into brand champions
* Present your brand’s identity accurately and consistently


==Outreach==
==Outreach==

Revision as of 19:26, 9 March 2008

Misc projects

Assorted ideas/notes

  • Hover notes thingy like Flickr (extension) - This would allow one to add notes to images without actually altering the original file.
  • Seamless layout that allows one to go from wiki to blog without too much graphic difference. Try not to make it look like the users are leaving OWW when reading a blog. (Ex: http://wiki.shift.pt/doku.php )
  • Software ideas for blogs

Brand Management Considerations

The following list has been copied from Branding Strategy Insider (my comments in italic) What are the most important considerations in brand management?

  • Deeply understand the target customer
    • This is a topic of discussion and related to the future "business model"
  • Promise one or two benefits that are unique, compelling and believable
  • Capture your brand’s promise in a tagline or slogan
  • Aggressively build awareness
  • Deliver on the brand promise at each point of customer contact
  • Market to your employees first – turn them into brand champions
  • Present your brand’s identity accurately and consistently


Outreach

  • A small list of them could be compiled in a specialpage or tagged as "very interesting" and then displayed randomly to visitors of the site. I'm sure they'd become greatly used.

Organizing OWW

This is a list of steps that I consider essential to make OWW better organized and easier to use.

  • A new set of tutorials for new/recent users. These tutorials should be step-based and when possible accompanied by screencasts (videos).
    • Hierarchical pages - this is very important to keep the wiki organized. Many new users place their pages in the wrong place.
  • Forms to kick-start pages. These forms can be implemented on a page-type basis. If creating a protocol page, the form would show fields for material, methods, notes, etc. These forms would only appear on first edit.
  • Setup a page (community page, activity page, features page) that will concentrate featured and active pages on the wiki. This page depends on the creation of new functions/extensions that allow to create and follow such activity.
    • Vote page up/down (à lá Digg)
    • Lab Notebook Milestone marker (feature a project's status)
    • Latest users & Map with location (this is easier if country and city are made compulsory on sign up)
  • Focus on outreach by creating some plugins/widgets for blogs and other sites to display related OWW pages (ie Google Adsense). Also get a page together with all the buttons and banners available with code for easy insertion in html.
    • Edit count top 10 (activity != interesting --> logs, order pages, etc)