Content management
A content management system may support a card engine to dynamically perform operations such as configuring content for display via a user interface and generating reports based on user behavior, account status, and business logic. In cooperation with a facts controller to provide facts that the card engine may access substantively in real time, a rules engine to provide constructs in the form of card definitions, and a development engine, the content management system may enable a content manager to effect changes to card and container definitions by providing or modifying rules and rulesets in the rules engine dynamically. Cards evaluated dynamically by the card engine may be transmitted to user equipment. In this way, the content manager may make content decisions in accordance with business logic and events occurring proximate to the user, thereby impacting the user experience and generating reports in a substantive and real-time fashion.
1. A server, comprising:
one or more processors; and
memory to maintain one or more software components comprising instructions that are executable by the one or more processors, the one or more software components comprising:
a content management system configured to:
receive changes to relational metadata that describe content;
determine that a source of the relational metadata changes has sufficient access privileges to effect the relational metadata changes;
in response to determining that the source has sufficient access privileges to effect the relational metadata changes:
store the relational metadata changes in one or more relational databases;
form structured content that corresponds to the changes to the relational metadata and content described by the changed relational metadata;
record a version of the structured content; and
propagate the structured content to one or more mobile devices;
wherein the relational metadata are stored in a non-hierarchical configuration in the one or more relational databases.
2. The server of claim 1 , wherein the content management system is configured to:
enable a live preview of the structured content before being propagated to the one or more mobile devices;
receive an indication as to whether the live preview is accepted;
log a failure in response to receiving the indication that the live preview is not accepted; and
record the version of the structured content and propagate the structured content to the one or more mobile devices in response to receiving the indication that the live preview is accepted.
3. The server of claim 1 , wherein:
the one or more relational databases hold at least two tables that reference content;
the at least two tables are linked by the relational metadata;
the content referenced by the at least two tables is linked by the relational metadata; and
the changes to the relational metadata effect changes to the content in the structured content propagated to the one or more mobile devices.
4. The server of claim 1 , wherein the structured content is propagated as cards surfaced by a card engine.
5. The server of claim 1 , wherein the changes to the relational metadata include changes to access privileges.
6. The server of claim 1 , wherein the content management system is configured to:
store changes to the content in content storage;
wherein the structured content corresponds to the changes made to the relational metadata and the changes made to the content.
7. A computer-implemented method for managing content, comprising:
receiving changes to relational metadata that describe content;
determining whether a source of the relational metadata changes has sufficient access privileges to effect the relational metadata changes;
in response to determining that the source has insufficient access permissions to effect the changes, logging a failure; and
in response to determining that the source has sufficient access privileges to effect the relational metadata changes:
storing the relational metadata changes in one or more relational databases;
forming structured content that corresponds to the changes to the relational metadata and content described by the changed relational metadata;
recording a version of the structured content changes; and
providing, as the structured content, a report showing results from the relational metadata changes;
wherein the relational metadata are stored in a non-hierarchical configuration in the one or more relational databases.
8. The method of claim 7 , further comprising:
generating the report;
receiving an indication as to whether the generated report is accepted;
logging a failure in response to receiving the indication that the generated report is not accepted; and
recording the version of the generated report and providing the generated report as the provided report in response to receiving the indication that the generated report is accepted.
9. The method of claim 7 , wherein:
the one or more relational databases hold at least two tables that reference content;
the at least two tables are linked by the relational metadata;
the content referenced by the at least two tables is linked by the relational metadata; and
the changes to the relational metadata effect changes to the content in the structured content reflected in the generated report.
10. The method of claim 9 , further comprising:
propagating the structured content to one or more mobile devices as cards surfaced by a card engine; and
receiving feedback related to the surfaced cards;
wherein the report reflects the feedback.
11. The method of claim 10 , further comprising:
analyzing the feedback for user behavior related to the surfaced cards;
wherein the report reflects results of the analysis.
12. The method of claim 10 , further comprising:
analyzing the feedback for financial reporting data;
wherein the report reflects results of the analysis.
13. The method of claim 7 , further comprising:
storing changes to the content in content storage;
wherein the structured content corresponds to the changes made to the relational metadata and the changes made to the content.
14. A computer-readable storage medium comprising instructions that, when executed by one or more computing devices, cause the computing devices to implement a content management system to perform operations comprising:
receiving changes to relational metadata that describe content;
determining whether a source of the relational metadata changes has sufficient access privileges to effect the relational metadata changes;
in response to determining that the source has insufficient access permissions to effect the relational metadata changes, logging a failure; and
in response to determining that the source has sufficient access privileges to effect the relational metadata changes:
storing the relational metadata changes in one or more relational databases;
forming structured content that corresponds to the changes to the relational metadata and content described by the changed relational metadata;
recording a version of the structured content; and
propagating the structured content to one or more mobile devices;
wherein the relational metadata are stored in a non-hierarchical configuration in the one or more relational databases.
15. The computer-readable storage medium of claim 14 , wherein the operations further comprise:
enabling a live preview of the structured content before being propagated to the one or more mobile devices;
receiving an indication as to whether the live preview is accepted;
logging a failure in response to receiving the indication that the live preview is not accepted; and
recording the version of the structured content and propagating the structured content to the one or more mobile devices in response to receiving the indication that the live preview is accepted.
16. The computer-readable storage medium of claim 14 , wherein the operations further comprise:
generating, as the structured content, a report resulting from the relational metadata changes;
receiving an indication as to whether the generated report is accepted;
logging a failure in response to receiving the indication that the generated report is not accepted; and
recording the version of the generated report and providing the generated report in response to receiving the indication that the generated report is accepted.
17. The computer-readable storage medium of claim 14 , wherein:
the one or more relational databases hold at least two tables that reference content;
the at least two tables are linked by the relational metadata non-hierarchically;
the content referenced by the at least two tables is linked by the relational metadata; and
the changes to the relational metadata effect changes to the content in the structured content propagated to the one or more mobile devices.
18. The computer-readable storage medium of claim 14 , wherein the operations further comprise:
storing changes to the content in content storage;
wherein the structured content corresponds to the changes made to the relational metadata and the changes made to the content.