We are excited to provide insight on hot and common issues, supportability, and some how-to's for Microsoft SharePoint Designer. The blog is solely authored by "support" individuals, so many of our posts will be issue + solution centric. Since we interface with customers day-to-day, we definitely have a unique view and understanding of the problems seen by users, such as yourself. If you are looking for a wider scope of topics related to SharePoint Designer, we suggest checking out the official Microsoft SharePoint Designer Team Blog.
Our support team consists of three individuals, and we take on support issues for all customers in the professional and premier space. Chances are, if you have called in to Microsoft Support with a SharePoint Designer related issue, you've worked with one of us. We are the same people authoring this blog, and include:
- Michael Mongeau (myself): I am a Support Engineer for SharePoint Designer, FrontPage, and FrontPage Server Extensions (yep, still supported). When I can, and often on my personal time, I answer community questions on the MSDN forums, MSDN newsgroups, and SharePoint University forums under the alias "monjo". Additionally, I own and sometimes to blog about SharePoint Designer on my personal site
http://dataformwebpart.com. However, my focus going forward will now be directed at creating content for this blog instead of my own.
- Dalibor Kovacevic: Supports SharePoint Designer, FrontPage, and FrontPage Server Extensions. Dalibor is our Knowledge Engineer and helps review and revise internal support documentation. He has a BS in Information Technology Management. He enjoys seeing what crazy things he can get SharePoint to do with SharePoint Designer.
- Lucas Koehntop: Supports SharePoint Designer, FrontPage, and FrontPage Server Extensions. Lucas has a BS in Computer Science, and has his MCSE. He loves high tech country life, along with enterprise computing.
Have any suggestions for content, or questions about the blog? Please email us at email@example.com, and we will do our best to respond and take your suggestions into consideration. Note: please understand we are very busy, and will most likely not reply to all emails.