We all know that web development is often driven by concepts and marketing. The goals are msotly marketing related, so as a technical fellow, you’re not leading. As professional developer you should know that such a view has a positive and negative side: positive because it’s driven by goals, not just ‘where they ask for’, negative because technical solutions are always on the budget side of the project. So you’ve to work efficient. Working efficient means most of the time that you’ll skip some parts. To prevent you from making mistakes while designing the solution, I want to make you aware of the following questions which should be asked:
- Do you know where to host your solutions and on which infrastructure?
- We can design Sitecore in 2 ways: single site, multisite…. Single site means that it’s used for 1 site, changing it later on is hardly impossible and very time intensive. Multisite costs way more at the first stage but prepares your solution for more sites.
- How many users will use Sitecore? Do they have different roles? For different Sites?
- What’s the primairy way of using Sitecore? Should be optimize the website for web-editing? Or will you only use the Content Editor?
- What’s more important? Lower costs on Sitecore design or more system usability(means more efficient content editing => more productivity for content editors)?
- What’s the more important, that the (X)HTML is valid and readable for software or that the site has rich interaction such as AJAX technologies.
This list is at the moment way to short and should expanded, but this is allI can think of by now.
I’m off for some days to Val Thorens. Snowboarding(for what’s left of the snow) and partying a lot. I’m back around the 7th of may.