Difference between revisions of "Website core"
| Line 1: | Line 1: | ||
| + | What are the priorities of the system? What needs does it have to address first? What we have to do and what is secondary? What is best done by a blog or a wiki and what needs specific development? | ||
| + | |||
== Image module == | == Image module == | ||
| Line 22: | Line 24: | ||
guests -> replace by participants | guests -> replace by participants | ||
| + | |||
| + | |||
| + | == Project(+event+series+programme) module == | ||
| + | |||
| + | deals with the structure of the events, needs to be broken into subchapters. | ||
| + | |||
| + | |||
| + | == Sound module == | ||
| + | |||
| + | storage and indexation of sounds, recordings, archives, etc. possibly generates streaming. | ||
| + | |||
| + | |||
| + | == Text module == | ||
| + | |||
| + | from writing/versioning to publishing of text + pdf export | ||
| + | |||
| + | |||
| + | |||
| + | == Services == | ||
| + | |||
| + | the services are components that give generic functionalities for the modules. ie, every module will need translation, permission, etc. | ||
| + | |||
| + | |||
| + | == Permission == | ||
to accomodate more users/writers/collaborators, the permission system needs to be adapted | to accomodate more users/writers/collaborators, the permission system needs to be adapted | ||
* who has access to what? we need to think of scenarios for that | * who has access to what? we need to think of scenarios for that | ||
| + | |||
| + | |||
| + | == Translation == | ||
language + translations | language + translations | ||
* at the moment, the amount of languages in which a post is possibly translated is hardcoded and multipl ways of dealing with translations are in place -> homogeneity needed. what are our needs in term of translations? | * at the moment, the amount of languages in which a post is possibly translated is hardcoded and multipl ways of dealing with translations are in place -> homogeneity needed. what are our needs in term of translations? | ||
| − | + | ||
| + | == Metadata == | ||
| + | |||
| + | link content to taxonomies, tags, keywords. | ||
Revision as of 14:02, 14 December 2005
What are the priorities of the system? What needs does it have to address first? What we have to do and what is secondary? What is best done by a blog or a wiki and what needs specific development?
Contents
Image module
The image module provides a handy way to store images to include as illustrations in articles via a web interface. It is by no means a replacement for the image gallery
function:
upload / resize / generate html code for images
permissions:
image module is contextual. If user is granted access for an event, s/he will have access to the image folder with the same rights.
modifs to existing module:
make one folder per programme/context, adapt to new permission scheme, multilingual?
Guests/participants module
guests -> replace by participants
Project(+event+series+programme) module
deals with the structure of the events, needs to be broken into subchapters.
Sound module
storage and indexation of sounds, recordings, archives, etc. possibly generates streaming.
Text module
from writing/versioning to publishing of text + pdf export
Services
the services are components that give generic functionalities for the modules. ie, every module will need translation, permission, etc.
Permission
to accomodate more users/writers/collaborators, the permission system needs to be adapted
- who has access to what? we need to think of scenarios for that
Translation
language + translations
- at the moment, the amount of languages in which a post is possibly translated is hardcoded and multipl ways of dealing with translations are in place -> homogeneity needed. what are our needs in term of translations?
Metadata
link content to taxonomies, tags, keywords.
