Mixing
SXA or not SXA is the Question what are your experiences?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
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?
sxa sxa-storefront
edited Aug 28 at 8:09
Pratik Wasnik
307114
asked Aug 28 at 5:41
squadwuschel
2449
add a comment |Â
up vote
1
down vote
favorite
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?
sxa sxa-storefront
edited Aug 28 at 8:09
Pratik Wasnik
307114
asked Aug 28 at 5:41
squadwuschel
2449
1
I think this may generate opinionated answers. But in my experience I would not recommend any client to do a project without using SXA. It has been the single biggest jump to productivity and consistency in Sitecore ever... Sure there are nuances that can cause issues and its a mental shift in how you build, but once you have done a couple, you wont want to go back to standard Sitecore. I certainly don't
– Richard Seal♦
Aug 28 at 12:41
I would definitely give it a shot with SXA. It just rocks! Great set of components to begin with (and you create all over again to every customer and every project) and you can only focus on components that bring "business" value
– Peter Prochazka
Aug 28 at 14:10
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
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?
sxa sxa-storefront
edited Aug 28 at 8:09
Pratik Wasnik
307114
asked Aug 28 at 5:41
squadwuschel
2449
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?
sxa sxa-storefront
edited Aug 28 at 8:09
Pratik Wasnik
307114
asked Aug 28 at 5:41
squadwuschel
2449
edited Aug 28 at 8:09
Pratik Wasnik
307114
edited Aug 28 at 8:09
Pratik Wasnik
307114
edited Aug 28 at 8:09
Pratik Wasnik
307114
307114
asked Aug 28 at 5:41
squadwuschel
2449
asked Aug 28 at 5:41
squadwuschel
2449
asked Aug 28 at 5:41
squadwuschel
2449
2449
1
I think this may generate opinionated answers. But in my experience I would not recommend any client to do a project without using SXA. It has been the single biggest jump to productivity and consistency in Sitecore ever... Sure there are nuances that can cause issues and its a mental shift in how you build, but once you have done a couple, you wont want to go back to standard Sitecore. I certainly don't
– Richard Seal♦
Aug 28 at 12:41
I would definitely give it a shot with SXA. It just rocks! Great set of components to begin with (and you create all over again to every customer and every project) and you can only focus on components that bring "business" value
– Peter Prochazka
Aug 28 at 14:10
add a comment |Â
1
I think this may generate opinionated answers. But in my experience I would not recommend any client to do a project without using SXA. It has been the single biggest jump to productivity and consistency in Sitecore ever... Sure there are nuances that can cause issues and its a mental shift in how you build, but once you have done a couple, you wont want to go back to standard Sitecore. I certainly don't
– Richard Seal♦
Aug 28 at 12:41
I would definitely give it a shot with SXA. It just rocks! Great set of components to begin with (and you create all over again to every customer and every project) and you can only focus on components that bring "business" value
– Peter Prochazka
Aug 28 at 14:10
1
1
I think this may generate opinionated answers. But in my experience I would not recommend any client to do a project without using SXA. It has been the single biggest jump to productivity and consistency in Sitecore ever... Sure there are nuances that can cause issues and its a mental shift in how you build, but once you have done a couple, you wont want to go back to standard Sitecore. I certainly don't
– Richard Seal♦
Aug 28 at 12:41
I think this may generate opinionated answers. But in my experience I would not recommend any client to do a project without using SXA. It has been the single biggest jump to productivity and consistency in Sitecore ever... Sure there are nuances that can cause issues and its a mental shift in how you build, but once you have done a couple, you wont want to go back to standard Sitecore. I certainly don't
– Richard Seal♦
Aug 28 at 12:41
I would definitely give it a shot with SXA. It just rocks! Great set of components to begin with (and you create all over again to every customer and every project) and you can only focus on components that bring "business" value
– Peter Prochazka
Aug 28 at 14:10
I would definitely give it a shot with SXA. It just rocks! Great set of components to begin with (and you create all over again to every customer and every project) and you can only focus on components that bring "business" value
– Peter Prochazka
Aug 28 at 14:10
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
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.
answered Aug 28 at 7:37
Dawid Rutkowski
2,610221
add a comment |Â
up vote
3
down vote
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?
- Most importantly if your client is not budgeted to spend the 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.
- 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.
- 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.
- If there are possibilities that the Content finalization in your project will be delayed and can't be available in early phases of project.
- 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.
answered Aug 28 at 9:34
Amitabh Vyas
1,6291628
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
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.
answered Aug 28 at 7:37
Dawid Rutkowski
2,610221
add a comment |Â
up vote
3
down vote
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.
answered Aug 28 at 7:37
Dawid Rutkowski
2,610221
add a comment |Â
up vote
3
down vote
up vote
3
down vote
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.
answered Aug 28 at 7:37
Dawid Rutkowski
2,610221
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.
answered Aug 28 at 7:37
Dawid Rutkowski
2,610221
answered Aug 28 at 7:37
Dawid Rutkowski
2,610221
answered Aug 28 at 7:37
Dawid Rutkowski
2,610221
answered Aug 28 at 7:37
Dawid Rutkowski
2,610221
2,610221
add a comment |Â
add a comment |Â
up vote
3
down vote
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?
- Most importantly if your client is not budgeted to spend the 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.
- 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.
- 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.
- If there are possibilities that the Content finalization in your project will be delayed and can't be available in early phases of project.
- 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.
answered Aug 28 at 9:34
Amitabh Vyas
1,6291628
add a comment |Â
up vote
3
down vote
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?
- Most importantly if your client is not budgeted to spend the 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.
- 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.
- 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.
- If there are possibilities that the Content finalization in your project will be delayed and can't be available in early phases of project.
- 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.
answered Aug 28 at 9:34
Amitabh Vyas
1,6291628
add a comment |Â
up vote
3
down vote
up vote
3
down vote
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?
- Most importantly if your client is not budgeted to spend the 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.
- 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.
- 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.
- If there are possibilities that the Content finalization in your project will be delayed and can't be available in early phases of project.
- 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.
answered Aug 28 at 9:34
Amitabh Vyas
1,6291628
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?
- Most importantly if your client is not budgeted to spend the 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.
- 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.
- 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.
- If there are possibilities that the Content finalization in your project will be delayed and can't be available in early phases of project.
- 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.
answered Aug 28 at 9:34
Amitabh Vyas
1,6291628
answered Aug 28 at 9:34
Amitabh Vyas
1,6291628
answered Aug 28 at 9:34
Amitabh Vyas
1,6291628
answered Aug 28 at 9:34
Amitabh Vyas
1,6291628
1,6291628
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f13561%2fsxa-or-not-sxa-is-the-question-what-are-your-experiences%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
I think this may generate opinionated answers. But in my experience I would not recommend any client to do a project without using SXA. It has been the single biggest jump to productivity and consistency in Sitecore ever... Sure there are nuances that can cause issues and its a mental shift in how you build, but once you have done a couple, you wont want to go back to standard Sitecore. I certainly don't
– Richard Seal♦
Aug 28 at 12:41
I would definitely give it a shot with SXA. It just rocks! Great set of components to begin with (and you create all over again to every customer and every project) and you can only focus on components that bring "business" value
– Peter Prochazka
Aug 28 at 14:10