Now let's say that within the same example above, you have network users that speak spanish - and their language within the NetGen application is set to Spanish - in markets US, Canada and Mexico. Since the content has only been created in Worldwide/Default, and the Default is English, would they have access to the content? No they would not because content has not been created in their set language, therefore it would not be available. When creating the new context, Administrators can determine if the content is the same across all markets. If it is, then they simply can create the content in the language necessary. In this case, they would create the content in the context of Worldwide/Spanish. Once created, all users with their language set to Spanish would now have access to the content within the NetGen application.

Now, let's say that content within a market needs to be tailored to meet the requirements of that market. For example, let's say that the Market is Mexico and the language is Spanish. While content has already been created in Worldwide/Spanish, and users language is set to Spanish, users would have access to content created in Worldwide/Spanish. However, when content is created in the context of Mexico/Spanish - users that are set to Mexico/Spanish - will now view Market/Spanish specific content. This ability gives administrators the ability to tailor content that fits the needs of specific markets within a worldwide user base.

NetGen makes it possible for web pages to dynamically display corporate content or producer content without creating multiple web pages. This ability allows for a single page to dynamically display information based on if the url displays www, or if it displays the subdomain of a producer.

For example, let's say you create a web page called Contact Us, and the page url is www.yourcompany.com/contactus. An object, like a predefined region, will have been created for both Corporate and Producers. The Corporate Contact Us predefined region will have the corporate contact info in it. The Producer contact us predefined region info will have the Web Wizard: signature in it. Based on the url that the prospect goes to, Corporate's web page (www.yourcompany.com/contactus) will display the corporate contact information. A Producer's web page (www.subdomain.yourcompany.com/contactus) will display the producer's signature.

Objects such as templates, page layouts, and predefined regions can all be created and connected to Site Contexts allowing for dynamic content to be viewed.

Site Context Options:
None:  will automaticallly display on the page.
Corporate:  will display object content that is Corporate specific. The url will not have a subdomain in it
                      and will display Corporate object content.
Producer:  will display object content that is Producer specific. The url will have a subdomain in it in
                    order to display Producer object content.

Connecting an object to a site context is done anytime you want to display content that differs for both corporate and producers - while only building one web page. For example, you may have an About Us page on your website. On the corporate page, you may want the content to give information about the company. On the producer's page, you want the producer to be able to put in their own customized information. In this case you build a predefined region with the company's content and in the predefined region details, connect it to the Corporate Site Context. You connect the already created Web Wizard: My Text to the Producer Site Context. Both predefined regions will be added to the About Us page.  

When a prospect goes to www.yourcompany.com/aboutus - they will view the predefined region connected to Corporate.
When a prospect goes to www.subdomain.yourcompany.com/aboutus - they will view the predefined region connected to Producer, for the specific producer's web page they are visiting.

One web page, with dynamic content able to support producers within your network.

The NetGen application uses a algorithm when rendering content. Understanding "the Tree" will help you determine context creation when creating and sharing content.

Key Points:
Administrators
? Content created by Administrators in the group/group account is automatically created in
     Market/Language:Worldwide/Default
? Contexts are created when:
        A) Corporate web pages need to communicate in multiple languages.
        B) Users within your network speak a language other than your group default language
             and need content to support their efforts. Users
? A Users web page(s) will display content based on the market/language their account is set to.
? Users will only have access to content within the application that is in the context of their
     Market/Language.

The Tree is used when determining if existing content will be displayed to users within the NetGen system, based on the market/language, and how content is displayed on the worldwide web in the selected market/language. This helps determine actions needed for content creation and management.

Scenario:
An email message has been created by an Administrator in Worldwide/Default. Within the email message is an image, which also has been loaded in Worldwide/Default. The email has been shared to a permission group that has users in the United States, Canada and Mexico. Some users are set to English, while others are set to Spanish.

Question:Using the Tree below, will users with a language set to Spanish - have access to the email message that has been shared with their permission group?

TQ: Is there a Context that matches the User Account's Market and Language? No
TQ: Is there a Context for Worldwide/Language of the User Account? No
TQ: Is there a Worldwide/Default context? Yes.
TQ: Is the Default Language for the Worldwide Market equal to the Language of the
        User Account? No

Users with their language set to Spanish, will not have access to the email message.

Actions to take: Create the email message and image used in the email message in Worldwide/Spanish.