Mixed A4T implementations
Open
Adobe Target
Alloy
Konductor
- Dominant language
- JavaScript
- Stars
- 104
- Forks
- 60
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 5
Description
Allow A4T to be used with one product on Web SDK and the other on a legacy implementation.
Contributor guide
Research direction
No files, tests, or entry points are named. Begin by clarifying the A4T compatibility requirements between the Web SDK and legacy implementation, then map the affected integration boundaries; done means one product can use the Web SDK while the other uses the legacy implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100