Dfyjkt

I am not sure if I should use SXA in my project. Currently we want to use only the XP but in the future we would like to use XC too.

• I think I need to create many components by my self because of the design wishes from the gui team




• When we later use the XC we only would use the item listings and not the checkout or user registering or the shopping cart.

So, currently I think its not worth the price and the additional starting time for my Sitecore website when I create a tenant and I am using not enough components out of the box.

Is it hard to create new SXA components?

Our current desission:

• we have decided not to use SXA in our sitecore project


• because its very expensive


• its hard to customize/extend existing SXA component with addional markup


• we want clear and simple components designed directly from us for us


• we have a lot unique controlls


• we are new to sitecore and its hard to learn how to use sitecore with helix pattern right. And with an other technologie stack in sitecore intself it seem hard to do it the right way because of the lack of documentation for SXA and Helix.

Faster time to market is not a preference, its a necessity now a days.

SXA is not just about its toolbox and pre-built components. Its about the entire SXA Website Development Process which help you to expedite the website development process.

In a non-SXA project you always have dependencies on the previous phase. Most importantly the Content Entry, this can never take place until all the phases e.g. User Experience, Visual Design, Front-End, Back-End are complete. Well there is a delta for the Backend development which can be overlapped with Content Entry but that is negligible. The Content Entry phase gets more bigger when you have Multi-site and Multilingual project to go live with.

Whereas if you are using SXA the Content Entry can start right from the Visual Design phase, when you are done with Wireframing. By Saying that when you will finish the Backend development, you will be having handsome amount of actual Content in place which also helps in more realistic testing compared with testing using Lorem Ipsum content (Which we normally do).

Additionally it also reduces your actual development time by using more than 100+ pre-built components. And most importantly if your designing/content/digital marketing team is skilled enough to work on Sitecore SXA, the time to market can be reduced tremendously. Plus everyone in your team like front end developers, content team and backend developers work consolidated on Sitecore utilizing the powers of SXA hence what all you can expect is a great outcome.

As David said, its not worth re-iterating all the features which SXA provides as you can find them on countless blogs and videos. Hence rather talking about Why Opt-In for SXA, let me list out few points on When and Why Opt-Out for SXA?

1. Most importantly if your client with Non-Subscription Model is not budgeted to spend cost on SXA Licensing. BUT in your research phase if you find that using SXA can save more money and time on your project, you can try to convincing the client to use SXA.


2. If you are not starting from the scratch, you are bound to follow the current theme being used by the existing solution (which is not a grid system) and you are not budgeted for the efforts to make the SXA site fit-in your existing solution.


3. Your front end and content team is not skilled enough to use Sitecore SXA and if you think user trainings for this project is not feasible due to time crunch.


4. If there are possibilities that the Content finalization in your project will be delayed and can't be available in early phases of project.


5. As you said if the design requirements of the components are more complex than the OOTB components and number is such custom components is higher. And if you think developing these custom components will be more easier than massaging the OOTB SXA components.

But believe me if you are good with these points you MUST use SXA. I mean its worth trying an Helix compliant platform bundled with good amount of pre-built components available by just drag-drop.

Of course, it is worth it! I will not write down all the features again as it was mentioned thousands of times on different blog posts. It's not just about the components which are shipped with SXA. There are much more features which will speed up your site development process drastically. Just a few articles from first Google results:

• The Benefits of Sitecore Experience Accelerator for Your Project


• SITECORE EXPERIENCE ACCELERATOR - A new way of building Sitecore websites


• Advantage of designs in #Sitecore Experience Accelerator

Regarding the components - believe me, you will not need to create a lot of custom ones. I think, that having 5 custom renderings that is already a huge number when you have SXA installed. Rendering Variants give you such a big flexibility that there is no need for creating custom renderings.