24 Results for Category Sitecore Experience Platform
Helix was introduced by Sitecore in 2016 as a set of official guidelines and recommended practices for Sitecore Development. Since then, the Sitecore community has been supporting the Helix initiative and many websites have been built using this approach. A well-known website that was built to demonstrate best practices of the Helix principles and guideline was Habitat.
Los Angeles, CA - XCentium today announced the launch and availability of their Flex Accelerator for Sitecore, a new SaaS solution offered as part of the Sitecore KickStart program. Designed specifically for mid-market organizations, Flex Accelerator for Sitecore enables Sitecore’s industry-leading digital experience platform to be deployed in a SaaS setting in as little as 30 days and at a starting price of $100,000 per year.
Flex Accelerator for Sitecore is home to several clients eager to use the new hosting model provided by the Sitecore KickStart program. Nexford University was the first to take advantage of the solution, with a new website built on Sitecore® Experience Platform version 9 only five weeks from hand-off to launch.
Los Angeles, CA — February 18, 2019 — XCentium, a full-service digital consultancy, today announced that 9 team members from XCentium have been awarded nine Most Valuable Professionals (MVPs) by Sitecore®, the global leader in digital experience management software. XCentium’s 2019 Sitecore MVPs are 9 of only 315 professionals worldwide to be named a Sitecore MVP this year.
This post is somewhat of a sequel to my previous one around multi-site and multi-language setup. When there is only one site and only one language things are pretty straightforward in terms of site context. Once multiple sites are introduced every time we are getting an item in Sitecore and/or building a link we need to make sure we do it within the correct site and correct language. For the most part Sitecore does it out of the box but there are cases when this functionality breaks down.
As a website evolves and its audience grows making your content available in multiple languages becomes a top priority. The most common way to achieve this goal is to use Sitecore's out of the box language versioning functionality where the tree is shared and the same item in can have translated versions. But what if it's not only your content that differs between various country sites but also presentation? What if your sites intended for various countries are independent from each other and possibly share some components but not all? What you can do is set up a site in such a way that tree is split between countries meaning each site has its own site definition with its own hierarchy.