Admin: Change tracking and publishing

[eirikurn]

Tux Admin should track changes (outside the adapter). For now, changes should be stored in memory or localstorage, but in the future we might want to sync these changes to some cloud service.

Changes appear in the edit bar on the bottom, which has a button to publish the changes, and a way to list and revert changes. Adapters should provide a friendly name for the model and a title for each instance.

When editing a whole model, the modal should have 3 buttons: Cancel, Preview and Publish. Clicking Publish save all model changes to the adapter. Clicking Preview tracks the changes locally, closes the modal and updates the page to reflect the changes. These changes can be published by clicking the button in the edit bar, or opening the modal again.

When clicking the edit button, tux should toggle between showing published and non-published data.

Questions:

• Should edit bar list all changed sub-models or just the parent model (eg sections of an article)?
• How granular should change tracking appear in the edit bar? Field level, or model level?
• Conflict tracking: Always override with local changes? Prompt user to use server changes or local changes? Apply to whole model or per field?