[TYPO3-50-general] Concept for BE functionality/interface
Franz Koch
typo.removeformessage at fx-graefix.de
Tue Nov 13 11:59:13 CET 2007
Hi,
as much as I have understood, BE and FE are technically the same and the
BE itself will be just a different view/template. But what about the
special functions needed for the BE. Will they be part of the general
presentation layer or be components?
Besides of that, is there already a concept for the functionality
provided in the backend, like which wizards and tools (create page
wizard, create content wizard, select template wizard, breadcrumb
navigation, sidebar,widgets,...)?
I'm asking, because this features should not only be decided by devs,
but also by the HCI team. So a coordination of that would be necessary
(if not done already - but haven't found something specific). And it has
to be started quite early with this - because good concepts and layouts
need to grow.
There would have to be created a overall concept for the backend - and
that BEFORE the functionality is coded. 'Form follows function' is not
the correct way to go for usability. First there has to be created the
concept, based on layouts that show how the BE might look like, and then
you will see, which features will have to be coded to achieve this. Of
course you can also go the other way around, but then you will have to
do things twice, changes here and there and finally some useful concepts
might be dropped.
Just my 2 cent.
--
Kind regards,
Franz
More information about the TYPO3-project-5_0-general
mailing list