Offer guidance as to what to do after creating a new GTM container
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 383
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 80
Description
## Feature Description
Currently when a new GTM container is created via Site Kit it won't be very useful. In fact it will actually raise a 404 on the homepage because the new container won't have any published version associated with it.
After a new container is created, we should offer some next steps for the user to take or learn about to use their new container.
---------------
_Do not alter or remove anything below. The following sections will be managed by moderators only._
## Acceptance criteria
*
## Implementation Brief
*
### Test Coverage
*
### Visual Regression Changes
*
## QA Brief
*
## Changelog entry
*
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the Site Kit flow that creates a new GTM container and determine where post-creation guidance is rendered. Done means users receive clear next steps after creating a container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- analytics, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100