Home > Articles > Web Development

How Sitecore and the Modern CMS Follow the Object-Oriented Thought Process

Sitecore Development Certified Senior Developer Jon Upchurch discusses how Sitecore and other modern content-management systems follow an object-oriented approach to content. This approach conveys many benefits for developers and business users alike.
Like this article? We recommend


As a developer, I had the opportunity to work with a good friend, Matt Weisfeld, author of The Object-Oriented Thought Process, and now we spend a lot of time discussing objects. My career has led me to work with a content management system (CMS) in various well-established formats, and I've found that in general the approach of all of them is the same, regardless of the platform: They focus on the page. Content is loaded into a page from a content repository, design templates are based around the page, and so on.

This methodology has worked for more than a decade, but I've always felt that this approach was forced, based purely on business requirements. From a publishing standpoint, this approach makes perfect sense, but from a development standpoint it feels like a legacy approach. However, pragmatism trumps principle, and I continued developing in the same manner, blissfully unaware that alternative products were gaining popularity in the market, and these alternatives provided a new solution that would appeal to business users who were less tech-savvy, as well as to object-oriented developers like me.

For a while, I'd been hearing about Sitecore from other web developers, as well as in job interviews, discussion forums, and even from employers who were looking to expand into other markets. I didn't get a chance to work with it until about a year ago. I was immediately smitten.

Sitecore probably isn't the first content management system to use this approach, but it was the first to which I was exposed. I've since encountered a few other products that take a very similar approach, but I'm still in love with Sitecore. For simplicity's sake, I'll use Sitecore as my example for the rest of this article, but these ideas aren't necessarily limited to Sitecore.

In my experience, the biggest problem with the page-based approach has always been that it doesn't scale well. To do e-commerce or interact with a CRM, ERP, or some other business system, you need a completely different approach. You can't simply treat a customer profile or a set of product information as more content…can you?

An Object-Based Approach

Instead of thinking of content and data separately, Sitecore treats content as data. This simple paradigm was incredibly liberating to me as a developer, and it resonated with my approach to the rest of my development work. In Sitecore, everything that's displayed (and most of what isn't) comes from data templates. A simple bit of text, a blog, a product catalog—all are derived from data templates.


Data templates are a collection of typed fields, as well as the methods and rules for interacting with them, defining how the data is stored and modeled in the content tree. The template acts as a class that defines the data and its structure. These templates define rules about the type of data, format of the content, and where the content items they map out can be used. While not quite to the level of encapsulation, the data template is pretty close. The presentation of data is separate from the data itself, and rules can be set up per field to describe where the data comes from and how the content will be validated.


Content items (objects) can reference other content items (composition) and can inherit from other templates, deriving standard values and behaviors from their ancestors. Templates can be treated like anything in the spectrum from interface to concrete class, and can easily be extended by or extend from other templates. Content items can either use default values provided by their parent templates, or override them at the template or item level. Additionally, changes to an item are stored as template deltas, which allow changes to the parent template to be reflected in the child items without affecting the changed fields.


The display of content items can change, depending on the context in which they are referenced. If they're viewed from a parent item, they can be configured to be rendered one way; but when addressed themselves, they can be rendered in a different way. Templates that inherit from other templates can inherit the parent template's behaviors or override them. Presentation rules inherit from parents, and with a little bit of code can be set up to use the template deltas as well. This means that general content can be rendered at the base template level, and additional content can be rendered at the child content level (or overridden entirely). This design allows for a very powerful and modular approach to displaying content.


My instinct when working with other content management systems was always to start looking at layouts first: "What kind of content will I have to display, and how must I arrange it on the page?" In Sitecore, the opposite is true. My first thought now is, "What will the structure of my data be, and how can I model that in Sitecore?" Whereas other content management systems would have me interfacing with a DBMS to create tables to model my data, in Sitecore I can work in the same content tree that the business users use. This is a wonderful thing: Your business users can see an immediate visual model of the data as they're working with it, and you can give them the power to create, edit, update, and publish new data directly!

With the data defined, you can unleash the content authors and editors to work on creating content items—the concrete versions of the templates. The next object-oriented parallel is in the presentation. You define your layout mostly as a canvas on which to render content, similar to a template/skin/theme in a traditional CMS. Then, depending on what content is addressed by the browser and what type of device is addressing the content, the content is rendered according to the configuration and its developed sublayouts and renderings. If you're referencing a URL to an item with children from a print layout, the children can be listed in a way that's friendly to a printer. If you reference one of those children directly from a mobile device, it might display differently. The framework handles the context; the developer just handles the implementation.

Object Orientation in Practice

From a developer's point of view, the Sitecore approach is comparable to other familiar designs. What are the benefits for business users? The biggest benefit is the fact that all the data/content is immediately accessible in an intuitive way. Although the data lives in a database, no special tools are required to access it, and even product data can be readily managed in the same system as marketing content. Marketing and business content all have structure, so the consistency of presentation and format of data are improved. Data becomes far more searchable, including facets for specific parts of the data—not just the content in general. Because it's extremely easy to associate custom metadata to content, you can leverage that metadata with the power of search indexers like Apache Lucene or Solr.

Another benefit to modeling data and content in this way is that templates can serve as a middle ground between business users and developers. No developer should expect a business user to think of things in terms of string, float, integer, and object, but we can talk to them in terms of plain text, rich text, number, link, and so on. This fact allows for easy collaboration between developers or business analysts and business users to model relevant data effectively. It becomes a lot easier to visualize data when it's easily examined in the content tree.

Wrap Up

This type of solution might not be practical for every scale of project. Sitecore isn't economical for small sites, although Umbraco uses a similar model and is a popular open-source alternative to Sitecore. Any similar solution will be a bit more invested in the front end of a project, making it less attractive for smaller projects. The strength is how well these solutions scale to larger projects, where the model really becomes efficient both for development and for business users to maintain the data. Just as in cases where a structured programming approach is more suitable than object-oriented programming, this kind of solution isn't ideal for a simple blog or brochure site, but it's a good tool for a developer or business user to have, especially at the enterprise level. When evaluating solutions, consider whether the content and data would benefit from an object-oriented approach.


• Matt Weisfeld, The Object-Oriented Thought Process, Fourth Edition

Sitecore CMS

Umbraco CMS

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020