[TYPO3-hci] Less ways to do it...

[Ernesto Baschny [cron IT]]

Michael Scharkow schrieb am 22.05.2006 17:53:

> just a few thoughts about making common tasks easier to solve by
> *removing* stuff from the BE:

Yeah, I like the concept.

> 1. Remove page types completely (except for sysfolders, see #2), only
> keep page properties. See the various questions about not-in-menu
> pagetype *and* the property hidden-in-menu, or the question whether
> shortcuts can have subtitles, etc. Basically, we should only have pages
> that have certain properties, and those should be nicely arranged in a
> tabbed interface.

This seem to be already proposed several times now. See your own thread
"Less features, more future" in typo3-dev from oct-2005. :) I agree this
fits nicely in this newly created group.

> 2. Make a stricter distinction between pages and sysfolders. It has been
> a best-practice ever since, but it should be enforced strictly: Pages
> contain *only* content records and sysfolders contain all other records
> but no content records. Any ambiguity as to where store stuff should be
> removed.

Would be nice, but would break a lot of sites that rely on that (news
related to a specific sub-part of a site stored in the "start-page" of
that sub-part). A solution to migrate those sites would be to
"auto-create" SysFolders under each page that has non-content elements.
But this would also require template changes (uid's) and maybe even
extension changes.

> 3. If we follow #2, we can remove the distinction between list and page
> view: Pages default to page view and sysfolders to list view. no need
> for any other options if the functionality (=clipboard and sorting
> mostly) is there.

True, clipboard/copy&paste are some things that are not very reachable
in the Page-Module. But you would always need to keep functionality in
sync between TemplaVoila and "Modern" template building.

> 4. Remove the access module and put it into the page property dialogue
> where it belongs. It's a matter of debate whether we should have a
> "permissions" tab (only relating to BE users) and a "visibility" tab
> (only for FE stuff like start/stop/hidden/fe-group) or a mix of both
> (because a lot of users confuse this). I'd keep BE and FE stuff
> separated though.

Nice thing in the access module is that you can do (and see) stuff in
the whole page-tree at once (recursive).

> 5. Remove static templates and all related db tables and columns. They
> are obsolete and have been since 3.6.

Agreed.

And I would also try to find those things where "there is more than one
way to do it". The backend should not be like Perl. There are several
icons/buttons to edit "page properties", this is confusing to the users.

I think most things just need someone to "just do it". :)

Cheers,
Ernesto