I ran into an interesting situation this morning with a customer. One of their internal departments has a group of technical writers that manages a lot of procedural documents and forms and they use a web site based on FrontPage to manage this. They were originally asking for some help learning Expression Web, which they had identified as the upgraded product to FrontPage. They manage a site that is almost completely read-only to their users, with a team of 6-8 who edit pages on the site. They are leveraging Dynamic Web Templates (DWT) within their page designs, so they are seeing some reusable benefits in their efforts.
I’ve spent a couple of days of time with them, explaining the benefits of SharePoint features, including collaboration and permission management, and different approaches to page editing and management.
At the end of today’s session, however, we all felt that it would still require less effort to migrate their site to an ASP.Net based site using Expression Web, than would be required to convert the pages to SharePoint. This is because the site is completely read-only to the users and there is no collaboration requirement.
They did bring to my attention a web tool for managing security on the IIS web site to support permission management for their site if they did move to Expression Web. This tool is the Web Site Administration Tool, described here on MSDN. This looks like a useful tool (although I haven’t installed it yet) to manage the last hurdle that was a firm requirement for SharePoint, that of page permissions. They need to restrict page views to specific AD groups and specific individuals.
Because I was working with only one department, there was not a way to “sell” the advantages of having a corporate environment. I think that this department could benefit in the long term from using a SharePoint platform, through content reuse and version management and collaboration for their small team, and this department could serve as one of the supporting reasons for the customer as a whole to move to a SharePoint platform for their corporate intranet.
Until the conversation can be held at the Intranet level, however, the justification for moving on a broadscale to SharePoint can’t be leveraged to help the accounting department. If we wait too long to get the corporate intranet moved over to SharePoint, this site will be converted completely to .Net and Expression Web, and it will be even more difficult to justify the page conversion cost to migrate these pages again, ultimately to SharePoint.