Experience Editor support AND headless?
We're using Sitecore 9 for a greenfield project. One of the topics of discussion is whether or not we want to use EE vs. Headless. I'm not going to ask the pros vs cons of using one over the other, I have experience and done plenty of reading on that.
However, from my reading on JSS, it would seem that it's possible to have a mix of the two if you so desired. Some parts could have full EE support, but some parts can be completely headless if desired. Is that right, or is there something I'm missing that would prevent this?
experience-editor jss
add a comment |
We're using Sitecore 9 for a greenfield project. One of the topics of discussion is whether or not we want to use EE vs. Headless. I'm not going to ask the pros vs cons of using one over the other, I have experience and done plenty of reading on that.
However, from my reading on JSS, it would seem that it's possible to have a mix of the two if you so desired. Some parts could have full EE support, but some parts can be completely headless if desired. Is that right, or is there something I'm missing that would prevent this?
experience-editor jss
add a comment |
We're using Sitecore 9 for a greenfield project. One of the topics of discussion is whether or not we want to use EE vs. Headless. I'm not going to ask the pros vs cons of using one over the other, I have experience and done plenty of reading on that.
However, from my reading on JSS, it would seem that it's possible to have a mix of the two if you so desired. Some parts could have full EE support, but some parts can be completely headless if desired. Is that right, or is there something I'm missing that would prevent this?
experience-editor jss
We're using Sitecore 9 for a greenfield project. One of the topics of discussion is whether or not we want to use EE vs. Headless. I'm not going to ask the pros vs cons of using one over the other, I have experience and done plenty of reading on that.
However, from my reading on JSS, it would seem that it's possible to have a mix of the two if you so desired. Some parts could have full EE support, but some parts can be completely headless if desired. Is that right, or is there something I'm missing that would prevent this?
experience-editor jss
experience-editor jss
edited 2 hours ago
Mark Cassidy♦
17k43480
17k43480
asked 2 hours ago
Frank RosarioFrank Rosario
1314
1314
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
As long as your app is capable of server-side rendering (SSR) then you can render it on a Sitecore CM server and use Experience Editor (EE) to edit it.
Beyond that, your app can live on a Node.js server somewhere (separate from Sitecore) and consume Layout Service data for rendering.
That said, you are not able to use Experience Editor in a headless fashion. In other words, Experience Editor requires a Sitecore instance.
The Application Modes section of the JSS docs might provide further insights: https://jss.sitecore.com/docs/fundamentals/application-modes
Essentially, your app would run in Integrated Mode on the CM server in order to enable EE management. Then you could use either Headless SSR Mode or API only mode to run your app headlessly. With your app fetching Layout Service data from a Sitecore CD.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "664"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f16237%2fexperience-editor-support-and-headless%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As long as your app is capable of server-side rendering (SSR) then you can render it on a Sitecore CM server and use Experience Editor (EE) to edit it.
Beyond that, your app can live on a Node.js server somewhere (separate from Sitecore) and consume Layout Service data for rendering.
That said, you are not able to use Experience Editor in a headless fashion. In other words, Experience Editor requires a Sitecore instance.
The Application Modes section of the JSS docs might provide further insights: https://jss.sitecore.com/docs/fundamentals/application-modes
Essentially, your app would run in Integrated Mode on the CM server in order to enable EE management. Then you could use either Headless SSR Mode or API only mode to run your app headlessly. With your app fetching Layout Service data from a Sitecore CD.
add a comment |
As long as your app is capable of server-side rendering (SSR) then you can render it on a Sitecore CM server and use Experience Editor (EE) to edit it.
Beyond that, your app can live on a Node.js server somewhere (separate from Sitecore) and consume Layout Service data for rendering.
That said, you are not able to use Experience Editor in a headless fashion. In other words, Experience Editor requires a Sitecore instance.
The Application Modes section of the JSS docs might provide further insights: https://jss.sitecore.com/docs/fundamentals/application-modes
Essentially, your app would run in Integrated Mode on the CM server in order to enable EE management. Then you could use either Headless SSR Mode or API only mode to run your app headlessly. With your app fetching Layout Service data from a Sitecore CD.
add a comment |
As long as your app is capable of server-side rendering (SSR) then you can render it on a Sitecore CM server and use Experience Editor (EE) to edit it.
Beyond that, your app can live on a Node.js server somewhere (separate from Sitecore) and consume Layout Service data for rendering.
That said, you are not able to use Experience Editor in a headless fashion. In other words, Experience Editor requires a Sitecore instance.
The Application Modes section of the JSS docs might provide further insights: https://jss.sitecore.com/docs/fundamentals/application-modes
Essentially, your app would run in Integrated Mode on the CM server in order to enable EE management. Then you could use either Headless SSR Mode or API only mode to run your app headlessly. With your app fetching Layout Service data from a Sitecore CD.
As long as your app is capable of server-side rendering (SSR) then you can render it on a Sitecore CM server and use Experience Editor (EE) to edit it.
Beyond that, your app can live on a Node.js server somewhere (separate from Sitecore) and consume Layout Service data for rendering.
That said, you are not able to use Experience Editor in a headless fashion. In other words, Experience Editor requires a Sitecore instance.
The Application Modes section of the JSS docs might provide further insights: https://jss.sitecore.com/docs/fundamentals/application-modes
Essentially, your app would run in Integrated Mode on the CM server in order to enable EE management. Then you could use either Headless SSR Mode or API only mode to run your app headlessly. With your app fetching Layout Service data from a Sitecore CD.
answered 2 hours ago
Adam WeberAdam Weber
1,017210
1,017210
add a comment |
add a comment |
Thanks for contributing an answer to Sitecore Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f16237%2fexperience-editor-support-and-headless%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown