Sitecore Saving vs Saved Event and when to use which

One of the developers I am mentoring asked me a good question and I thought I would share the answer with the guild in case you are wondering the same.

The question is related to saving items to an external DB when they are saved in Sitecore.  There are really two ways to handle it.

1) Write an Item Provider and store them in a single location.
2) Use the item save events but which one is the right one to use.

In our case it was more beneficial to use option 2.  Using Saved vs Saving depends on whether the external DB will store any data that will be calculated based on saved data rather than simply saving a copy.  Saved happens after the Sitecore item is saved where as Saving will allow you to perform additional operations on the Sitecore item prior to save.

The other thing to be aware of is that when an item is duplicated it will NOT call the saving or saved events unless the user explicitly hits save.  If you require duplicate items to make it to your database too then you will need to implement this event too.

John West wrote a really good article with sample code as well, called Intercepting Item Updates with Sitecore.

If you have any tips, tricks or resources you would like to share with the guild please email them to chris.williams@readwatchcreate.com and we will post them here.

Having Trouble Finding a Sitecore Resource? Why Not Train one.

I recently wrote a quick article on LinkedIn regarding the current shortage of Sitecore talent called Having trouble finding s Sitecore resource.? Why not train one and am getting a lot of good feedback.

If you are interested in learning more on the best way to train a Sitecore resource to help build your team. Please contact us at  chris.williams@readwatchcreate.com and we will help.

On a side note, if you are a .NET Developer working with C# and are interested in working with Sitecore or Dynamics CRM, you can apply for our Mentorship Program.  If accepted, then we will mentor you on Sitecore or Dynamics CRM.  We will provide you with a project to work on with us that will build your skills and allow you to make some money at the same time.

To apply for the Mentorship Program please email your resume along with details on why you want to work with Sitecore or Dynamics CRM to chris.williams@readwatchcreate.com

We look forward to working with you to achieve your goals.

Sitecore MVP Summit Day 2

After breakfast Pieter Brinkmanstarted the conference off with a welcome.

Next was the Keynote featuring Michael and Lars.

An introduction to Who's Who at Sitecore

Out the front of the hotel waiting for the bus for an amazing boat tour on the Venetian Lady

The Venetian Lady was beautiful.

 A Stellar view of the city from the top deck of the Venetian Lady

Roll your own cigars :)

Really good Rum

On the beach preparing for the group photo

 Look at that beach

A conference could not be complete without some John West meme :) 

http://memegenerator.net/Sitecore-John

Everyone I spoke to had an amazing time, thanks Pieter and Marissa for organizing a stellar event.

Sitecore MVP Summit 2013 - Day 1

Last night was an amazing reception, Pieter and Marissa provided a warm welcome and some amazing shwag.



I immediately put the mobile card holder on my phone and made use of it a lot at the MVP Reception at the James Royal Palm.

We were greeted by strong winds and rains but the friendly staff were on hand with large umbrellas to welcome us in. 

The area has some nice buildings



On Lincoln Road, we found a really good burger place



I got to meet all the Sitecore MVPs from Japan.


The Sitecore Pillow was on hand and brought some of his relatives.  I would love provide a home for one of the to Three Point Turn in Toronto Canada.

Thanks Pieter and Marissa for an amazing first day.  I look forward to breakfast, the presentations today and the evening on the Venetian Lady.  I will post again about this on Day 2.

jQuery not firing after Microsoft AJAX Update Panel Postback - or why pageload is better than document.ready

I ran into an interesting issue today while using jQuery in an AJAX Panel.  It appears that existing items that were there on original page load were triggering but any new ones after an ajax postback were not.  I did some searching and came across the issue.

It appears that document ready and pageload are not the same  document.ready only loads once when the page is loaded but not on all the AJAX page loads.  The solution is to use function pageLoad() and do your calls within there.

However, this leads to another problem.  If you simply use function pageLoad() then you can only call it once on your page.  There is a solution to this as well.  This article explains how to make ASP.NET AJAX Multiple pageload functions possible through simply using

<script type="text/javascript">

    Sys.Application.add_load(function () {
     // Your Code here
   }

</script>

If you have any tips, tricks or resources you would like to share with the guild please email them to me at chris.williams@threepointturn.com

QuickStart: Deciding what Data Goes Where

One of the biggest factors in a successful Sitecore implementation is determining where data is stored.

These storage locations can be grouped into four types:

a) Sitecore Content Tree
b) Local Data Sources
c) Enterprise Data Sources
d) External Data Sources

The initial tendancy is to place everything in the content tree especially if you are not working with Enterprise Data Sources or External Data Sources.


What To Store In The Content Tree
---------------------------------

The Sitecore Content Tree is a good place to store data that is easily placed in a hierarchy of 1 to 1 or 1 to many item relationships.
It is NOT good at storing data that is tightly related to many other items.  It is also not as great a storing large volumes of direct children unless you take

advantage of such modules as Item Buckets.

The key question to ask when considering placing content in the content tree or media library is:

* Is this content only used by Sitecore or is it used by another application such as CRM, SAP, Sharepoint or some other system?
If this content is only used by sitecore in most cases this data should live in the Sitecore Content Tree, or Media Library.
There are some exceptions such as User Management/Security which may be only used by Sitecore but does not make sense to be in the content tree or media

library.  User Management is discussed in another Blog Article.

* Does this content need to be editable by content editors or is the data edited in external systems or only by users of the website?
If content editors will not be editing this content then the additional overhead would not necessarily be worth it and you are probably better served storing
it in the external system, additional SQL Server database tables, or in another data source.

* Other than for reporting, is this data read by any other website components?
If the data is only being collected by sitecore and then displayed in a report or used by the rules engine, you don't really need to store it in the content

tree.  Storing it in an external table would allow data to be queried more easily for reports or dumped to external reporting applications.

Here are some examples of data to store in the Content Tree:


* Page Hierarchy: By this I mean the website root node and all the pages used to build your navigation.  It makes sense to store this as it helps
  structure your content.

* Static Page Content: This is content related directly to a page.  It may be as simple as a title and a description and whether it is included in sub navigation.

* Resource Strings: These are all the field labels, static descriptions, help messages that are straight text with no formatting.

* General Site Settings: These are settings either related to the entire sitecore instance or per site. These are specifically setting that need to be edited by the

end user.  These settings are instance-wide and do not change often then you would want to place these in the .config files.
 
* Media Items such as images, PDF, Word Documents, PowerPoints, etc should be stored in the media library.

* Semi-static lookup lists.  This includes country lists, departments, regions, currencies, etc.

* Generic content items:  These are content items that will be updated, possibly need approval and then get published.  They can be shared across many pages.
An example would be a an article.  It may exist in an article page, but also be featured on a front page, or in a content rotator.  This single piece of

content would have all the information in one place and be referenced on the multiple pages.


Some examples of what NOT To Store in The Content Tree
------------------------------------------------------

* User Information such as logins, roles etc.

* Reporting Data and Logs are best stored in a local data source as this data will be written once and then reported on.  End users will NOT be editing this data.

* Product lists, e-commerce purchase transactions.



In an external database directly accessed via the Sitecore Web Application (three-tiered of course).  This would also include any imports and extracts
c) Cloud/external data sources (eg. via web services, Sitecore Connectors, etc)

QuickStart: Securing Sitecore

Sitecore is built on the standard .NET Membership Provider.  As such developers will be familiar with how it functions under the hood as far as creating user, profiles and roles.  However, it can become a little more complex when dealing with securing content.  Content needs to be viewed and edited by users who log into the Sitecore Admin, whether it be the page editor, content editor, or media library.  As well, content needs to be viewed and edited by users accessing the public website.  This can be confusing especially if you have not mapped out a roles matrix first.  This Quickstart will help walk you through the steps you need to ensure you have a secure sitecore installation.

Ensure before going to Production that you follow the checklist at the end of this blog post to ensure you have secured your Sitecore Installation.

1) Develop a role matrix

Roles are used to determine which of people will be responsible for reading/editing/publishing content.  Depending on your implementation, certain people may only be able to accessing certain content.

Some may access the page editor, while others need the content editor, and still others need the desktop.  

  

 It is very tempting especially when working with small companies to map users to their access.  Joe is the one uploading pdf files and editing content. Mark will will be the one proof-reading the content and then publishing it.  Rather, Joe is a content editor and Mark is a publisher.  So your role matrix would be:

Role

-----

Admin

ContentEditor

Publisher

RolePermissions

-----------------

/sitecore/content             Admin                          Read/Write/Publish/Admin/Delete

/sitecore/content             ContentEditor               Read/Write/Publish

User Roles

------------

Joe                     ContentEditor

Mark                 Publisher

Production Promotion Security Checklist

1) Important Sitecore provides a default “Admin” user which has unrestricted access. By default, this user has the password “b” (lower case, single letter). You should change the password associated with this account and store the password in a secure location.

2) Ensure /Sitecore is in the robots.txt file

3) Ensure you register your site with webtools and exclude this path there as well.

4) Log in as a user of each role and double check that you cannot read/edit specific content you have secured.  The access viewer can help ensure you see a sea of red.

Quickstart: creating a sitecore package

Although the preferred method for deployment is through Hedgehog, sometimes it it necessary to build a sitecore package to deploy or share your sitecore modules.   If you are deploying a build and You will want to split your packages up to avoid reference issues.  I tend to seperate them into 4 packages: data templates, media library, sublayouts/layouts and content tree.

Note: if you run into conflict issues you may have to break the content package into pages and content then deploy content package before pages.

If you are building a package for a module then you will be including everything in one package.  This would include dll and other physical files.  If you are including config changes always include them in an includes config and dont overwrite the existing config.

STEPS

1 open the browser and navigate to the sitecore admin

2 ensure you click options to and select desktop

3 enter your username and password and login

4 click on the Sitecore menu and click on developer tools

5 click on package designer

6 click on new to create a new package

7 give the package a name

8 save the package

9 enter a name to save the package xml

10 in the menu select static items to add items to your package.

NOTE: although tempting avoid using dynamic packages as you may unintentionally miss content items needed or include more items than you need.

11. Click on the item you need and if necessary choose add subitems.

12 if there are more items in the group add them the same way.

12 click next and enter a name for the items.

13 save the package

14 generate the package

15 once generated click on the globe to download it

When you are ready to deploy the package check out the quickstart on how to install a package using Sitecore ROCKS or how to install a package if Rocks is not installed.

Sitecore QuickStart: Create Visual Studio Project

In Sitecore Training you learned how to create a Visual Studio Project for your Sitecore Instance.  This is an awesome start for your first project, however as you start to share functionality across projects, create your own modules, or start working in a multiple sites per instance scenario, you may need multiple projects per instance.

In the solutions I have architected, I generally will leave the Sitecore instance as is and create projects in their own projects folder.  These projects can then be deployed to the sitecore instance as needed by copying over the dll and any layouts, sublayouts etc.  Architecting the Content Tree and Physical Folders will be in a future QuickStart.

In this blog article, I will be creating a Visual Studio Project that could be used for a single site within the Sitecore Instance.

Step 1: Create a Visual Studio Class Library.

Click on the File Menu and Click New and then Project 

On the left panel ensure you have clicked Windows then on the right click Class Library.  Name your project and directory to store your project.

Step 2: Add References To Sitecore Kernel and Sitecore Logging

In the Solution Explorer Panel, Right click on References then click on Add Reference...

Click on the browse tab and navigate to the bin folder of your sitecore instance.  Select the Sitecore Kernel and Sitecore Logging DLLs.  Alternatively you could place these dlls in a shared folder.  Click OK to Add References.

Add References to your project for System.Web 

Step 3: Create folders for your Sitecore Components

NOTE: This is a very basic folder structure.  Your project may have a more sophisticated structure to represent your solution. However the concept of deployment on build is the same.

STEP 4: Add Build Events

Right click on your project and click on properties

Click on Build Events

In the Post-build events command line paste the following.  

xcopy "$(ProjectDir)Layouts" "C:\inetpub\wwwroot\SitecoreQuickStart\Website\Layouts" /s /I /y

xcopy "$(ProjectDir)Renderings" "C:\inetpub\wwwroot\SitecoreQuickStart\Website\Renderings" /s /I /y

xcopy "$(ProjectDir)Sublayouts" "C:\inetpub\wwwroot\SitecoreQuickStart\Website\Sublayouts" /s /I /y

xcopy "$(ProjectDir)bin\debug\SitecoreQuickStart*.pdb" "C:\inetpub\wwwroot\SitecoreQuickStart\Website\bin" /s /I /y

xcopy "$(ProjectDir)bin\debug\SitecoreQuickStart*.dll" "C:\inetpub\wwwroot\SitecoreQuickStart\Website\bin" /s /I /y

NOTE: Change SitecoreQuickStart to your project name.  You may need to add more dlls to copy, however do not be tempted to do a *.dll as you may end up overwriting other versions of dlls in the Sitecore Instance.  It is better practice to only copy over the dlls you require.  Also, we are copying the Layouts folder to the Sitecore Layouts folder directory.  For larger projects it is better to create subfolders beneath the layouts folder unless the Layouts are needed for Sitecore Admin Applications, but that will be discussed in a future post on creating Sitecore Admin Applications.

STEP 5: Compile Your Solution

From the Build Menu Choose to Build Solution.  Once completed it should have copied your Sitecore Components to the Sitecore Instance or reported errors in the error list.

Now that your Sitecore Project is set up, the next step is to create your Sitecore Components in the Sitecore Content Tree.

Sitecore How-To: Set the Data Source Property of a Sublayout

The Data Source property of a Sublayout is used when the sublayout needs to use a content item other than the current item.

For example, you may have a landing page with various callouts to other content. These content items would exist in other parts of the tree. For these callout Sublayouts you would not want them accessing the current page item, you would want them pointing at another object that would store the callout title, image and link.

Here are the steps to set the data source on a sublayout on a page.

1. Login To Sitecore and open the content editor
2. Navigate to the page you want to edit
3. Click on Presentation -> Details in the top menu
4. In the Details Panel click on Edit
5. Click on Controls to see the list of sublayouts
6. Click on the Sublayout you want to change the data source for
7. Click on the data source field. You can either manually enter the path or click browse to choose the content path from the tree dialog
8. Click ok to save
9. Click ok to close all the other dialogs

Sitecore How-To: Sitecore Country and Region Dropdowns

We had a couple people in the Guild ask about country and region DropDownLists so thought Dennis Augustine and I thought we would write an article on it.  

Problem: In our application we require a country and region picker.  When someone chooses a company we need to filter the region picker.

Solution: This can be accomplished by adding two DropDownList controls to your SubLayout. Call one ddlCountry and the other ddlRegion.  

In the content tree under a shared lookup area create a folder called "Country"  under this folder add the countries with key as country code and phrase as country name.  Next under each country create a folder called "Regions" store all the regions in this folder.  I use DictionaryEntry as my Sitecore Data Template for the country and regions.

On Page_load you would call GetCountries() and assign it to the ddlCountries.DataSource Property.

    protected override void OnLoad(EventArgs e)
    {
       ddlCountry.DataSource = GetCountries(); 
       ddlCountry.DataValueField = "Key"; 
       ddlCountry.DataTextField = "Phrase"; 
       ddlCountry.DataBind(); 
   }

Next trap the change in country using the following event:

protected void ddlCountry_SelectedIndexChanged(object sender, EventArgs e)
    {
            ddlRegion.DataSource = GetRegions(ddlCountry.SelectedValue); 
            ddlRegion.DataValueField = "Key"; 
            ddlRegion.DataTextField = "Phrase";  
           ddlRegion.DataBind(); 
    }

Next add the following code to the sublayout. Ideally later you would store these in a library for use late in other parts of your code. Also note that you would need to change "SiteSettings.LookupPath" to the path where you are storing your countries in the tree.  This setting occurs a couple times in my code below.

///<summary> 
/// Getting children items by parent item path 
///</summary> 
/// <param name="itemPath"></param> 
/// <returns>List<LookupItem></returns> 
public static List<LookupItem> GetLookupItemChildren(string itemPath) 
{ 
Item item = Sitecore.Context.Database.Items[itemPath]; 
List<LookupItem> lst = new List<LookupItem>(); 

if (item != null) 
{ 
foreach (Item child in item.Children) 
{ 
lst.Add( new LookupItem(child["Key"], child["Phrase"],child["AlternatePhrase"])); 
} 
} 

return lst; 
} 

///<summary> 
/// Getting Countries by Countries 
///</summary> 
public static List<LookupItem> GetCountries() 
{ 
return Lookups.GetLookupItemChildren(SiteSettings.LookupsPath + "/Country"); 
} 

///<summary> 
/// Getting Regions By Country KEY 
///</summary> 
public static List<LookupItem> GetRegions(string countryKey) 
{ 
Item item = Lookups.GetItemByKey(SiteSettings.LookupsPath + "/Country", countryKey);
return Lookups.GetLookupItemChildren(SiteSettings.LookupsPath + "/Country/" + item.Name + "/Regions"); 
} 

In Sitecore 7 you can replace these item lookups with LINQ statement.

Dennis Augustine has now created and uploaded the Country Region Dropdown Sitecore Module based on the blog post and it is now available in the Sitecore MarketPlace as a Development Accelerator.

If you have any questions or any tips, tricks or resources you would like to share with the Guild please email me at chris.williams@threepointturn.com or dennis.augustine@threepointturn.com 

Install A Sitecore Package From Sitecore Rocks

If you are looking to upload a package using Sitecore Rocks Visual Studio Plug-In you can do so by:

1)  Opening Visual Studio, clicking on SITECORE menu option.  

2) Click on Sitecore Explorer

 3) Click on the connection you want to install the package on.  If not connected then connect to it.  If connected choose Manage Packages.

4) In here you can create a package, upload a package, prepare anti-packages etc.

The anti-package feature is one of the most useful.

For those using commandly, you would use the Manage Package task

QuickStart: Resource Strings

When planning the Sitecore Content Tree Architecture it makes sense to place some content on a page.  Other times it makes sense to create Generic Content items that would store blocks of content in a shared location.  This content could be used across pages.  Other times there are content items such as Form Labels, static text for instructions.  These need translations, but placing the potentially thousands of them in the generic content folder would make it more difficult to manage.

The alternative is to create a folder underneath each site in a Multi-Site solution called ResourceStrings.

Under this folder you can arrange your resource strings by SubLayout name and/or whichever folder structure makes sense to make them easier to find.

If you use a fast query to find them then as long as the resource string name is unique you can place them wherever you want or reorganize them later as you please.

        public static string Translate(string key)

        {

            string itemPath = "FAST_" + Context.Language + "_" + Context.Site.ContentStartPath + "/ResourceStrings//*[@Key = '" + key + "']";

            if (CacheManager.GetData(itemPath) != null)

            {

                return CacheManager.GetData(itemPath) as string;

            }

            string result = string.Empty;

            Sitecore.Data.Items.Item[] dictionaryItems = Sitecore.Context.Database.

                    SelectItems("fast:" + Sitecore.Context.Site.ContentStartPath + "/ResourceStrings//*[@Key = '" + key + "']");

            if (dictionaryItems != null && dictionaryItems.Length > 0)

            {

                // bad entry should fail gracefully.

                try

                {

                    result = dictionaryItems[0].Fields["Phrase"].Value;

                }

                catch

                {

                    result = string.Empty;

                }

            }            

            CacheManager.Add(itemPath, result, CacheItemPriority.Normal, null, new SlidingTime(TimeSpan.FromSeconds(SiteSettings.ItemCacheInSeconds)));

            return result;

        }

Note that this example uses CacheManager.  This is simply the Microsoft Practices Cache Manager.

In order to support the content editor you would need to wrap the controls you are using to display them in sc:editframe I am actually working on a QuickStart Package that would include a series of controls that loosely wrap the standard Sitecore and .NET controls with the ability to supply a resource string.

The Resource Strings Module is now available in the Sitecore Marketplace with full source code.
This should help you get started.  If you are using Sitecore 7 you may want to take advantage of LINQ in Sitecore over FAST to make the code more readable and to piggy back on any optimizations Sitecore makes in the LINQ Provider.

If you have any tips, tricks or resources you want to share with the Guild or simply have a Sitecore question email me at sitecoreguild@outlook.com or chris.williams@threepointturn.com

The security settings for the current language prevent you from seeing this item. To continue, select another language from the Language drop-down list on the Versions tab.

I saw a few blog posts on this error but took me a while to figure out what the real solution was.  Here is a description of the error and how to resolve it.

Problem: A user is assigned access to edit content in the Content Editor but when they click on an item to edit they get the following error:

The security settings for the current language prevent you from seeing this item.
To continue, select another language from the Language drop-down list on the Versions tab.

Reason: In the content editor on the Master database there is a folder  at /system/languages
This folder has a new security key called language:read and language:write.  By default this is assigned to sitecore\everyone.  This is fine provided that only local users are accessing the content editor but if you are using ad domain\everyone will be default be denied.

Solution: Click on security and access viewer.  Navigate to /system/languages.  click on assign and assign the {your domain}\everyone access to language:read and language:write.   If you want to do this for a specific language you can open the folder click on the language and set these access properties there.

Sitecore - Getting Started Tips

Last night was the Toronto Sitecore Users Group meeting and I noticed there are were a lot of people just starting out with Sitecore. I figured it would he helpful if our first Sitecore Guild blog post assisted some of those beginners. If you have any additional tips for beginners feel free to comment on this post.

1) Take the Sitecore Training. If you have not been trained
on Sitecore, you will miss a lot of key concepts that will
hinder the success of your project. I know from experience.

2) Set up Sitecore to support multiple domains at the start.This will help you later when you want another site to share content.

Planning for shared content across sites will force you into the mindset
of shared content and code. This will help you on future projects too.

NOTE: In newer versions of Sitecore use an app.config file for each site to store the site mapping and other site specific settings. This will simplify upgrading.

Configuring Multiple Sites / Configuring Sites in web.config File

Read Watch Create has developed a free MultisiteQuickStart. If interested email chris.williams@readwatchcreate.com


3) Remember not all data needs to be in the CMS. Sometimes
data such as billing information do not need version control
or publishing rules. It is better to leave these items in
the database where they belong.

4) Wildcard content items are your best friend.
You may run into situations where you have content that is not in the content tree but you still want friendly urls not query strings.
It may not live in the CMS either because of tip 2 or because the data is coming from an external source

The solution is to place a * node below a node to accept all urls below it. Then instead of parsing a query string you would parse an url
for the data.

Here is the link and a brief note on wildcard nodes:

Sitecore Avoiding Query String In Dynamic Url

5) Resource Strings are content.
Store all your static string in the Content Tree as ResourceStrings.
This is a shift from standard .net where your resource strings would be
compiled in a resource file. By doing this, resource strings can be changed
by a content editor. Additional languages, in most cases would not require a recompile.

UPDATE: Check out this blog post for more information on the Resource String Module in the Sitecore MarketPlace

6) Keep common functionality together.
In the database, layouts, sublayouts, renderings exist in different nodes in the site but
In the physical folders, if you keep all the items related to a given folder you can more easily
package them up for another project. You never know when you can reuse a component.

I set up my physical folders as follows:

components\classes
components\dataproviders
components\Layouts
components\SubLayouts
components\Renderings
components\webcontrols
components\{modulename}\classes
components\{modulename}\dataproviders
components\{modulename}\Layouts
components\{modulename}\SubLayouts
components\{modulename}\Renderings
components\{modulename}\webcontrols
{sitename}\\classes
{sitename}\\dataproviders
{sitename}\\Layouts
{sitename}\\SubLayouts
{sitename}\\Renderings
{sitename}\\webcontrols

This keeps all the general items together, the module specific and the site specific in their proper places.

7) Find it before trying to build it.
Sitecore developer love to share. Through trac and the Developer Network you will find a wealth of shared source you can simply use.

UPDATE: Sitecore MarketPlace provides a vast amount of modules and developer starting points to help you get started on development rather than starting form scratch.

You can also find cookbooks that will tell you step by step how to accomplish common tasks. Unless you are implementing
something really specific, you are likely to find
a solution with source code that will either solve your exact problem or at least are a good starting point.

http://sdn.sitecore.net

8) Get Help from others.
If you are doing your first Sitecore project, don't be afraid to partner up with someone who has already done one. Sitecore gives you the illusion that it is easy to start a site but there is an initial learning curve. A partner that has been through even a single project could
help you avoid common pitfalls that could save you lots of time on your project.

9) Pay it forward.
When working on your solutions, if you do have to write a custom module but feel its generic enough to help other developers later. Share it.
The more we share the stronger Sitecore gets and the more productive we get as a community.

10) Connect with other Sitecore Developers.
A good way to do this is through going to the User Group Meetings, joining the Sitecore Facebook Groups and connecting to each other
on various Social Networks to share.

11) Check out the Sitecore QuickStart Blog Series
I have recently started a blog series called Sitecore QuickStarts.  This series provides a step-by-step guide through setting up your Sitecore development environment, your Sitecore Instance and guide you on your way to a successful implementation.

Twitter is underrated as a knowledge base. The Toronto Sharepoint Users Group developed the concept of placing @TSPUG on posts. Instead of posting where they were, they posted a quick comment or question and a link to answers.

I have started up a twitter account for the Sitecore Guild at https://twitter.com/SitecoreGuild
Please connect on twitter and when you find cool things for sitecore post them and be sure to include @SitecoreGuild in the post so we can all find them.

I will be collecting some of them regularly and sharing them here with the guild as well.

If you have any tips, tricks or resources please share them on twitter, comment on a post here or email them to me at chris.williams@readwatchcreate.com