Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

/conf suggestions

Avatar

Avatar
Boost 3
Level 2
Antony6790
Level 2

Likes

3 likes

Total Posts

21 posts

Correct Reply

1 solution
Top badges earned
Boost 3
Ignite 1
Give Back
Boost 1
Affirm 1
View profile

Avatar
Boost 3
Level 2
Antony6790
Level 2

Likes

3 likes

Total Posts

21 posts

Correct Reply

1 solution
Top badges earned
Boost 3
Ignite 1
Give Back
Boost 1
Affirm 1
View profile
Antony6790
Level 2

19-04-2021

Hi All,

 

Do we have to maintain /conf as code in GIT repo or control this folder access using ACL's? what is  the best practice ?

 

Even though we are in 6.5, we are not yet using Editable templates fully and just starated using Content Fragments.

 

Also planning to move AEM as cloud service in Q3.

 

Appreciate any suggestion on this.

 

Thanks.

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 100
Level 10
asutosh_jena
Level 10

Likes

560 likes

Total Posts

677 posts

Correct Reply

194 solutions
Top badges earned
Give Back 100
Boost 500
Affirm 100
Ignite 1
Establish
View profile

Avatar
Give Back 100
Level 10
asutosh_jena
Level 10

Likes

560 likes

Total Posts

677 posts

Correct Reply

194 solutions
Top badges earned
Give Back 100
Boost 500
Affirm 100
Ignite 1
Establish
View profile
asutosh_jena
Level 10

19-04-2021

Hi @Antony6790 

 

It is always best practice to keep the /conf in code i.e.using any source code management (git) and it will be deployed as part of the deployment package.

In AEM as CS, the ui.content package contains all content and configuration. The Content Package, contains all the node definitions not in the ui.apps or ui.config packages, or in other words, anything not in /apps or /oak:index.

  • Context-aware configurations
    • /conf
  • Required, complex content structures (ie. Content build-out that is builds on and extends past Baseline content structures defined in Repo Init.)
    • /content, /content/dam, etc.
  • Governed tagging taxonomies
    • /content/cq:tags
  • Legacy etc nodes (Ideally, migrate these to non-/etc locations)
    • /etc

 

Please refer the link here:

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem...

 

Also you can refer the wknd website which is implemented by following the best practices by Adobe:

https://github.com/adobe/aem-guides-wknd

 

Hope this helps!

Thanks

Answers (0)