We cant build WKND from scratch - it wont compile.
Our organisation uses episerver and has several commerce sites with around 50million page impressions a month. We have around 30 episerver developers.
As the CMS architect, I have been tasked with evaluating AEM. The content team want to be able to play with the author tool, and the WKND would be enough for starters.
Is there any way to get WKND up and running on a local dev machine from pre-compiled binaries or similar?
https://github.com/adobe/aem-guides-wknd/releases/tag/aem-guides-wknd-0.0.6 this repo mentions "CRX Page Manager" version, but the link is broken.
What is CRX Package manger, and does it have something which might help get WKND running on any machine?
== UPDATE 1 ==
Unfortuantely, the https://github.com/adobe/aem-guides-wknd/releases/tag/aem-guides-wknd-0.0.6 repo has no documentation or instructions how to use or install the package, but by complete accident I clicked on the "broken" "CRX package manager" link while I happened to have an author instance open, and I got this package manger I have not seen before. So I "imported" the aem-guides-wknd-all zip, and now when I look in the author instance sites area, I see an unpublished wknd site pages.
The next question, is how do I publish these pages (there is no publish option I can find), and, once published, how do I actually view the pages as a customer would? If I fire up the "publisher" copy of the jar, I just see the same thing as the author version - i.e. no website.
Solved! Go to Solution.
To Setup up a local development environment. You need a copy of Adobe Experience Manager to run on a developer’s machine.
For getting AEM License - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-developer-license/td-p...
To run WKND Reference Site on Local machine. Download aem-guides-wknd.all-0.0.6-classic.zip and upload it to local AEM instance using CRX Package Manager(You can only access it if your AEM instance is up and running)
Authoring & Publish Demo
Thanks, I got this far - I imported the wknd site into the locally running author instance. The next step I am struggling to find is how to setup replication to be able to actually view the site on the publisher.
That video you kind linked to says 2 things:
1) a site called we.retails is out of the box on the author and publisher. Mine was on neither. I have instaled "wknd Site" on author now.
2) It says that there is a default replication agent. My author had no replication agents defined.
Yes, I already tried to setup the replication by hand, as it doesnt come out of the box as the docs say it should. I had to guess the parameters should be, but when I hit "test connection" it says success.
Worryingly, it says success whether or not I have the publisher running.
I set the replication target to http://localhost:4503/bin/receive?slinkg:authRequestLogin=1 and user to be admin/admin. I had no idea what "Agent User Id" was, so left it blank. The replication has enabled set to true. Under triggers, I checked "on modification" and "on distribute". Again, all guesswork.
If i then open a random page, e.g. http://localhost:4502/editor.html/content/wknd/language-masters.html and select "publish" it says published successfully.
But there is no content on the publisher. It just gives 404 for every URL I have tried (and again, I have no idea what the actual site URL should be, so have made hundreds of guesses, including things like "http://localhost:4503/content/wknd/language-masters.html"
@nutmixI followed the same link and I got my pages replicated without any issue. Please have a look from the point "Configuring Replication for Multiple Publish Instances". The exact link for the same https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/replication.html...
I was able to view the pages from my publisher using http://localhost:4508/content/wkndmuzik/us/en/homepage.html
Also to view the page exactly as in author the whole project including the components and clientlibs and the bundles should also be published alongwith the content.