[DOCS]: Add "Implementing variant - A/B test - support to entities" page to branch 7.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation
Research direction
Read the contributing guidelines and compare the legacy content in source/includes/_plugin_misc_variant_entities.md with the target page at docs/plugin_miscellaneous/variant_entities.rst. Transfer the content into RST, review and update it using nearby documentation pages and the style guide, then verify the resulting page at the 7.0 documentation URL.
Written by the indexing model from the issue text.
Description
Description
We need to move the content from legacy repo and convert it to RST, as well as update the content.
[!IMPORTANT]
Please read the below resources before contributing to help you with this task:
- Contributing guidelines
- Contributing to Mautic’s documentation
- Mautic technical writing style guide
- The "Suggestions (Optional)" section below for guides on how to update the page
Relevant Documentation URL
https://devdocs.mautic.org/en/7.0/plugin_miscellaneous/variant_entities.html
Link to the content at legacy docs
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
- Dominant language
- Shell
- Stars
- 19
- Forks
- 48
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 25
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.
More from mautic/developer-documentation-new
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 76/100
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 76/100
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
All issues in mautic/developer-documentation-new
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·