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
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.