It is done by overlaying page component and modified the meta tags in page.html.

I am trying to do the local setup for xwalk project. I have completed the following steps:1. Running AEM instance in https mode.2. Running Universal Editor Service locally on port 80003. "aem up" in port 30004. created a site using "site from template"...and finally I have added the following meta t...

Hi @ShaileshBassi  Consider If we want to create two sites namely, "pocfeature1site" and "pocfeature2site", when we use "Create Site Config" Admin API, shall we mention the URLs as follows:  first site : "url": "{{author_host}}/bin/franklin.delivery/{org}/pocfeature1site/main" second site : "url"...

I wanted to create a site "pocfeature2site" using "create site config" Admin API. In Payload, I have mentioned the content as follows : "content": { "source": { "url": "https://author-blabla-.adobeaemcloud.com/bin/franklin.delivery/%7Borgname%7D/pocfeature2site/poc-feature2", "type": "markup", "suff...

1. We have to get the administrator privilege from Adobe to create the organization2. We have to mention Authorization as No Auth and In Headers, we have to add x-auth-token while creating the site.

yes this is the official documentation for repoless approach.. But when i try to create organization using admin api, it throws 401-unauthorized error. I tried again with x-auth-token header. Now I am getting 403-forbidden error.

Hi @ShaileshBassi I did the same and I have copied the auth_token cookie from application tab and pasted it in Authorization part of Postman client.  It got reflected on Headers part as shown in the below screenshot:But I am getting 401-unauthorized only.

Thanks @ShaileshBassi I'll try this solution. But before that, as per the documentation, we have to create the organization first. I have downloaded the Admin API postman collection and configured it. Authorization part is little confusing here. I have logged in using https://admin.hlx.page/auth/ado...

 I want to leverage the repo less approach for my new EDS cross walk project, where four developers will be working collaboratively. Each developer will create their own feature branch in GitHub. Before merging their changes into the dev branch, they need to test their individual features separately...

Hi @kautuk_sahni @arunpatidar Sorry for late reply. Yes this is the correct answer. We are unable to access configurations and headers directly. I attempted to set cache-control headers for certain pages in my project, but they were not applied. Adobe has confirmed that, due to the product's design ...