mautic / mautic/developer-documentation-new
[DOCS]: Add "Dynamic Content" page to branch 7.1
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 19
- Forks
- 48
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 25
Description
Description
Whenever parent issue (#427) has completed, cherry-pick the PR commits (excluding merge base branch commits) to 7.1.
Refer to the Git cherry-pick section of the Community Handbook for detailed instructions.
[!IMPORTANT]
Before the PR for the parent issue is merged, the status of this issue is blocked.
Relevant Documentation URL
https://devdocs.mautic.org/en/7.1/rest_api/dynamic_content.html
Are you willing to help us fix this by making a pull request?
No
Suggestions (Optional)
How to update the page
-
Find the file that needs to be updated in the
docs/directory. The dev docs URL format is as such:https://devdocs.mautic.org/en/x.x/FOLDER_NAME/FILE_NAME.htmlFor example, if the relevant URL is
https://devdocs.mautic.org/en/7.0/plugin_extensions/manipulating_contacts.html, then findmanipulating_contacts.rstfile inside theplugin_extensionsfolder. -
Transfer the content under the note admonition. Look at other pages on how to structure the content.
-
Review and update the content when you see fit.
-
Follow the contributing guidelines that are listed in the "Resources" section above.
Screenshots or Screen Recordings (Optional)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Wait for parent issue #427 to complete, then inspect the 7.1 docs path for rest_api/dynamic_content.rst and compare it with the referenced Dynamic Content page. Cherry-pick the relevant parent PR commits without merge-base commits, transfer the content under the note admonition, and verify the 7.1 documentation page builds correctly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 40/100