Start Here: Documentation Templates: Old - FlipsideCrypto/fsc-evm GitHub Wiki
For new pages, please follow the naming conventions outlined in Updating and Maintaining the Wiki section.
The following macros are intended to be used to create and maintain various models. These macros can be accessed via version >=`vx.y.z` of the `fsc-evm` package. Macro variables are set and managed in the respective repo's `dbt_project.yml` file. Please see the `fsc-evm` installation instructions in the [README](https://github.com/FlipsideCrypto/fsc-evm/blob/main/README.md) for more details on how to access and utilize this macro effectively.
<(optional) general description of the following macros or category>
---
# `<MACRO_NAME>`
## Usage
<Add any notes about where and how this macro is used here.>
[fsc_evm.<MACRO_NAME>](<link_to_macro__file>) Note: The link must point to the `permalink`, which is the line in the code where the macro begins.
## Parameters
_Note: Parameters with `default` values must be ordered after non-default parameters._
| Parameter | Type | Default | Description | Variable |
|--------------------------|---------|---------|----------------------------------|------------------------|
| `<PARAMETER_1>` | <TYPE> | <VALUE> | [DESCRIPTION_OF_PARAMETER_1] | `<PROJECT_VARIABLE_1>` |
| `<PARAMETER_2>` | <TYPE> | <VALUE> | [DESCRIPTION_OF_PARAMETER_2] | `<PROJECT_VARIABLE_2>` |
| `<PARAMETER_3>` | <TYPE> | <VALUE> | [DESCRIPTION_OF_PARAMETER_3] | `<PROJECT_VARIABLE_3>` |
| `<PARAMETER_4>` | <TYPE> | <VALUE> | [DESCRIPTION_OF_PARAMETER_4] | `<PROJECT_VARIABLE_4>` |
## Example
```sql
# Example 1
{{ fsc_evm.<MACRO_NAME>(
<PARAMETER_1>,
<PARAMETER_2>,
<PARAMETER_3>.
<PARAMETER_4>
) }}
# Example 2
{{ fsc_evm.<MACRO_NAME>(
var('<PROJECT_VARIABLE_1>'),
var('<PROJECT_VARIABLE_2>'),
var('<PROJECT_VARIABLE_3>'),
var('<PROJECT_VARIABLE_4>')
) }}
# Example 3
{{ fsc_evm.<MACRO_NAME>() }}
...
...
## `General Guides` Template
1. Provide a high level summary or explanation on the topic.
2. Detail the implementation by walking through required steps, variables or applicable notes. Please proofread and provide as much detail as possible. Any developer should be able to follow and understand these steps with limited prior context.
3. Share best practices, tips or tricks on the topic.
4. Provide detailed examples, reference links to models, sources etc. on how to implement. Feel free to provide screenshots!
```md
# <TITLE>
### Summary:
### Best Practices, Tips & Tricks:
### Implementation Steps, Variables & Notes:
### Examples, References & Sources:
---
# <TITLE>
...