All Projects → adobe → aem-spa-project-archetype

adobe / aem-spa-project-archetype

Licence: Apache-2.0 license
Maven Archetype for creating new AEM SPA projects

Programming Languages

CSS
56736 projects
typescript
32286 projects
javascript
184084 projects - #8 most used programming language
HTML
75241 projects
groovy
2714 projects

Projects that are alternatives of or similar to aem-spa-project-archetype

Aem Links
Adobe Experience Manager links, cheat sheets and solutions to common problems.
Stars: ✭ 254 (+296.88%)
Mutual labels:  adobe, aem
aem-spa-component-mapping
Provides a way to map Single Page Application front-end components with Adobe Experience Manager resource types.
Stars: ✭ 20 (-68.75%)
Mutual labels:  spa, aem
Aem Project Archetype
Maven template to create best-practice websites on AEM.
Stars: ✭ 337 (+426.56%)
Mutual labels:  adobe, aem
Aem Core Cif Components
A set of configurations and components to get you started with AEM Commerce development
Stars: ✭ 60 (-6.25%)
Mutual labels:  adobe, aem
commerce-cif-connector
AEM Commerce connector for Magento and GraphQL
Stars: ✭ 42 (-34.37%)
Mutual labels:  adobe, aem
AEM-DataLayer
Simple DataLayer API for Adobe Experience Manager
Stars: ✭ 33 (-48.44%)
Mutual labels:  adobe, aem
Tools
Tools to support development, testing and deployment of Marketing Cloud technologies
Stars: ✭ 94 (+46.88%)
Mutual labels:  adobe, aem
aem-cif-project-archetype
Maven template to create new CIF Project AEM projects that follow best practices
Stars: ✭ 20 (-68.75%)
Mutual labels:  adobe, aem
aem-touch-ui-validation
AEM Touch UI Validation Library
Stars: ✭ 40 (-37.5%)
Mutual labels:  adobe, aem
aem-react-editable-components
SPA React Editable Components for Adobe Experience Manager
Stars: ✭ 43 (-32.81%)
Mutual labels:  spa, aem
cookbook-cq
Chef cookbook for Adobe CQ (aka AEM)
Stars: ✭ 20 (-68.75%)
Mutual labels:  adobe, aem
aem-docker-getting-started
Getting started guide for development with Adobe Experience Manager and Docker.
Stars: ✭ 38 (-40.62%)
Mutual labels:  adobe, aem
aem-spa-page-model-manager
Interface between Adobe Experience Manager and Single Page Application framework.
Stars: ✭ 26 (-59.37%)
Mutual labels:  spa, aem
commerce-cif-magento-graphql
Magento GraphQL data models and query builders for AEM
Stars: ✭ 20 (-68.75%)
Mutual labels:  adobe, aem
ovid-editor
Adobe panel providing the most advanced scripting environment possible -- Typescript, app DOM autocomplete, full I/O features and more
Stars: ✭ 43 (-32.81%)
Mutual labels:  adobe
xd-storage-helper
A little helper to make storing key-value-pairs (e.g. settings) for Adobe XD plugins easier.
Stars: ✭ 22 (-65.62%)
Mutual labels:  adobe
modern-webpack-starter
🏰 A modern JavaScript starter using Webpack 4. Made in a simple way - good for learning or starting a new project without having to rollout cli-auto-builders.
Stars: ✭ 42 (-34.37%)
Mutual labels:  spa
openspa
OpenSPA - An open and extensible Single Packet Authorization (SPA) protocol
Stars: ✭ 49 (-23.44%)
Mutual labels:  spa
plugin-toolkit-react
Adobe XD plugin UI components for React
Stars: ✭ 30 (-53.12%)
Mutual labels:  adobe
Cloud-PAW-Management
Simplify PAW and SPA for the masses, unify the MS Internal, and public PAW specs, and expedite deployment to ~5min or less.
Stars: ✭ 45 (-29.69%)
Mutual labels:  spa
---

**IMPORTANT:** The SPA archetype has been merged into the [AEM Project Archetype](https://github.com/adobe/aem-project-archetype). This repository is no longer maintained.

---

AEM SPA Project Archetype

This archetype creates a minimal Adobe Experience Manager project as a starting point for your own SPA project.

See the WKND Events Tutorial on the Adobe Help Center website for an example of how to use it.

Usage

Requirements

  • Java 8 or higher
  • Maven 3.5 or higher
  • AEM 6.4.7+ or 6.5.3+

Generating a project

Run the following command to generate a project from the archetype:

mvn archetype:generate \
  -DarchetypeCatalog=remote \
  -DarchetypeGroupId=com.adobe.cq.spa.archetypes \
  -DarchetypeArtifactId=aem-spa-project-archetype \
  -DarchetypeVersion=4.0.0

Maven will prompt you for the following parameters:

  • projectTitle: Descriptive project name (e.g. My App)
  • projectName: Technical project name, used for building AEM paths (like /content/${projectName}/en, e.g. myapp)
  • groupId: ID which uniquely identifies your group and project, should start with a reversed domain name you control (e.g. com.mycompany)
  • optionFrontend: Frontend framework to use in the generated project (either angular or react)

See archetype-metadata.xml for the full list possible parameters.

Documentation

Development

Building

To make modifications to this archetype and use it locally, follow these steps:

  1. Clone the repository: git clone REPO_URL
  2. Navigate into the project directory: cd aem-spa-project-archetype
  3. Switch to the development branch: git checkout development
  4. Add the archetype to the local archetype catalog: mvn clean install archetype:update-local-catalog
  5. Navigate into a different directory where you want to generate a project from the archetype
  6. Update the list of locally available archetypes: mvn archetype:crawl
  7. Generate a project from the local archetype:
mvn archetype:generate \
  -DarchetypeCatalog=local \
  -DarchetypeGroupId=com.adobe.cq.spa.archetypes \
  -DarchetypeArtifactId=aem-spa-project-archetype \
  -DarchetypeVersion=4.0.1-SNAPSHOT

Docs

Contributing

Contributions are welcome! Read the Contributing Guide for more information.

Releasing

To create a release and have CI deploy it to the Central Repository, follow these steps:

  1. Decide on the version number of the new release (e.g. v1.2.3)

  2. Update the archetype:generate commands in this README file with the new version number (so users install the latest version of the archetype)

  3. Run the following commands to create the release. If the tests pass on CI, this will deploy the project to OSSRH and automatically release it to the Central Repository:

    NEW_VERSION="1.2.3"  # Replace with your version number
    
    # Update the version in all POM files
    mvn versions:set -DnewVersion=$NEW_VERSION
    
    # Commit and tag the change
    git commit -am "v${NEW_VERSION}"
    git tag "v${NEW_VERSION}"
    git push && git push --tags
  4. After successfully creating the release, create a new snapshot version which will be used for further development:

    # Increase and add "-SNAPSHOT" to the version number in the POM file
    mvn versions:set -DnextSnapshot
    
    # Commit the changes
    git commit -am "Prepare next development iteration"
    git push
  5. Update the changelog on the Releases page

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].