User Story
As a Product Manager, I would like a database-like feature in DA, so we can access and maintain Page and Card Metadata Properties across multiple pages.
Acceptance Criteria
There are two scenarios to consider:
Read - for self-service reporting purposes
Write - for self-service bulk updates
Read
Authors and Product Managers can access this database to find Page Metadata properties
Authors and Product Managers can access this database to find Card Metadata properties
The list should contain the Page URL and the various properties associated with that page
Additional Context
Enabling the ability to read the database will allow Product Managers to quickly get a report of whats going on on their pages
This will also enable engineering to get out of the "run a script to produce a report" game and also standardize one of the ways we currently use our Query Index
Authors can write to this database and the update is reflected in the DA doc as well
Similar to AEM, maybe there is an ability to download a JSON, allowing authors to make changes to that JSON and then re-upload it with the changes reflected
Additional Context
Enabling the ability to Write to the database will get Engineering and Authoring out of "petty" bulk updates that take too long and require content freezes (i.e. "We need to update tag A to tag B across all our BACOM pages") - taking us from weeks to days.
User Story As a Product Manager, I would like a database-like feature in DA, so we can access and maintain Page and Card Metadata Properties across multiple pages.
Acceptance Criteria There are two scenarios to consider:
Read
Additional Context
Write
Additional Context