You can find Design Manager in Site Actions on your SharePoint 2013 site. It converts graphic design that is made as HTML with tools such as Dreamweaver into SharePoint master pages and stylesheets. When HTML with design is imported, you can use Snippets to add web part zones and other functionality.
How it works
How it works
It does work. It is a simple upload of a file with design.
To be honest, I'm not thrilled. I know that it sounds fantastic. It solves a well known problem of implementing graphic design into a SharePoint site.
I implemented design in more SharePoint sites than I can remember. I like building HTML and adding controls in Visual Studio. I don't like to use browser and click on buttons, but it seams like I'll have to learn it in order to add functionality with snippets.
Snippet code? Snippet code looks more complicated than adding controls in Visual Studio. Why does it look different?
What about editing the design package? What about upgrading the design package? Maybe I'm wrong, but I also see a big fat chance that all that nice HTML will break when I shove some web part zones here and there. What am I supposed to use to edit HTML then? Last time I used Dreamweaver, SharePoint didn't even exist. I don't think that I have the strenght to learn Dreamweaver...
What about working in Visual Studio on templates, event receivers, and web parts? I usually have everything stored in Visual Studio. Design package is a file that needs to be stored somehow, somewhere. I also need to store the resulting master pages and other files somewhere else than in database.
In short, and without screaming and throwing dishes ;-)
The main problem that I have with Design Manager is that the imported design doesn't cover the functionality: web parts, controls, and not to mention standard SharePoint list views and web parts.
Related Content
The Story of SharePoint 2013
Customizing Content Query Web Part
Other Things I Wrote
SharePoint 2013 Mobile
Metadata Driven Navigation
Geolocation
Simply Intranet - Upgrade to SharePoint 2013
Adventures with Napa Apps
MySite
To be honest, I'm not thrilled. I know that it sounds fantastic. It solves a well known problem of implementing graphic design into a SharePoint site.
I implemented design in more SharePoint sites than I can remember. I like building HTML and adding controls in Visual Studio. I don't like to use browser and click on buttons, but it seams like I'll have to learn it in order to add functionality with snippets.
Snippet code? Snippet code looks more complicated than adding controls in Visual Studio. Why does it look different?
What about editing the design package? What about upgrading the design package? Maybe I'm wrong, but I also see a big fat chance that all that nice HTML will break when I shove some web part zones here and there. What am I supposed to use to edit HTML then? Last time I used Dreamweaver, SharePoint didn't even exist. I don't think that I have the strenght to learn Dreamweaver...
What about working in Visual Studio on templates, event receivers, and web parts? I usually have everything stored in Visual Studio. Design package is a file that needs to be stored somehow, somewhere. I also need to store the resulting master pages and other files somewhere else than in database.
In short, and without screaming and throwing dishes ;-)
The main problem that I have with Design Manager is that the imported design doesn't cover the functionality: web parts, controls, and not to mention standard SharePoint list views and web parts.
Related Content
The Story of SharePoint 2013
Customizing Content Query Web Part
Other Things I Wrote
SharePoint 2013 Mobile
Metadata Driven Navigation
Geolocation
Simply Intranet - Upgrade to SharePoint 2013
Adventures with Napa Apps
MySite