BD-3318-5 Apply Diataxis standards to Liquid documentation

[rachel-feinberg]

Why are you making this change? (required)

Apply Diataxis standards and brand voice to three Liquid articles/pages.

Related PRs, issues, or features (optional)

• N/A

Feature release date (optional)

BD-3318

Contributor checklist

• I confirm that my PR meets the following:
  • I signed the Contribution License Agreement (CLA).
  • My style and voice follows the Braze Style Guide.
  • My content contains correct spelling and grammar.
  • All links are working correctly.
  • If I renamed or moved a file or directory, I set up URL redirects for each file.
  • If I updated or replaced an image, I did not remove the original image file from the repository. (For more information, see Updating an image).
  • If my PR is related to a paid SKU, third party, SMS, AI, or privacy, I have received written approval from Braze Legal.

Submitting for review

If your PR meets the above requirements, select Ready for review, then add a reviewer:

• Non-Braze contributors: Add braze-inc/docs-team as the reviewer.
• Braze employees: Have any relevant subject matter experts (like engineers or product managers) review your work first, then add the tech writer assigned to your specific vertical. If you're not sure which tech writer to add, you can add braze-inc/docs-team instead.

Thanks for contributing! We look forward to reading your work.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
braze-docs-ko	⬜️ Ignored (Inspect)	Visit Preview		Oct 15, 2024 4:49pm

[josh-mccrowell-braze]

Do we have any standards around naming "Use case" headers so we don't have the same header multiple times on the page? It might help with SEO.

[rachel-feinberg]

I'll update the templates, but I've been using "Use Case" for one-off use cases that are nested under specific headers, as it's implied that the use case is for that header (in this case, variable tags). For multiple use cases that are nested under the same header, I've been using "Use Case: So-and-So". I think "Use Case #" has been used in the past.

[josh-mccrowell-braze]

Left some comments! These are good improvements, though. Approving so I'm not a blocker.