You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Depending on the template this might be best resolved with a "fence" style markdown extension.
Here's an example of the current syntax:
{% capture table %}
| Parameter | Description | Example || ------------------------------------- | ------------------- | -------------------------- || <em>utm_source</em> | The name of the product, domain of the website that drives traffic to the link. | <em>utm_source=email</em> || <em>utm_medium</em> | The channel you are using to share your link. | <em>utm_medium=social</em> || <em>utm_content</em> | The specific item that a person clicks on to access the link (such as an A/B test, a website banner, or a specific ad). | <em>utm_content=get-the-addon-button</em> || <em>utm_campaign</em> | The specific product promotion or strategic campaign. | <em>utm_campaign=launch-announcement</em> |
{% endcapture %}
{% include modules/table.liquid
content: table
%}
Depending on the template this might be best resolved with a "fence" style markdown extension.
Here's an example of the current syntax:
All the template is doing is this:
If at all possible it would be nice to not need to do anything other than the markdown for a table.
The text was updated successfully, but these errors were encountered: