Document for creating custom segment parameter

[dtng95]

📋 Description

• Adding new document about creating new custom segment for Engage V16

📎 Related Issues (if applicable)

✅ Contributor Checklist

I've followed the Umbraco Documentation Style Guide and can confirm that:

• Code blocks are correctly formatted.
• Sentences are short and clear (preferably under 25 words).
• Passive voice and first-person language (“we”, “I”) are avoided.
• Relevant pages are linked.
• All links work and point to the correct resources.
• Screenshots or diagrams are included if useful.
• Any code examples or instructions have been tested.
• Typos, broken links, and broken images are fixed.

Product & Version (if relevant)

Engage V16

Deadline (if relevant)

📚 Helpful Resources

• 🧾 Umbraco Contribution Guidelines
• ✍️ Umbraco Documentation Style Guide

[nathanwoulfe]

Hey @dtng95 I've left some comments/suggestions below - mainly to keep the linter happy, but also updated the manifest example.

It's probably worth adding a note too that this example depends on the Engage Backoffice NPM package, which hasn't been released yet.

[eshanrnh]

Thanks for the PR, @dtng95. We will review it asap.

[eshanrnh]

Hey @dtng95 👋,

Could you add the new article to the SUMMARY.md file so it appears in the navigation for review?

[eshanrnh]

Thanks for the PR, @dtng95 🙌 The PR looks great 💪

I have added several suggestions to remove “we,” fix vale errors and warnings, format technical terms, and align with the style guide. Let me know if anything is unclear.

Also, as mentioned above, kindly add an entry for the implement-custom-segment-parameters.md article in the SUMMARY.md file

[dtng95]

Hi @eshanrnh ,
I've updated the PR, including my changes based on your comments, and move the current changes to an existing document, which already has an article in SUMMARY.md file

[eshanrnh]

Thanks for incorporating the suggestions, @dtng95 🙌

The images are not showing in the Preview. Can you double-check the image paths since the article has been changed?

[eshanrnh]

Attempt to fix images :)

[dtng95]

Thanks @eshanrnh for the update. Was about to push another update to fix the image, but you've already updated it. It looks good!