- associations
- associations/belongs_to.md
- associations/has_and_belongs_to_many.md
- associations/has_many.md
- associations/has_one.md
- associations/common/scopes_common.md
- associations/common/show_hide_buttons_common.md
- recipes
- actions.md
- associations.md
- authentication.md
- authorization.md
- cards.md
- custom-asset-pipeline.md
- custom-fields.md
- custom-tools.md
- customization.md
- dashboards.md
- evaluation-hosts.md
- faq.md
- field-options.md
- [ ] fields.md
- filters.md
- grid-view.md
- [] index.md
- installation.md
- licensing.md
- localization.md
- menu-editor.md
- recipes.md
- records-reordering.md
- resource-tools.md
- resources.md
- search.md
- stimulus-integration.md
- tabs.md
- upgrade.md
- grammarly
- options heading
- each option should have
defualt
andpossible values
- the field should have images from different views
- version and license requirements
We begin the file with the name of the field. Next we write the field declaration and a short description of what the field does. Next we should attach an image or gif with it.
The second section is the Options
section marked by an h2
(##
) paragraph.
We should pass each option following this pattern:
:::option `OPTION_NAME_IN_CODE_BLOCK`
Short description of the feature.
Code samples here.
Images here.
##### Default value
`THE_VALUE_IN_CODE_BLOCKS`
#### Possible values
Some possible values if they are known (`true`, `false`, `" "` `"on"`, `"off"`, etc.) or a text description about them.
:::
After the options, if the field has a lot of options and permutations and you'd like to show more, we can add an ## Examples
block.
Next are all the other things about the field. Maybe it requires some explanation