AdobeDocs / AdobeDocs/experience-platform.en
Acxiom AEP Connector content updates
- Dominant language
- No language data
- Stars
- 11
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
Issue in .https://github.com/AdobeDocs/experience-platform.en/help/destinations/catalog/data-partner/acxiom-data-enhancement.md
I am the Solution Architect for Acxiom responsible for several of our Source and Destination connectors. We are undergoing a rebrand of them and I have content updates across 2 sources and 2 destinations. These updates include changes to file names, image assets, copy, and links dirstributed throughout our content.
Would you consider allowing us to push a branch with the comprehensive changes for a PR-merge? Or is the preferred method for a comprehensive update like this still through UI forks? Please advise!
Thanks,
Brett Campbell
Acxiom Solution Architect
Contributor guide
Research direction
Start by reviewing help/destinations/catalog/data-partner/acxiom-data-enhancement.md and identify the related Acxiom source and destination pages referenced by the requested rebrand. Confirm the repository's preferred contribution workflow before editing. Done means the affected file names, image assets, copy, and links are consistently updated across all four connectors.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100