How to configure Orchid and scale the configuration as your site growsSee Also: Edit this page
A config file
config.yml in the root of the resources directory serves as the root of all site options. The entire
site can be fully described in this one file, but if you have lots of options and want to make it easier to manage it
all, you may break it out into individual files in the
config/ directory. Orchid merges the options in
config.yml, which are then made available to all parts of the Orchid build. Configuration options are loaded
before every build when running in "serve" mode.
Note: Orchid supports many data languages, including TOML. You may name your config file
config.tml to parse it as
TOML rather than YAML, or
config.json to parse as JSON. The same goes for all files in
different files can use different formats as needed.
Basic Site Config
theme: # (1) menu: - type: 'readme' - type: 'license' wiki: # (2) sections: - 'userManual' - 'developersGuide' services: # (3) generators: disabled: - 'javadoc' - 'posts' allPages: # (4) layout: single
- Theme options come from
themeor from an object at the theme's
key. When using multiple themes, you may want to use individual theme keys to configure each theme independently, but
themeis generally easier to quickly try out different themes.
- Generator options come from an object at that plugin's key
- Services are all scoped under the
servicesobject, and are used to configure the behavior of the Orchid framework.
- In addition to the options defined in a page's FrontMatter, you may have a set of shared options that all pages, or specific sub-sets of pages should have in common. This is an example of archetypes, learn more about them here.
For larger and more complex sites, a single
config.yml file will get messy very quickly. You may break up your
config.yml into as many smaller files as you need, simply by adding a file in the
whose filename corresponds to its options key. This process is recursive, and you can further break up those files by
creating directories within
config/, and so on. You may also specify a filename and and folder, and the two will be
merged into one single options object, where the options in the file take precedence over the folder.
For example, the following YAML configs are equivalent:
Config in one single config.yml
# config.yml theme: siteName: 'My Site' components: - type: pageContent - type: readme - type: license menu: - type: page itemId: 'About' - type: link title: 'Contact' url: '/contact'
Config broken into several files
# config.yml (you could even omit config.yml if desired)
# config/theme.yml siteName: 'My Site'
# config/theme/components.yml - type: pageContent - type: readme - type: license
# config/theme/menu.yml - type: page itemId: 'About' - type: link title: 'Contact' url: '/contact'