Currently the package summary/description is done using plain text, e.g.
Hiri is an email client for Office 365 / Exchange / outlook.com / msn.com / hotmail.com / live.com. Basically all the Microsoft Email services :) Hiri has full email, calendar and tasks functionality. Hiri is a subscription service but you do have 14 days free to try it to see if you like it. Visit www.hiri.com for more information.
Perhaps we could consider using markdown to allow nicer formatted text (e.g. bold, italics, lists, links, images etc). Markdown seems to be quite widely used (e.g. github).
Some issues if we do use markdown:
- Are we worried if we use hyperlinks that could be used to trick users? Note that a lot of software already makes valid URLs clickable (e.g. gnome-terminal).
- For backwards compatibility and for developers that don’t want to use it we probably should have a flag
description_formator similar to opt-in to using markdown.
- Use of images could be used to track people browsing the store - is that a problem?
- For clients that don’t / can’t display formatted text (e.g. command line) do we need an easy method of stripping the markdown out?