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.
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