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
center, e.g. to add LibreOffice versions, categories, licenses. The
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
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
files (for each public release).
The release content type will contain the information about the
and all extensions files of that release with the information about
license and appropriate platform. I had to add about 5 or 6 file
to the release content type.
It would be possible to add some more information to each content
e.g. install instructions, legal information for users, images
Does this structure sound more user friendly? Feedback? Additions?
## Developer LibreOffice
## Freie Office-Suite für Linux, Mac, Windows
## Support the Document Foundation (http://documentfoundation.org)
## Meine Seite: http://www.amantke.de
To unsubscribe e-mail to: email@example.com
Posting guidelines + more:
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be