User-Owned CMS Data

Built simple low-volume applications which use the CMS for user-specific datastore.

Use cases

• Built simple low-volume applications which use the CMS for user-specific datastore.

Examples;

• Small auction site

• Simple "purchased access" management, e.g. courses, videos, etc.

Not suitable for

• Large user bases ( CMS item limits

• Heavily trafficked sites ( API rate limits )

• Complex data structures ( but JSON might work )

Design & Architecture Notes

• Uses HF WF API to perform CRUD ops

• Lists are marked with custom attributes to designate

  • User-owned records

  • Behavior - remove | redact | readonly

• Defined UserID field in CMS to designate ownership

Security

CSRF token

Encryption options exist

Optimization

• Can use JSON on a per-user record for disparate data, ideally not large lists.

External Data Options