# Strapi

JavaScript !== TypeScript

### datamodel behind “dynamic zones” (jsonb?)

Very cool!
Every component gets its own table.
Example: Page type "page" with components "foo" and "bar" creates the tables
- pages
- id=1 title=hello world
- page_components
- id=1 page=1 componentType=foo componentId=5 dynamicZoneName=slots
- id=2 page=1 componentType=bar componentId=47 dynamicZoneName=body
- id=3 page=1 componentType=bar componentId=48 dynamicZoneName=sideBar
- component_foo
- id=5 headline=testtest text=testtest
- component_bar
- id=47 title=lol

Gotchas:
- Renaming of "dymanic zone" does not migrate content refs. So formerly-referenced content is in limbo
- Actually, all renamings (even simple fields) result in data loss
- Fields cannot be renamed without completely losing data (columns are set to null)

### Draft system
- Publish and draft state
- you can not write a draft version of an already published post
- edited version becomes "published" automatically
- or you set the post back to draft, but this also unpublishes the old version of that post

### i18n
- Translated pages are seperate rows (with their own id)
- Queries can be sent with a specific locale
- Translations of a page are included in the response (if needed)
- Fill in from other locale feature exists
- Relations are not filled in
- Relation pickers respect the availability within the locale (cant relate from locale "EN" to "DE")
- Synchronizations after translation will always erase the content
- Structure changes are not mirrored to other locales and partial synchronizations are not available

#### Regional content

### Page hierachy
- We have tested `strapi-plugin-navigation`
- we are still unsure if managing custom url structures in strapi is the best way
- or if its better to hardcode everything in nextjs and only use flat collections in strapi

### User interface
- its possible to create custom views based on filters (persisted in the url)
- create a plugin which adds custom navigation items linking to a collection url with applied filters (e.g. link to "marketing pages" based on the `page` collection and `?filter=pagetype:marketing`)

#### Customizations
- Plugin system is pretty strict. You can only customize things based on "injection zones". This should allow us to achieve most things, however we have to follow a set of rules and can not just place buttons in arbitrary positions

### Flexibility of components (change names and types)
- Types can only be changed simply (short text to long text, one image to multiple iamges)

### custom resolver support (top x of coffee in magazin)

### richtext editor
- Use snarkdown (1kb) in frontend
- Replace `h1` in frontend code

### custom collections
- ❌

### relation connector
- ✅

### flexibility of menu
- ✅
- Customizable with `plugins`

### mutations
- ✅

### graphql API
- A lot of redundant `data` and `attributes` nesting
- It's possible to keep all different pages (marketing, magazin, ladingpage, transactional pages) in the same `page` collections. This makes query'ing very easy (single query root, less duplicated fragments)

### content versioning
- ❌
- You will find her in a different castle

### redirect tables
- not included, but we can build that on top of a custom collection

### Migrations
- simple field additions are handled by strapi on boot-up
- everything else is not handled natively and looses data in some cases. E.g. field rename / component relocation
- We will write a cookbook with instructions and helpers for doing more involved tasks
- Also possible to script all those edgecases if needed

### media library
- auto image resize to 4 sizes
- resize algo not the best: produces larger image than source sometimes
- includes a crop feature
- possible s3 integration
- url-based resizing with a simple plugin (we tested that, works out of the box)
- https://market.strapi.io/plugins/strapi-plugin-local-image-sharp
- Webp with quality 90 has great results

### Check if different images can be used for different locales
- This works as the locales are completely seperate data objects

## Cool plugins
- https://market.strapi.io/plugins/strapi-plugin-local-image-sharp
- https://market.strapi.io/plugins/strapi-plugin-placeholder
- https://strapi.io/blog/new-community-plugin-content-versioning