Ok, so I’ve been playing with the SharePoint 2013 preview for a couple of weeks, mostly I’m impressed. However, I just can’t seem to wrap my head around the idea that Microsoft is not going to include a “Design” view in their SharePoint Designer program.
Granted, this application has its roots back in the dreadful days of FrontPage. But seriously, to have to make changes to page formatting and save the file in order to render it? It’s like going back to the old days of classic .ASP coding when you’d open a file in notepad, make a change, save, refresh browser to see results. Ouch. And since SharePoint is a collaborative platform do I allow the power users to have designer access to production to make these UI changes and potentially have them break live sites during their save/refresh cycles? Honestly, I’m hoping this feature was excluded from preview because it “just wasn’t ready yet” and is not going to be a permanent change for the RTM.
Additionally, I really like the fact that I can open a page in SPD split view, click on a UI element, and have it take me right to the code that deals with that UI element. Especially useful if I notice some wording or style that I want to make a quick change to without having to scroll through the code to find the right line.
As for those of us who can quickly set up the Data View Web Part in SPD as a way of displaying List driven content… I’m not sure how we’re going to deal with having to create XSL driven UI.\
I think this may be strategy based on Microsoft’s part to drive power users over the edge to the Visual Studio world, but as one of SharePoint’s main selling points appears to be it’s ease of use for the end user and easy customization of the system with “no code” solutions, I have to wonder how effective it will be in the long run for getting companies to adopt SharePoint who have not already made the investment. Or maybe MS just figures they’ve got a large enough customer base as it is.
Still loving the “Zoom to Content” function (ct100_fullscreenmodeBtn) though….
When dealing with SharePoint, I’ve found that I like to keep all my scripts in a single directory, both because it’s clean and it helps to separate out the site wide scripts from other files on the site. However, once you’ve created your scripts library, often times you don’t want the average user poking around inside these directories. By hiding a scripts library from the browser you can keep your site secure (ish). There’s no way around poorly written code, but at least you’re not putting out the welcome mat and allowing browser access. Hiding the library allows you to prevent the casual inquisitive eyes from wandering through your script code.
1. Create a document library in the root of your web application. Use the document template of none.
2. Your naming convention for this library should be something simple. I use /Scripts but you can name it anything like. Just be consistent as you’ll always want to have a standard to make your pages somewhat portable from one site to the next.
3. Once the library is created you want to hide it from the browser, this option just eliminates the browser navigation. If you know the URL it can still be accessed through the browser, just hidden from normal navigation. You always have access to it through SharePoint Designer (SPD).
To hide from browser open your site in SharePoint Designer
- Right click on your Script library
- Select Properties
- On the Settings tab, select Hide from browsers
This library can no longer be accessed through the browser SharePoint interface.
REDMOND, Wash., Feb. 15, 2006 – As the Internet becomes an increasingly valuable environment for individuals and organizations to share information, collaborate and carry out tasks, the people tasked with building Web sites to support these activities need increasingly powerful and versatile tools to accomplish their goals.
Having adopted technologies such as Microsoft Windows SharePoint Services and Microsoft Office SharePoint Portal Server 2003 to help create, manage and build collaborative Web sites, many organizations are discovering that their current Web-authoring tools lack support for the latest standards and capabilities that SharePoint products and technologies makes possible – such as ready access to data coming from multiple outside sources and the capacity to build no-code, powerful applications and automated workflows. Professional Web site designers also are feeling the pressure to deliver more dynamic and interactive user experiences, and to create sites more rapidly and cost-efficiently.
In response to these diverse demands, Microsoft is introducing a new tool, Microsoft Office SharePoint Designer 2007, for building SharePoint applications and designing SharePoint sites. This new product – part of the full 2007 Microsoft Office lineup announced today – will join Microsoft Expression Web Designer, the next-generation tool for designing dynamic, standard-based Web sites, to deliver a complete set of tools for Web design and development. Both products are currently in initial beta testing. Microsoft Office SharePoint Designer is scheduled for release in the second half of this year at a suggested retail price of US$299 through retail and Microsoft Volume Licensing channels. Pricing and availability details for Microsoft Expression Web Designer will be announced in the near future.
PressPass recently asked John Richards, director of Windows SharePoint Services at Microsoft, to describe how these new products fit into the company’s overall approach to Web authoring technologies. Full story here
So what is happening with FrontPage?? Here’s the answer:
PressPass: What is happening to the current FrontPage product, and how is Microsoft communicating with FrontPage users to alleviate concerns about migration, ongoing technical support and the like?
Richards: After we fully release SharePoint Designer 2007 and Expression Web Designer, FrontPage will be discontinued gradually. This process will bring our customers and partners a broader choice of tools that go far beyond the capabilities within the current FrontPage product to meet the needs of today’s and tomorrow’s Web authors, designers and developers.
In the meantime, Microsoft will continue to provide current FrontPage customers with full product support through June 2008, as well as clear guidance on how they can smoothly migrate to SharePoint Designer 2007 or Expression Web Designer, depending on their roles and needs. In the near future, all registered Microsoft Office FrontPage customers will receive e-mail from Microsoft outlining our overall strategy and roadmap for these next-generation Web authoring tools. We also will provide continual updates on the Microsoft Office product Web site. In addition, current FrontPage customers in both the retail and enterprise channels will be able to take advantage of special upgrade offers starting in the second half of 2006.
FrontPage is dead, long live SharePoint Designer…