Implement Sitecore without a proper architecture, and you’re just asking to fail.
A proper Sitecore Architecture starts with a comprehensive document, developed by Sitecore experts who know how to create a pleasant experience both for the website visitor and the content editor. They know how to translate designs into re-usable components following Sitecore Helix principles and development best practices. These experts understand the software development lifecycle, and how to balance your technology needs and your business goals.
Our team of Sitecore Architects has over a decade of experience planning large-scale implementations. We believe that the success of any project depends on the quality of the technical architecture done at the beginning. We’re ready to help you get your implementation project started off on the right foot.
We’ll start by reviewing the wireframes and designs provided which outline the intended look and feel of key aspects of your site. Based on these we identify the key page types and design patterns that can be translated into individual content modules to be used on the site.
During discovery, we’ll lead a discussion with your team to understand other key aspects of the project such as other Sitecore functionality you intend to incorporate, specifics around how various components work, and any specific needs your content editors may have. Some of the information we’re sussing out may include:
- Differentiating between content that is specific to a type of page vs content that appears across page types.
- For design patterns that appear on multiple pages, will the content developed belong solely to one page or will some of the content appear in various parts of the site? Testimonials, for example are typically the same content, but displayed in multiple places.
- Are there any key relationships between different content types? Products and Resources for example?
- Will your Sitecore solution require additional functionality, such as search, Salesforce integration, or multi-language support?
- Will any personalization be applied now or in a future phase? Is there an outline of how and where that may be applied already?
- What level of technical knowledge will your content editors have? For specific modules, will flexibility or standardization be more important?
- Which team members need access to the CMS, will different members need access to different types of content? Is there a need for review and approval of content?
Based on our findings, we’ll put together a detailed Sitecore Architecture Document. This defines the building blocks in Sitecore that will be used to create the site - including layouts, renderings, and data templates. This vital piece of documentation serves as ground zero for your implementation, outlining how your content will be structured, what pages and modules will be created, and how content will be editable within Sitecore.
With buy-in from you and all the necessary stakeholders, a solid Sitecore Architecture Document ensures that everyone is on the same page, and on board with the plan—from brainstorming to launch.
Engagency is here to serve and we’re happy to help. Set up a time to talk with us now.
Choosing a CMS? 10 Things to Consider
Do you feel like you're falling behind? Your website just isn't keeping up? You sound like you're ready for a digital transformation. The first step to a successful transformation is implementing a CMS. Here's 10 things to consider when exploring your content management system options.
Engagency CEO Featured in Authority Magazine
Jason Perry, CEO of Engagency shares some thoughts on leadership with Authority Magazine
6 Signs You Need a DAM
75% of decision makers are implementing Digital Asset Management (DAM). Not sure your organization needs one? Think again. Here are 6 key signs you need a DAM.