Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcommon.ftd
More file actions
Latest commit
30 lines (20 loc) · 1.05 KB
/
Copy pathcommon.ftd
File metadata and controls
30 lines (20 loc) · 1.05 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
-- ftd.column render-definition:
width: fill
--- ft.h1: `id`
This accepts the "id" of the document to be built. The ID
corresponds to the relative path of the URL after the base_url has been removed.
Eg if the current fpm package's name is `amitu.com/foo/` and the specific
document we are looking for is `amitu.com/foo/bar/`, the `id` would be `/bar/`.
--- ft.h1: `root`
This accepts the "root" of the fpm package. It specifies the location where
the fpm package exists. This is an optional field. In case if value is not provided,
it will take the current directory as the root for fpm package.
--- ft.h1: `base_url`
A fpm package has a base name. Say there is a file `foo.ftd` in your fpm package,
it's full URL would be `<fpm-package-name>/foo/`. `<fpm-package-name>` could
be something like `a.com/b/`. The `base` in this case would be `/b/`. But when
running locally, the base could be `/`.
--- ft.h1: `data`
The document being rendered may use [`get-data`
processor](https://fpm.dev/processors/get-data/). To pass `data` is used to pass
data to `get-data`.