Files
directus/docs/guides/interfaces.md
Rijk van Zanten 817ccf3620 Overhaul docs (#3951)
* Add Quickstart Guide

* Update installation

* Remove unused files

* Update support/backing

* Tweaks in concepts

* Setup file structure for API reference 2.0

* Setup page layout for reference

* Add clean-urls plugin

* getting started updates

* Finish authentication rest

* getting started updates

* Render stylus in 2 spaces

* Various

* Various

* Finish activity docs

* Add collections reference

* Add extension reference

* concepts updates

* Fields/tweaks

* Add files doc

* Add revisions

* concepts docs

* More api reference

* Finish rest api reference (finally)

* initial concepts

* More things

* Add assets api ref

* Move sections from file to assets

* Add environment variables

* contributing docs

* Add field transforms page

* Left align table headers

* concept links

* Add API config

* Fix mobile nav

* Add migrating a project

* doc link fixes

Co-authored-by: Ben Haynes <ben@rngr.org>
2021-02-05 18:51:54 -05:00

114 lines
3.2 KiB
Markdown

# Custom Interfaces <small></small>
> Custom Interfaces allow you to create new ways of viewing or interacting with field data on the Item Detail page. [Learn more about Interfaces](/concepts/interfaces/).
## 1. Setup the Boilerplate
Every interface is a standalone "package" that contains at least a metadata file and a Vue component. We recommend using
the following file structure:
```
src/
index.js
interface.vue
```
### src/index.js
```js
import InterfaceComponent from './interface.vue';
export default {
id: 'custom',
name: 'Custom',
description: 'This is my custom interface!',
icon: 'box',
component: InterfaceComponent,
types: ['string'],
};
```
- `id` — The unique key for this interface. It is good practice to scope proprietary interfaces with an author prefix.
- `name` — The human-readable name for this interface.
- `description` — A short description (<80 characters) of this interface shown in the App.
- `icon` — An icon name from the material icon set, or the extended list of Directus custom icons.
- `component` — A reference to your Vue component.
- `types` — A CSV of supported [types](/concepts/types/).
::: tip TypeScript
See
[the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/interfaces/types.ts#L5-L18)
for more info on what can go into this object.
:::
### src/interface.vue
```vue
<template>
<div>My Custom Interface</div>
</template>
<script>
export default {};
</script>
```
#### Available Props
- `value` — The value of the parent field.
- `width` — The layout width of the parent field. Either `half`, `half-left`, `half-right`, `full`, or `fill`.
- `type` — The type of the parent field.
- `collection` — The collection name of the parent field.
- `field` — The key of the parent field.
- `primary-key` — The current item's primary key.
## 2. Install Dependencies and Configure the Buildchain
Set up a package.json file by running:
```bash
npm init -y
```
To be read by the Admin App, your custom interface's Vue component must first be bundled into a single `index.js` file.
We recommend bundling your code using Rollup. To install this and the other development dependencies, run this command:
```bash
npm i -D rollup rollup-plugin-commonjs rollup-plugin-node-resolve rollup-plugin-terser rollup-plugin-vue@5.0.0 @vue/compiler-sfc vue-template-compiler
```
You can then use the following Rollup configuration within `rollup.config.js`:
```js
import { terser } from 'rollup-plugin-terser';
import resolve from 'rollup-plugin-node-resolve';
import commonjs from 'rollup-plugin-commonjs';
import vue from 'rollup-plugin-vue';
export default {
input: 'src/index.js',
output: {
format: 'es',
file: 'dist/index.js',
},
plugins: [terser(), resolve(), commonjs(), vue()],
};
```
## 3. Develop your Custom Interface
The interface itself is simply a Vue component, which provides an blank canvas for creating anything you need.
## 4. Build and Deploy
To build the interface for use within Directus, run:
```bash
npx rollup -c
```
Finally, move the output from your interface's `dist` folder into your project's `/extensions/interfaces` folder. Keep
in mind that the extensions directory is configurable within your env file, and may be located elsewhere.