Re: [libreoffice-website] LibreOffice Extensions-Site: Renovation

Hello Andreas,

I think Philipp has a point here. Mozilla came up with some very good 
designs and I think that one of the utmost priorities with the new 
extensions and templates site is to attract and appeal to users.

Best,

Charles.


Le 2014-02-12 12:05, Philipp Weissenbacher a écrit :
> Hey Andreas,
>
> Indeed, it does sound more user-friendly like that. I think that most
> people/extension developers would approach publishing an extension like
> that.
>
> I don't want to ruin your enthusiasm, but how about we adapt what 
> Mozilla
> has?
> Source: https://github.com/mozilla/zamboni or better
> https://github.com/mozilla/playdoh
>
> IMHO they already have a lot of features we'd also like, plus there's a
> shared maintenance cost.
> It's based on Django, however. So there'd be some learning curve to
> overcome. + extra load on the servers.
>
> Never mind the course we take, I'd be very much willing to help 
> implement
> it.
>
> Gruß,
> Philipp
> Op 11 feb. 2014 22:18 schreef "Andreas Mantke" <maand@gmx.de>:
>
> > Hello,
> >
> > after the feedback from Cor I thought of an alternative structure
> > (hierarchy) of the content types. It would be more flat.
> >
> > -- ExtensionsCenter (EC)
> > -- ExtensionsProject (EP)
> > -- ExtensionsRelease (ER)
> >
> > The EC will contain in the edit view form fields to customize the 
> > total
> > center, e.g. to add LibreOffice versions, categories, licenses. The 
> > view
> > will show a search form with result area, short search links etc.
> >
> > The contributor will have to create (or get) an account and start with 
> > a
> > project for each extension. There will be a edit form where he will be
> > asked for the necessary information about the extension project. The
> > view of the project will show information about the project, e.g.
> > category, description and maybe a form to send messages to the project
> > owner. There will also links to the releases and for the download of 
> > the
> > files (for each public release).
> >
> > The release content type will contain the information about the 
> > release
> > and all extensions files of that release with the information about
> > license and appropriate platform. I had to add about 5 or 6 file 
> > fields
> > to the release content type.
> >
> > It would be possible to add some more information to each content 
> > type,
> > e.g. install instructions, legal information for users, images
> > (screenshots, logos).
> >
> > Does this structure sound more user friendly? Feedback? Additions?
> >
> > Regards,
> > Andreas
> >
> > --
> > ## Developer LibreOffice
> > ## Freie Office-Suite für Linux, Mac, Windows
> > ## http://LibreOffice.org
> > ## Support the Document Foundation (http://documentfoundation.org)
> > ## Meine Seite: http://www.amantke.de
> >
> >
> > --
> > To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
> > Problems?
> > http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> > Posting guidelines + more: 
> > http://wiki.documentfoundation.org/Netiquette
> > List archive: http://listarchives.libreoffice.org/global/website/
> > All messages sent to this list will be publicly archived and cannot be
> > deleted

--
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted