Tips & Tricks from Linda

The DEECD (Department of Education & Earlier Childhood VIC) needs to upgrade the branding of several Public facing Sites from SP2010 to SP2013 platform.  I upgraded the existing look & feel in SP2010 to SP2013 and also made their mobile site using SP2013 new branding functionalities. I developed the customed HTML master page, CSS and jQuery file for below web sites. I also troubleshooting a "The Design Branding Package creation failure issue" which related to a SharePoint 2013 bug confirmed by Microsoft (see my post here ). Below are screenshots of some Web sites in desktop & its mobile site. The above content in mobile view won't be seen in the desktop view of the Website. It only shows when in the page editor mode. The Web site for Deaf user.

I had been worked on a SharePoint 2010 Internet sites upgraded to SharePoint 2013 project in 2014. The SharePoint 2010 site was customized with some farm solutions.  I experienced the Design Manager Design Package creation failure issue in SharePoint 2013 which upgraded from SharePoint 2010. The Design Package was used for the site branding deployment. I added the branding sources files including JavaScript, HTML master page, CSS and images to another clean out of box site collection and then the design package can be created successfully on there. But after deployed those custom farm solutions to this site collection, and package creation was failure again.    So I started to look at this issue around those custom solution. I found out the root cause of the design package creation failure was the special character (ASCII) ▲ added to the custom property bag value. I went to SharePoint designer and then clicked on “Site Options”, and then removed a...