@akashdeepAEM I would recommend using the  https://developer.adobe.com/document-services/docs/apis/#tag/Html-to-PDF/operation/pdfoperations.htmltopdf. and then write the asset to the DAM using the Assets API / utilities.

@pm31415 In your question, you mentioned you wanted to create. structured content, so is the concept of authoring in AEM comes into picture.  But your earlier comment mentioned something else on the ability to do the data entry in preview or live site. Feel free to elaborate on your use case you are...

Try comparing the configuration files between the server where it is working and where it is not. Look at all the /deny rules in the /filter section.

@OsmanWa Instead of static URLs i would recommend, using the query parameters to do the filtering during the querying itself. Something like - /blogs?tag=tech&author=john&date=2025  The code would look like - // In your block's JS export default async function decorate(block) { const urlParams = n...

@ParvathiSo1 The root cause of your issue is that browsers cannot directly resolve bare module specifiers like @apollo/client. Unlike Node.js, which has a built-in module resolution system that understands npm package names, browsers require either:Relative paths (./, ../)Absolute paths (/)URLs (htt...

@SmrithiG1 Have you checked dispatcher log?  Is your servlet path resolving to required farm file which contains the /allow filter you mentioned above?

@manish2v1 Specific log files forwarding is not available through "LogForwarding" config as of now, but you can choose to discard the specific logs at your Splunk. Refer [0] for more details on the configuration required at your splunk to discard specific logs. [0] - https://docs.splunk.com/Document...

@pm31415 What do you mean -Authoring will have to be done in a preview mode (wcmmode=disabled) which isn't the ideal way Content authoring is done in Author in Edit mode and is the only way to author the content on a page. Your solution should be optimal enough for ease of content changes, performan...

@KuzubMK Did you check this? There seems to be a particular structure that the html page and its respective artifacts needs to be placed within a folder.  

@pm31415 I would recommend manage the page content through appropriate component authoring and write an exporter which can return the required JSON for the page. Now this JSON can be cached in the dispatcher and CDN based on the Cache-Control and /cache configurations in dispatcher. This way you do ...