Hi - i want to implement a member portal using AEM with SPA Editor.
Members will need to be authenticated based on external identity
provider like Okta. To elaborate the case a bit,1. user will login via a
landing page. This page will be a pre-login page, where it'll just show
some about the company details. This we know we can implement in AEM
with an SPA editor mode as well.2. when user clicks login, he/she will
be redirected to an external IdP (Okta), to authenticate, upon
The issue is related to the SPA React package at build time. We used the
aem-project-archetype as the starting point. It included a ".env" file
in the ui.frontend folder to specify the environment variables for the
React app. The ".env" file is used to inject the environment variables
to the React app when the project is built (mvn clean install
-PautoInstallPackage --> npm run build). I have searched this forum and
found that some people pull the runmode via some hidden html but this is
not a d...
thanks @Vijayalakshmi_S @BrianKasingli in the case that my "When to use
SSR" answer is no, may i know whether i still need to use the ACS
commons sitemap generator to generate the sitemap (ie. is it even going
to work on SPA sites) or assume(hope) that the main search engine will
be able to evaluate the JS?
Hi we are implementing an SPA site with AEM 6.5+SPA editor, is there a
way to generate a sitemap to optimize for SEO? or is SSR a must? and if
SSR is a must, then using Adobe I/O also the recommended approach? with
my previous implementation with AEM 6.3, we used the ACS commons sitemap
for non SPA app. Would this still work for SPA?