crikke / cms

Big money cms

YO

cms's Issues

Create content from ContentDefinition

When saving content validation should not be run, this because content which fails validation is still allowed to be saved.
Saving content should only return HTTP 401 depending on if the user has sufficient rights to save content.

Validation is done when publishing content and returns HTTP 400 if validation fails or HTTP 401 if user is not allowed to publish content

UI

1. Get ContentDefinition
2. Get all PropertyDefinitions for given Contentdefinition
3. Set Property Fields

Creating new content should only require ContentDefinitionID,

Up

Todo

• Save ContentName localized
• Match and validate content fields with PropertyDefinitions

PropertyDefinition Validation

Rules

• Required
• Regex
• Range

Tests

• Range
• Rexeg
• Required

Commands

• Create rule
• Update rule
• Delete rule

Queries

• Get rule
• Get all rules

Bad structure in codebase, Contentdelivery & management, contentdefinition

Should Contentmanagement/API & contentmanagement/App move from pkg to cmd maybe?

Contentdefinition Status

Status field on contentdefinition

When creating new contentdefinition it has status draft.
Content cannot be created from a contentdefinition with status Draft

• Published

• Draft

• /contentdefinition/{id}/publish

CQRS ContentLoader

You only save one version & locale of content at a time. So domain.ContentData can be simplified.
Same thing when editing content

Writes will have validation that has to be run

Authentication

firebase

Identity Manager

• https://github.com/ory/hydra
• Okta
• Auth0
• Google?
• Azure AD B2C
• Keyvault

Versioning,

• Fetch single content version from database instead of all versions and selecting the correct version in backend

Siteconfiguration - Should be remade into Workspace

Each workspace owns its data and should be a bounded context, there should not be any cross references between workspaces. Therefore, each workspace should have its own database.

One database for data across all workspaces:

• Should contain workspaces and their configuration

Each workspace has its own database:

• ContentTypes

Content Tags

• Add tags to model
• Query content by tags
• Query Tags
• PUT tag

Content Versioning - Refactor

//! TODO: instead of storing the versionnumber in PublishedVersion, store the actual version there.
//! This will always be the most frequent requested data and by doing this unnecessary logic to query the published version wont be needed.
//! Older versions should be moved to another collection since read speeds isn´t as important.
//! Obviously ContentVersion will need a version field.
//! This will also solve problem with status, since status will only be needed on ContentVersion and not Content

Site Configuration

Multiple instances of ContentManagement has read access. So needs synchronization

• ContentDeliveryApi: Read only
• ContentManagementApi: Write & Read

SiteConfiguration

• Configured Languages
• Root Page

Todo

• To synchronize siteconfig RabbitMQ is used.
• How to get siteconfig on startup?

AuthZ

Enforce that policies exist for given action
Example:
GET /content/foo,
In code check that there exist at least one policy for given action. In this case Read

• Persist policies in database

Refactor - Merge cmd/contentmanagement & cmd/contentdelivery

Should not be 2 different applications, instead mount contentdelivery route

Logging - Implement Prometheus

Just basic telemetry for v0.1.0

Backend & Frontend - each locale should be treated seperately

When editing content, each locale should be updated standalone. Different users should be able to have different access rights to locales.

So one user may edit sv_SE but not fi_FI.

OpenAPI spec

Site Configuration

Should contentmanagement be responsible for admin related tasks?

SiteConfiguration:

• Endpoint update languages

ContentType

Content & ContentDefinition are decoupled, when saving content it is Validated against the contentdefinition.
There is no need to version ContentDefinition because content can only be of the latest version of ContentDefinition.

Todo

• Queries

1. Fetch ContentType.
2. Edit Content
3. When publishing or saving draft, run validation

• If publishing and validation passes, set status published
• If validation fails or draft, set status draft.

4. Send Message that content has been saved with its status

ContentDeliveryApi

• Dockerfile
• Connect all middleware

API - Better error handling

https://stackoverflow.com/a/42876307