It’s april’s fool day, so I thought it would be nice to come up with some ‘blond’ feature requests. Perhaps some are already listed or planned for a later release, if that’s the case, my apology for double posting.
Fix browser editing before adding new features.
Currently, for me at least, Firefox proves to be the only stable browser that allows me to edit templates and pages. Both IE9 and Chrome sometimes have their quirks where placeholders don’t show up or drag-n-drop doesn’t work 100%. Having new stuff like Newsletters, Marketplace integration and stuff is great for us (developers/partners) but eventually we’re handing the project over to our clients. Telling them they have a state-of-the-art website that’s cross browser compatible, but they have to install an old FireFox version (v4 is out atm) to edit it, somehow doesn’t inspire confidence.
Sitefinity project configuration data.
The ability to store under ‘settings > advanced >Project’ custom data to allow for global project data be managed from a centralized and standardized location. In the form of a label and value field.
Most of us will have some best practices and methods of storing and retrieving some global parameters for a project. Some developers will use resources, others use web.config appsettings, others might load an xml file or load some sql table.
Instead of each developer having its own method and a wild grow of configuration classes, having a central repository and standardized way of storing this data will also benefit template exchange. In an accompanying file (or automated) we could just state declare these and these variables and template features would work.
I have a code snippet that automatically retrieves a ‘companyname’ and a ‘build-year’ which will automatically create the “Copyright ‘build-year’-current year ‘Company Name’. All rights reserved” in whatever language. Or take a GoogleMaps key as an example. Instead of storing the key on the pages that use it (and thus having to edit multi-places depending on internal/test/live site) we’d have a single and centralized place to store it.
Back-End template overview.
If you’d like developers to store custom Masterpages in ~/App_Data/WebsiteTemplates/MyTemplate/App_Master please be so kind and to change the “based on” column into something that doesn’t make my client think there’s something wrong. Please also see attached screenshot (sf_editing_templates.png) for an IE/FF/Chrome overview.
Back-End page overview.
When you’re managing pages, the default views (sort hierarchy) shows creation date instead of last published or last modified date. Doesn’t really matter atm, but a year from now most pages will be a year old while the client may have edited them 2 days ago. From clients view a last published date instead of creation date makes much more sense.
With regards to the ~/App_Data/WebsiteTemplates/MyTemplate/App_Themes/ThemeName folder structure, can you provide us with a folder policy? With the marketplace integration are you going to take the entire ‘ThemeName’ folder or the separate subfolders?
Suppose you use font-face in your theme, will it make a difference if we store them in ../ThemeName/Fonts or ../ThemeName/Css/Fonts ?