Clarify UI location for "Save" button in Versions and Deployments documentation

Open Beginner friendly
#28,812 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
76/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
markdown
Domain
documentation

Research direction

Open the Versions and Deployments documentation URL and review the section “Upload a new version to be gradually deployed or deployed at a later time.” Update the Save-button instructions to identify the Online Editor and the Edit Code step, then verify the rendered wording and dashboard navigation are clear.

Written by the indexing model from the issue text.

Description

content:edit documentation product:workers quick-fix stale
Existing documentation URL(s)

https://developers.cloudflare.com/workers/configuration/versions-and-deployments/

What changes are you suggesting?

Under the section Upload a new version to be gradually deployed or deployed at a later time the instructions for using the "Save" button are unclear.

The documentation states:
"... or create a new version via the Cloudflare dashboard using the Save button. You can find the Save option under the down arrow beside the "Deploy" button."

Issue: This button is only visible within the Online Editor (Edit Code) interface. A user navigating the main Worker dashboard or the Deployments tab will not find this button. The documentation should be updated to specify that these steps must be performed within the Online Editor.

Image
Additional information

Suggested Fix: Change the text to: "...or create a new version via the Online Editor in the Cloudflare dashboard by clicking Edit Code, then selecting the Save option under the down arrow beside the 'Deploy' button."

Dominant language
MDX
Stars
5.2k
Forks
16.8k
Avg merge
2d 13h
Merged PRs (30d)
344

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudflare/cloudflare-docs

All issues in cloudflare/cloudflare-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.