Developer forum

Hi Nicolai,

I really welcome that idea!

The following ideas come to mind:

1. English defaults in all templates. No Danish text even if it's just a placeholder. This also applies to keys in Translation files. E.g.:
@Translate(name, "Name")
instead of
@Translate(name, "Navn")

2. No unnecessary code, such as javascript pseudo protocols on click handlers. E.g.:
onclick="document.getElementById('whatever').submit();"
instead of
onclick="javascript_document.getElementById('whatever').submit();"

3. Better looking presentation. Ideally, all templates use the design used for the eCommerce Demo web site. That way, we get a good looking web site by default. This should also be applied to templates for eCommerce so we get nice carts and customer details screens out of the box, and not the ugly ones we have now.

4. No language="javascript" on <script /> elements

5. Better or more examples in XSLT templates. This is especially true for eCommerce navigation.

6. A cleanup of module templates which are no longer supported. Do we still really need a CustomerCareCenter folder under eCommerce?

7. Fewer templates. I never quite understood why we have Login_dk.html and Login_uk.html in Extranet for example.

8. I was going to enter jQuery here as well, but I realize not everyone uses that. I much prefer:
onclick="$('#whatever').submit();"

over

onclick="document.getElementById('whatever').submit();"

or even dynamic setups of the handlers, but that would force one to use jQuery. Could be a good thing tough.... ;-)

9. A fix of the Dynamicweb design / layout, so templates such as TextBottom-ImageTop.html really have the text at the bottom and the image on top.....

Imar

 

Just noticed the (and default configuration) which creates room for more ideas.

For the eCommerce module, I would really love a Setup wizard.

I realize it can be hard to define suitable defaults for everyone. I want euros as the default currency, but you may want Kroner. Same goes for countries and languages and so on.

A setup wizard, that can be run on a new installation, would guide me through the process of setting up a new site, enabling me to enter countries, currencies, languages, what have you. At the end of the wizard the changes are saved to the database so I can start using the system right away without messing with Kroner and Grupp1.

I believe something like this already exists for the eCommerce Light module but I've never been able to find it.

Kind regards,

Imar

Hi Nicolai,

I also welcome that ideia, in fact over here in Portugal we have implemented it with our own.

We have a combination for default templates in terms of:
 - paragraph (clean, valid, easy and proper css structure)
 - menus (clean, valid, easy and proper css structure - even language menus with a specific rule)
 - dataManagement forms with full javascript, email validation, translation tags and multiple columns (some rules and no javascript for the columns just html and css)
(our set of paragraph templates allow for easy selection in css/javascript of all paragraphs, or in a specific placeholder or even by type - I can send them to you for analyses if you like)

I also agree with Imar on basically all subjects. I would like to add
 - templates should be able to work in more than one paragraph at a time (for example, the gallery module, flipbook, does not allow for this) - this is also an alert to using id's because of validation issues
- eCom navigation examples. we have a lot of issues with this because of level conflicts
- quick newsletter subscribe newsletter - just e-mail and name
- valid e-mail templates with css (recover password, send confirmation, newsletter)
- month calendar templates for Calendar module - we have one solution but it's rather messy - I can also send it to you for some ideas

Nuno

Hi Nuno and Imar

Thanks for the input.

@Nuno: I would very much like your paragraph and datalist templates. Thanks - much appreciated.

Hi Nicolai,

Sent them to you e-mail.

A few more things that i noticed:
- the newsletter standard template is missing @ParagraphID in the onsubmit of the form
- upon sent recovery password, the system places a javascript alert hardcoded. we should be able to control this information
- the noEvents tag in calendar forces a table structure :S
- clean up of news item templates (the major 4 are usually enough - imageTop, imageBottom, imageLeft, imageRight)

Nuno

 Hi,
I would love it if
- You included XSLT versions too.
- You included example XML output from each module.
- Put the name of the template at the top, commented out including a path to where to find it
- Used "generic" class names for things like "item", "list" adding a container at the top stating the relation - for instance: "news". So in the CSS you might address an item like this: .news .item
- Had versions with and without use of if-defined
- Put some efford into using simpel, standard template names.

Oh, and perhaps HTML5 based templates :-) (prefixed with HTML5)
And for the XSLT templates, why not make a new standard where the user adds "debugxml=true" which will make a copy of the XML into a textarea. I do it on every XSLT template I make, as I find it quicker that the "savexml" parameter.

/Sten Hougaard

Another area where I would love to see some improvements is Extranet. Specifically, I would love to see better templates for:

1. Sign in - with a well-behaving "Remember me" checkbox just as the rest of the world uses and proper error messages.

2. Sign up with error messages for duplicate user names etc

3. Forgot password on a separate page

I would like to see these templates and functionality behave more like the ASP.NET Login controls op.

Imar