github/directus
1
1
Fork 0
mirror of https://github.com/directus/directus.git synced 2026-04-25 03:00:53 -04:00
Code Issues Packages Projects Releases Wiki Activity

Docs updates

Browse Source
This commit is contained in:
Ben Haynes
2020-10-01 16:26:11 -04:00
parent d38d5e266f
commit 297336adb3
2 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/concepts/files-and-thumbnails.md
View File

@@ -12,15 +12,20 @@ Storage adapters allow project files to be stored in different locations or serv
## Files
Directus allows you to manage all your files in one place, including documents, images, videos, and even third-party embedded resources (eg: YouTube). Files can be uploaded to the [File Library](#) in general, or directly to an item via a [Single File](#) or [Multiple Files](#) field.
Directus allows you to manage all your files in one place, including documents, images, videos, and more. Files can be uploaded to the [File Library](#) in general, or directly to an item via a [Single File](#) or [Multiple Files](#) field.
@TODO private files
### Relevant Guides
* [Uploading a File](#)
* [Requesting an Original File](#)
* [Requesting a Private File](#)
## Embedded Assets
Directus also supports ingesting third-party embedded assets, such as YouTube or Vimeo videos. These are managed the same as normal files, however the resource itself is stored on the external service, and referenced via its proprietary UID.
## Crop & Transform Images
Our file middleware also allows for cropping and transforming image assets on the fly. This means you can simply request an image, include any desired transformation parameters, and you'll be served the new asset as a response. This is very useful for automatically generating many different thumbnails/versions of an original file.

4
docs/concepts/relationships.md
View File

@@ -6,7 +6,7 @@
While it may seem complex at first, relational data is actually quite straightforward once you understand what's happeneing behind the confusing terminology. Before diving into the details of each type, let's first cover a few basics that will help you better visualize each in your mind's eye.
### PKs and FKs
### PKs vs FKs
Every [item](#) in a relational database has a unique "key" that identifies it within its [collection](#). Because it's required, the key is the first [field](#) created within a collection, typically storing an "auto-increment" number, an automatically generated unique hash, or a manually entered value. They are often abbreviated to "PK" (Primary Key), "ID" (Identifier), "UID" (Unique Identifier), or "UUID" (Universally Unique Identifier), depending on the type of value they store. After it's created, the value of an item's PK should _never_ change.
@@ -18,7 +18,7 @@ We've ignored compound keys in this explanation to help keep things as simple as
### Perspective Matters
Relationships and keys are relative to their "parent" collection. Looking at the same relationship/key from the perspective of a different collection may change or reverse its type.
Just like primary and foreign keys are directional, relationships are always relative to their "parent" collection. Looking at the same relationship/key from the perspective of a different collection may change or reverse its type.
## Many-to-One (M2O)