Comments on: Show Sitecore how to improve…

By: Francis Norton

Francis Norton — Fri, 09 Jan 2009 11:37:20 +0000

One big improvement would be a tree-structured view of placeholders in the top-left pane of the page design mode – the existing flattened list is very frustrating for complex pages, particularly those with repeating sub-layouts where you have to go all GUI to work out which of the identically-named placeholders you actually need to select.

By: Mark Cassidy

Mark Cassidy — Thu, 01 Jan 2009 13:35:13 +0000

On second thought…. I think Microsoft just showed the way

http://video.google.com/videoplay?docid=2943736722728060847

Happy new year everyone

By: Alex de Groot

Alex de Groot — Thu, 18 Dec 2008 16:22:36 +0000

Thanks Per, Alistair(http://adeneys.wordpress.com/2008/12/17/my-sitecore-wishlist/) and Mark for the very impressive suggestions. I’m not going to tell you that we solve your pains tomorrow. But I’ll definitelly try to redirect them to the right persons.

Keep it coming as well.

By: Mark Cassidy

Mark Cassidy — Thu, 18 Dec 2008 15:45:12 +0000

http://www.cassidy.dk/blog/sitecore/2008/12/showing-sitecore-how-to-improve.html

By: Per Bering

Per Bering — Tue, 09 Dec 2008 08:31:03 +0000

@Alex
Performance, stability, scaling >> Well, an example could be a solution with about 10 frontend servers each running 8 instances of staging slaves (8 sitecore sites on SSL) and one master server – Think about how much time it takes to publish and clear cache on on every 80 instances, and then think about the pain the SQL server cluster is is when every 80 instances request for data again. This is an extreeme example I know, but still it repesents issues we see in production enviorments and custormers expecatitions of sitecores ability to scale and performe. Feel free to look at our resent support issues the last few months or so.

CI >> See (http://en.wikipedia.org/wiki/Continuous_integration), what do you meen with “What about deployment?” – A start could be to make every think in Sitecore serializable so we could write data classes that would give us items directly from Sitecore or through a webservice if not running on the webserver.

SDN: Go and buy Community Server and then you would have superior forums, blogs, feeds and search – My point is that I need a search to search in ALL content on SDN, including all forums and I need ALL results to be shown and not only a few in each section. And please fix the search box, just remove the suggest feature – It dosn’t work. And last, the current design and layout is not optimal for the type of content that you serve, it should be more like MSDN for downloads, documenentation and the developer centers.

Thanks for listening

By: Matt Hovany

Matt Hovany — Wed, 03 Dec 2008 17:31:07 +0000

@Alex: I wasn’t implying SC6 wasn’t documented enough. I was only half joking/half suggesting we could use a 6.0+ only version of the sdn, rather than having 5.1, 5.2, 5.3, 6.0 content all mixed together (yes some 5.x content applies to 6.0 as well). Also sdn5 is running v5.1, it must be hard for the editors to have to use the old UI when 6 is so smooth.

By: Alex de Groot

Alex de Groot — Wed, 03 Dec 2008 10:42:18 +0000

Great Feedback Matt and Per,

@Matt: We’ve changed our training curriculum over the past few months. So it’s quite likely that we’ll never talk again about levels. ‘The training curriculum is based on a couple of base exams and can be adjusted by role-specific tasks. More information upcoming soon on the Sitecore site. Or contact your local sales office about this.
SDN6: If you point out there’s a lack of documentation for version 6, you’re wrong. Our documentation team has produced, on many requests, a set of 10 PDFs: http://sdn.sitecore.net/Reference/Sitecore%206.aspx
More are upcoming in the next months. We’re also working on restructuring SDN. The amount of knowledge on this network has grown rapidly. Please supply us with some more information how you’d love to see your personal knowledge portal.

@Per:
>> Performance, stability, scaling (.NET WebFarms, shared cache like Velocity).
This is a bunch, can you please give me the business case? At this moment we might be addressing some parts of it. But most of them are already working fine. I haven’t seen issues with performence and stability lately, but maybe you have some more info or you’re reffering to a specific case?
>> Freeing the API from the httpcontext to enable new applications and proper unittesting/deployment/CI etc
Again, thanks. I can imagine that the HttpContext is horrible for unittesting, but deployment? What do you mean by CI?
>> Build a much better community site with better search and forums
May I add better ’search’ and ‘forums’ to the feature list of ‘SDN6′ ?
Can you be a bit more specific, for example, how would you like to search in SDN?

I can’t promise you guys that all of this will adressed, please supply me the additional information I’ve asked for so I can direct it to the right guy internally.

Thanks so far and keep it coming,

- Alex

By: Per Bering

Per Bering — Wed, 03 Dec 2008 08:09:35 +0000

Performance, stability, scaling (.NET WebFarms, shared cache like Velocity), freeing the API from the httpcontext to enable new applications and proper unittesting/deployment/CI etc. Build a much better community site with better search and forums – Keep up the good work!

By: Matt Hovany

Matt Hovany — Tue, 02 Dec 2008 19:34:22 +0000

sdn6.sitecore.net?

By: Matt Hovany

Matt Hovany — Tue, 02 Dec 2008 17:45:26 +0000

How about a “Level 3″ certification course. Not for me, for our new devs.