Allow PageAPI + GraphQL PageAPI take a content query

User Story

Right now, our page APIs require a user to pass a url in order to render a page. It would be great if a user could pass a lucene query to pull a page (or pages). If multiple pages are returned, we would return an array of page responses.

OR
If you are pulling back pageAssets/slugs when returning content, we could allow the layout properties to be accessed.

Anyway - it seems like we were right initially calling the page API "Layout as a Service" - headless customers often don't want pages, they want to use a pages layout to be pulled into another page as just a component. Having to query for that by URL can get messy/confusing.

Something like:

        page(query: "+path:/about-us/* languageId:1 +site:demo.dotcms.com", limit:10, offset:0, sortBy: "modDate desc") {
            _map
            urlContentMap {
                identifier
                modDate
                publishDate
                creationDate
                title
                baseType
                inode
               }
            layout {
                header
                footer
                body {
                    rows {
                        columns {

Acceptance Criteria

1. Allow page responses to be delivered using a query and not just a url
2. Allow multiple page responses to come back if multiple pages are requested.

Proposed Objective

Please Select

Proposed Priority

Please Select

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Start by tracing the PageAPI and GraphQL PageAPI entry points and how they currently accept a URL. Define how a Lucene content query, limit, offset, and sort should produce one or multiple page responses, then verify the implementation against the two acceptance criteria.