Ryan Rogers has a post about programatically hiding the SharePoint Site Settings link from users without the correct access rights. Good idea and worth looking into…
For over a year our CMS site was plagued by deleted content occasionally popping back up in production or links reappearing that were dead because the content behind them was no longer there. Come to find out our background cleanup job was not created in the database. Andrew Connell has a good post about the background processing job, something to check out on CMS sites….
I watched a Web Cast about MCMS.RAPID and it left my jaw hanging. This is a very impressive FREE solution to help with MCMS deployments. It has several great features that I would love to have on my CMS site… which leads me to the one drawback- it is only for new CMS deployments and can’t be utilized OOTB on existing CMS sites. But hey… it is open source. Definitely worth checking out:
When designing a portal, keep the major areas in mind in relation to your URLs. SharePoint allows 20 areas (one being the Home) to be formatted nicely in the URL. For example, http://ThePortal.com/HR or http://ThePortal.com/Training. Once you hit the end of your 20 allotted areas, the URL will start organizing the areas into buckets. For example, http://ThePortal.com/C1/Helpdesk (note the C1). Continue reading Naming Areas on a Portal
If you want to stop your SharePoint site users from opening the site in FrontPage, you can add attributes to the Project tag in the ONET XML file and either limit their actions or stop capabilities completely. Continue reading Disabling Web Design Features