Sitemanager

Hello Andreas,

currently there is a completly different approach.

In WEC the TS can be changed - if i remember right?

The templates for sitemgr are stored as template (css/img/conf).
Changing the template just causes to write a special screen.css in the folder you specified as user folder and change the ts.

f.e. user folder: fileadmin/_special/users/

location of css file: fileadmin/_special/users/[uid of admin]/layout/screen.css

Additionally the tv templates can be changed based on the template.

I will think about a solution.
Anyway i think changing the TS is not a good solution for security reasons - my opinion.

Regards
Kay

The point is that WEC and also we develop lots of templates for all kind of sites which we could reuse and give to the people in a multisite.

It is right they can modify the TS but we could restict this and make .ts files not editable. Right now WEC is making them editable in fileadmin.

Another approach could be to load a custom CSS file after the skin has been loaded.

Benefit here would be that we could provide the skins in a global folder ie typo3conf/ext where it would be also easy to update skins i.e. if there is a security issue we need to take care of in TS.

Than the customer could load an own CSS file afterwards. This should be not to difficult to achieve as we would need to copy only the CSS folder to the customers directory instead of copying everything.

approach:
in typo3conf/ext/skin_myskin
with wec_config it is "copy skin_myskin to fileadmin/config/skins/skin_myskin

our approach would be similar but excluding files and folders (more like it is done in Magento
with a modified wec_config we "copy skin_myskin/css/* to fileadmin/customer/c###/config/skins/skin_myskin/css/ of course it needs to create the folders before copying if not existing.

Now the customer can access the CSS and do his modifications in here.

We also experiment with (t3xcscimp) - it would make all settings for fonts etc more or less obsolete. Have a look at!

Also we could think about using sassy and build some extension which manages the design, so customers only need to upload images or change values in a form instead of changing them direct in the CSS file. (sassify)

Sorry forgotten:

I am using a similar approach with templates created by our customers at http://dotemplate.com

Thierry Ruiz has build a great site and most html is standardized and therefore quite easy to integrate into the WEC system.
The customers create their own look they want to have with some simple clicks, than download the complete HTML as a zip and send it to us. We extract actually only the CSS and Images and upload them to a prepared template based on the WEC system but with all html namings from dotemplate and tada the template looks great and has lots of additional possibilities which the framework for templavoila offers to its users like those very flexible colums and modules etc - and of course the best TYPO3 tutorials in the Internet for Newbees like those people which will be users in these Multisites.

e.g. with:

http://typo3.org/extensions/repository/view/less/current/

Mhmm.
Is it possible to point out your filestructure as an image / screenshot?

The token replacement is already implemented in the template selector of ks_sitemgr ;)

Why aren't you using standard folders like the user or group folder?
Having all the customers directly in fileadmin is not very structured for me :( - just a thought.

Otherwise the admin can assign special rights if it's a normal filemount.

Regards
Kay

What is skin_newskin? - Is it an extension? - can't find it in TER...
Or do you mean the function in sitemgr?

I don't know wether sass or less is better. But i just found no sass php library :( - and i've no time to do it on my own :(

If there is any php solution for sass i would prefer sass over less, as extjs4 is completly skinned with sass - so there is already some knowledge about sass in the community.

Perhaps we can do a telephone conference after i left the hospital? ;)

I will concentrate the refactoring on the other modules and will do the template module as the last one.

PS: please add the used wec_extensions which concentrate on skins to the wiki of sitemgr ;)

regards
Kay

http://code.google.com/p/phamlp/

Ah ok Kay

http://goo.gl/yyVE6

In TER are lots of skins

less/sass this is why I suggest we ask the devs from WEC and try to do bundle the energy.
http://code.google.com/p/phamlp/
http://sass-lang.com/

OK you found it :-)

wec_config and framework_templavoila is needed

=======================

Here the already existing skins (Template Extensions) for TV

Skins by WEC ("")
skin_warehouse (CSS3)
skin_cityscape
skin_touchofelegance
skin_wireframe
skin_lilypads (CSS3)
skin_meadow
skin_weatheredwood
skin_stacks
skin_regal
skin_sketchbook
skin_brushstrokes
skin_lightsout
skin_bifold

Skins by DT3 ("DT3")
skin_dt3

Skins by BUSY NOGGIN ("BN")
skin_bn_white_wireframe
skin_bn_t_bone_starter
i.e. check out the busy noggin examples http://templavoila.busynoggin.com/

Skins by LisAndi ThaiPo3 ("ABC")
skin_abc_kik_red
i.e. used by Kirchenmusik Hochschule Rottenburg

To use the full power you would need also

wec_config
this is the extension to modify the settings and switch the templates

if you want to use an template switcher in the frontend you can use this one here:
http://svn.webempoweredchurch.org/projects/template-extensions/repository (skinpreview - not in TER!)
This is very usefull to setup your own demo website with all your customized templates to show to customers.
i.e.
http://demo.webempoweredchurch.org
http://t3pack.com

http://svn.webempoweredchurch.org/projects/template-extensions/repository
here you also find the source for the
templavoila_framework

and the
wec_styles
(which I recommend to customize to your needs by the way!)

in
wec_contentelements
http://svn.webempoweredchurch.org/projects/contentelements/repository
you find also an API to add your own content elements easily!

Please name all your skins starting with "skin_ks_***" which makes it easier to find the extensions
and in the description start them with: "TV Framework Skin: KS ......."

Thanks

Andi

hi andi,

through usability reasons the functionality of wec_config needs to be integrated into the sitemgr - otherwise there too much modules :(

I added an API to add more Tabs (lateron with a sort priority to ensure, that they are e.g. added before the help tab).
Additionally the sitemgr will work with the new CardLayout in the future, which was added in 4.6 (by me).

*Are you one of the developers of wec_config or templavoila_framework? *
Regards
Kay

Hi Kay

No I am not a developer of WEC :-( but I am using their stuff since 2004 and promoting theirs to as I like it very much (very usable and easy to use stuff and best documentations)

As far as I know they have added the possibility to do additional tabs in wec_config already.
In 2006 I had done the same like you and integrated wec_config into abc_config as the functionality wasn't and especially the sorting of the items wasn't what I thought is usable.
It actually it does not matter to integrate it into another extension.
Downthing is to maintain two extensions.
It would be good to keep the compatibility to WEc as those churches would be also a big potential client for the sitemanager ;-)

Thanks for your work

Andi

It would be good to keep the compatibility to WEc as those churches would be also a big potential client for the sitemanager ;-)

That's why i seperated the UI functions into seperate extensions as the first step of refactoring:

• EXT:sitemgr
  • base module
  • pure customer and user management
  • basic help module
• EXT:sitemgr_template
  • additional templating / layout tab for the sitemgr
• EXT:sitemgr_personal
  • better fe_user management (based on tt_adress and others)
  • add fields to fe_users->tt_adress needed in the german redcross

This way you can install the WEC TOOLS paralell and use them without sideeffects and you're able to decide what you wanna use ;)

Hi Kay this looks great

I think I meant "websites" and not "screens" as it would not make sense what I said there. haha!

One suggestion:

The templates "folders" are actually also "Extension Folders"

BUT if you install a skin as extension than the entries in localconf.php get very long and not really usable.
On the other hand every skin which resides in Fileadmin can be installed to with wec_config, so there is actually no need to put them inside the extension folder!

What about setting up a SKIN Folder typo3conf/skins/.... where all those skins which we will create in future will be placed. Those skins won't get installed as extensions in the extension folder but as skins in the skin folder - BUT they are still extensions as this is very usable and we would have backward compatibility for those who install them still as extension ;-)

Instead of installing afterwards a skin extension all skins placed in the skin folder get displayed in the sitemanager as a skin in the repository (This repository could even be a global repository on TYPO3.org IMHO.) Than the users choose a skin and use it (one way without modifications) or they want to modify a skin and therefor download it (copy it) to there private "fileadmin" folder (/user/c000/config/skins/....) The same skins could be loaded into a Group skin folder for those Institutions who need a CI and only provide specific templates for their customers (i.e. classes in a school or even students of a class or ministries of churches / departments of companies etc)

The localconf.php would stay clean without the skin stuff inside!

We checked the images you provided an they look much much better already than what has been provided by WEC. Great idea to display stuff in a lightbox and in a Grid. Good would even the possibility to sort the Templates by categories.

A TYPO3 Skin repository which would be actually a second Skin TER - as all Skins could be distributed still as skinns - could have the ability to search by categories or tags. This functionality in the backend would give users a very fast way to find a nice looking template for their sites - In the lightbox could appear i.e. informations like:

Image of the template - link to the skin on the Skin Ter where they could see even more screenshots of aa skin or even a live example like on demo.webempoweredchurch.org

They would need the name of the skin, perhaps som registration number (uid), the date of first upload and updates i.e. like onTER.
Than the compatibility Versions, and dependencies as some skins might needadditional extensions to be installed.

To install an extension you click on "use skin" and to make a backup or to modify a skin you could also click "copy skin" like it is already done in wec_config.

We are currently working on a skin which can be used at the same time on web / ipad / iphone (mobiles) each horizontal and vertical. we are using the laker Framework idea for this whith which we hope to export i.e. also Pages as iPhone eBooks lateron. A very usefull feature i.e. for schools which would need a way for the students to take their work home.

http://www.lakercompendium.com/
http://www.engageinteractive.co.uk/blog/2008/06/19/tutorial-building-a-website-for-the-iphone/
http://lessframework.com/
http://bakerframework.com/

we opened up another project for this on forge too called TYPO3 Mobile (mobi) with several subextensions to fit this purpose.

We think we could combine lots of this effort into creating a multipurpose HTML5 Skins based on the Ron Hull Framework.

@Kay
Could you please add our main developer Champ (czkaza) to this project which would be very helpful or let us know how to do so that he can join! Thanks

hi andreas,

i've added your main developer ;) - mail just got automatically dropped as spam :(

i moved the 2 questions to a seperated forum here on forge (would like to discuss that there):

1. Skin Location (typo3conf/ext or typo3conf/skins)
http://forge.typo3.org/boards/6/topics/3
2. Skin Ter
http://forge.typo3.org/boards/6/topics/4

Or Simply Boards -> Developers ;)

I think we need to devide that two topics from the basic issue or it will be to complex to handle, or things are simply forgotten.

Regards
Kay

no feedback at all?

Hi Kay

I was out the weekend and just came back and realized that the iPhone is not able to display the TYPO3 backend. anyway!

Yes your suggestion is good we should split it as those are two separate issues.

but what do you mean with Boards and Developers.

We could setup a discussion Forum if you mean this - yep. Perhaps better than Issues as the extension sitemgr would not make a skin TER ;-)

This is something actually what we can plan as far as possible but what has to be integrated into the TYPO3.org website or we would need to set it up at another location i.e. WEC as they already have most templates available and serve the skin directory from there. With the new extension manager this should be not to difficult to manage. already all skins get stored under the category skins.

Hi,

sry, for inconvience :(

Scroll to top use the Forum link in the horinzontal tab like nav bar and than choose the developer forum ;) - that's what i meant.

1. Skin Location (typo3conf/ext or typo3conf/skins)
http://forge.typo3.org/boards/6/topics/3
2. Skin Ter
http://forge.typo3.org/boards/6/topics/4

Thanks for your Feedback
Kay