Building tylerbutler.com, Part 4: The Main Home Page and Migrating Content

Enterprise Content Management (ECM) Team Blog : Building tylerbutler.com, Part 2: Building Content Types and Page Layouts

Tue, 12 Dec 2006 00:50:38 GMT

PingBack from http://blogs.msdn.com/ecm/archive/2006/11/06/building-tylerbutler-com-part-2-building-content-types-and-page-layouts.aspx

re: Building tylerbutler.com, Part 4: The Main Home Page and Migrating Content

nxliu — Tue, 12 Dec 2006 05:17:42 GMT

so, for those pages which are unique such as site collection homepage or subsite homepage(i call them aggregating pages since they rollup or aggregate different content), template is meaningless and you don't need page layout to create new homepage, you can use "detached page" when you think the page is not performance-critical

you surely need page layout for content page.

sometimes your aggregating page may also associate with content type(hybrid page), in such case i think you need page layout, content is dynamic and we need template(or layout) to control content change where content is present

re: Building tylerbutler.com, Part 4: The Main Home Page and Migrating Content

Michael Gannotti — Wed, 13 Dec 2006 14:34:08 GMT

This has got to be one of the best series of articles out there and many of my clients have loved them. Thanks for keeping this going with more great info.!!

Building tylerbutler.com, Part 5: Final Touches

Enterprise Content Management (ECM) Team Blog — Mon, 18 Dec 2006 23:43:09 GMT

Part 1 :: Part 2 :: Part 3 :: Part 4 :: Part 5 :: Part 6 This is part 5 of an ongoing series of posts

Building tylerbutler.com, Part 6: What Was Tough, and What’s to Come

Enterprise Content Management (ECM) Team Blog — Tue, 16 Jan 2007 05:26:29 GMT

Part 1 :: Part 2 :: Part 3 :: Part 4 :: Part 5 :: Part 6 This is part 6 of an ongoing series of posts

re: Building tylerbutler.com, Part 4: The Main Home Page and Migrating Content

alan chaplin (alan.chaplin@kpmg.co.uk) — Tue, 06 Feb 2007 20:40:30 GMT

We're looking to implement sharepoint 2007 based content management system. I have millions of documents on a file system to import - the site/library/meta data can be derived from parent folder and existing file properties. The time of 20 minutes for 200 documents sounds scary - weeks per million although expect we can improve by factor of 10 say by reworking code/better hardware.

However still doesn't feel like the right approach - any suggestions?

How we did it: PFGC.com -- design, development, and go live in 10 weeks!

Microsoft SharePoint Products and Technologies Team Blog — Sat, 26 May 2007 08:04:00 GMT

Dominion Digital , a Virginia-based Microsoft Gold Partner, recently launched the Performance Food Group’s

SP Branding and Content Migration

Irina Alexandris — Thu, 07 Aug 2008 00:10:45 GMT

Very interesting multi-part blog about SP branding and migrating content: http://blogs.msdn.com/ecm/archive