Skip to content

github(summary): update learn more link#384

Merged
crazy-max merged 1 commit into
docker:mainfrom
crazy-max:summary-learn-more-blogpost
Jun 26, 2024
Merged

github(summary): update learn more link#384
crazy-max merged 1 commit into
docker:mainfrom
crazy-max:summary-learn-more-blogpost

Conversation

@crazy-max
Copy link
Copy Markdown
Member

Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Comment thread src/github.ts
.addBreak()
.addRaw(`Build records include details such as timing, dependencies, results, logs, traces, and other information about a build. `)
.addRaw(addLink('Learn more', 'https://docs.docker.com/go/build-summary/'))
.addRaw(addLink('Learn more', 'https://www.docker.com/blog/new-beta-feature-deep-dive-into-github-actions-docker-builds-with-docker-desktop/?utm_source=github&utm_medium=actions'))
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also sets utm_source and utm_medium

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Go idea to add the UTM components. Do you think we should still use a go path and handle the redirect?
@dvdksn, maybe we should distill this post down into some "Introductory Guide" for users not familiar with Builds View?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm yeah, why not? We could have that intro page in the manual section for builds, and link off to the full description in the Docker Desktop section.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@colinhemmings

Do you think we should still use a go path and handle the redirect?

I don't think /go fits if we are using UTM parameters

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a few go-links with utm params, for example:
https://github.com/docker/docs/blob/main/data/redirects.yml#L694-L700

Copy link
Copy Markdown
Member Author

@crazy-max crazy-max Jun 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a few go-links with utm params, for example: https://github.com/docker/docs/blob/main/data/redirects.yml#L694-L700

How do we make sure the source/medium is right? For example if I open within my browser https://docs.docker.com/go/build-eap/ these are wrong as this does not come from Docker Desktop but directly from my browser. That's my concern.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, there is no guarantee that the link will be accessed only from the correct source, providing the correct utm.

@crazy-max crazy-max merged commit 2e70a0c into docker:main Jun 26, 2024
@crazy-max crazy-max deleted the summary-learn-more-blogpost branch June 26, 2024 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants