Usage: seedcase-flower COMMAND
Flower generates human-readable documentation from Data
Packages.
╭─ Commands ───────────────────────────────────────────────╮
│ <build> Build human-readable documentation │
│ from a datapackage.json file. │
│ <view> Display the contents of a │
│ datapackage.json in a │
│ human-friendly way. │
│ --help Display this message and exit. │
│ --install-completion Install shell completion for this │
│ application. │
│ --version Display application version. │
╰──────────────────────────────────────────────────────────╯
Using the CLI
Flower’s CLI has two commands: view which displays a Data Package’s metadata in the terminal, and build which generates plain text documentation files from it. The general pattern for the CLI is:
Terminal
seedcase-flower COMMAND [ARGS] [OPTIONS]To get an overview of the available commands and flags, run the following command, which is equivalent to using the --help flag:
Terminal
seedcase-flowerViewing Data Package metadata
To view the metadata in an easy-to-read format optimised for the terminal, use the view command:
Terminal
seedcase-flower viewViewing metadata in a custom location
By default, view looks for a datapackage.json file in the current directory, but you can specify a different path if needed:
Terminal
seedcase-flower view another/directory/datapackage.jsonYou can also point Flower to a remote Data Package by providing the full URL to the datapackage.json. For example:
Terminal
seedcase-flower view https://raw.githubusercontent.com/seedcase-project/example-seed-beetle/refs/heads/main/datapackage.jsonFor Data Packages on GitHub, use the gh: prefix as a shortcut instead of the full URL:
Terminal
seedcase-flower view gh:seedcase-project/example-seed-beetleStyling terminal output
Use the --style flag to format the terminal output with any of the built-in view styles. For example:
Terminal
seedcase-flower view --style quarto-one-page gh:seedcase-project/example-seed-beetleThis output will look identical to the output above, since quarto-one-page is the default style for view.
view only works with single-page built-in styles; multi-page styles are not supported.
view is only configurable via command line flags. This means that any options set in Flower’s configuration file are ignored, even those with the same name as the options passed to view.
For more details, see the view reference or run:
Terminal
seedcase-flower view --helpUsage: seedcase-flower view [OPTIONS] [ARGS]
Display the contents of a datapackage.json in a
human-friendly way.
╭─ Arguments ──────────────────────────────────────────────╮
│ <SOURCE> The location of a datapackage.json, defaults │
│ to a file or folder path. Can also be an │
│ https: source to a remote datapackage.json or │
│ a github: / gh: pointing to a repo with a │
│ datapackage.json in the repo root (in the │
│ format gh:org/repo, which can also include │
│ reference to a tag or branch, such as │
│ gh:org/repo@main or gh:org/repo@1.0.1). │
│ [default: datapackage.json] │
╰──────────────────────────────────────────────────────────╯
╭─ Parameters ─────────────────────────────────────────────╮
│ --style The style used to display the output in the │
│ terminal. Must be a single-page style. │
│ [choices: quarto-one-page] │
│ [default: quarto-one-page] │
╰──────────────────────────────────────────────────────────╯
Building documentation from Data Package metadata
To convert Data Package metadata into human-friendly plain text files for building shareable documentation, such as a website or PDF, use the build command:
Terminal
seedcase-flower buildThis command generates one new file, docs/index.qmd, since build by default uses the quarto-one-page style. The qmd extension means that this file is a Quarto-flavored Markdown file. While this is the default format, you can specify your own custom styles as detailed in the custom styles guide.
Changing input and output directory
By default, build will look for a datapackage.json file in the current directory, but you can use a different source location if you want, just like with view:
Terminal
seedcase-flower build another/directory/datapackage.jsonTo generate files in a different location, use the --output-dir flag with a folder name. For example:
Terminal
seedcase-flower build --output-dir my-dirThis will generate my-dir/index.qmd instead of docs/index.qmd.
Styling the output
Like view, build accepts a --style option to control how metadata content and files are organised using one of the built-in styles. For example, to split each resource into its own file, use the quarto-resource-listing style:
Terminal
seedcase-flower build --style quarto-resource-listingLike the default quarto-one-page style, quarto-resource-listing creates a docs/index.qmd. In addition, it creates a separate file for each data resource in the docs/resources/ folder.
You can see examples of the available built-in styles on the Examples page and read more about how to create your own custom style in the custom styles guide.
For more details, see the build reference or run:
Terminal
seedcase-flower build --helpUsage: seedcase-flower build [OPTIONS] [ARGS]
Build human-readable documentation from a datapackage.json
file.
╭─ Arguments ──────────────────────────────────────────────╮
│ <SOURCE> The location of a datapackage.json, defaults │
│ to a file or folder path. Can also be an │
│ https: source to a remote datapackage.json or │
│ a github: / gh: pointing to a repo with a │
│ datapackage.json in the repo root (in the │
│ format gh:org/repo, which can also include │
│ reference to a tag or branch, such as │
│ gh:org/repo@main or gh:org/repo@1.0.1). │
│ [default: datapackage.json] │
╰──────────────────────────────────────────────────────────╯
╭─ Parameters ─────────────────────────────────────────────╮
│ --style The style used to structure the output. If │
│ a style directory is given, this parameter │
│ will be ignored. │
│ [choices: quarto-one-page, │
│ quarto-resource-listing, │
│ quarto-resource-tables] │
│ [default: quarto-one-page] │
│ --style-dir The directory that contains the Jinja │
│ template files and sections.toml. When │
│ set, it will override any built-in style │
│ given by the style parameter. │
│ [default: None] │
│ --output-dir The directory to save the generated files │
│ in. │
│ [default: docs] │
│ --verbose If True, prints additional information to │
│ the console. │
│ [default: False] │
╰──────────────────────────────────────────────────────────╯