We are currently creating a large site using AEM 6.1 and will transfer hundreds of thousands of records from the old RDMS-based system to AEM JCR. We understand that the 1000+ node constraint does not apply to nodes of type nt: unstructured, but we restrict the constraint when using cq: Page nodes.
Our current site has the following structure:
/
├── blog/
│ ├── some-blog-post
│ └── another-post
└── articles/
└── some-article
└── another-article
└── ...
└── ...
└── ...
We have more than 6,000 articles in the article subtree, and we need to maintain a URL structure for a consumer-facing site. We use the classic interface, and we, of course, face performance problems when expanding the article folder in AEM Siteadmin. We could allow articles to be split into additional directories in Siteadmin, but we would have to maintain a flat structure for our URLs.
What is the best way to do this in AEM? We cannot do this in the dispatcher because the dispatcher does not have the ability to find out where to display the request in the JCR hierarchy.
source
share