Re: [libreoffice-design] Topic for design team to investigate: Content hosting consolidation on ask.libreoffice.org

On Fri, Oct 12, 2018 at 11:28:08AM +0200, kainz.a wrote:
> for the basic UX there are still some ideas from the design team
> https://docs.google.com/document/d/12dbdmzi3dy5TwNsIao0MXZSnl7X4jMk5zKwy8Azeohg
> (sorry that it is on gdocs)

Commented.

> And please keep it simple.

Yes, please. That document is already exploring the rarest cornercases:

- Bookkeeping a bazillion entries of metadata shouldnt be an end to itself:
  The webpage should handle metadata about extensions, if there is a reasonable
  usecase for using it e.g. in a query. However even basic querying -- apart
  from maybe for tags -- is already an advanced feature that 99% of users wont
  use.
- If metadata is extracted for search and querying, it should be parsed from
  the extension itself and not manually entered (or even duplicated: most of
  the stuff is already in the extension itself)

> Define the different users and what they want.

99% of extensions are:
- single revision
- single author
- cross platform

That is the usecase we should optimize for. Adding features for the 1% other
extensions should not be done if it adds complexity for the majority of
uploaders.

So in fact, half of the features in the google doc should be moved aside for
really, really pinning down a simple workflow for those 99% of uploaders that
wrote some single revision StarBasic or Python extension on their own.

Best,

Bjoern

-- 
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/design/
Privacy Policy: https://www.documentfoundation.org/privacy