If a user has a zone already on Cloudflare, it is easy for us to allow them to set up a custom hostname.
It will take some work for us to actually allow people to CNAME to their zoneless Workers, but in the meantime, developers can still deploy to their own custom sites.

To support this without requiring too much user involvement, we would need to:

• Create a dummy DNS record (if one doesn't already exist for the hostname), i.e. to 1.2.3.4 (to allow external DNS to resolve)
• Create a wildcard route for the hostname (somewhat related: cloudflare/wrangler-legacy#76 ).

We should document this as the recommended path for custom hostnames (will create separate issue in docs).

I'm trying to add a link to the REST API in the navbar. With the current design, it'd go in the hamburger - three dot menu as shown in the screenshot below

I'm worried these links might be too hidden away for people to see. Could we have these external links in the navbar with some kind of divider to make the distinction? (Could probably include a small h3/4 title too if needed)

We should add https://developers.cloudflare.com/workers/about/tips/signing-requests/ as Examples or a Tutorial.

The Algolia results currently are coming from the old (current) site:

We’ll need to either create a new Algolia account or have it re-crawl once we launch. The crawl probably takes some time / has a delay, so we need to be thoughtful about the coordination of this.

Similar to #72, there are some links to https://developers.cloudflare.com/workers/tooling/wrangler/secrets/ that are currently broken.

Now that we merged the v0 branch (#62), we need to do a bunch of post-merge cleanup. One such step is fixing all of the broken links (e.g. some links to /about/... need to be changed to /learning/...).

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/learning/playground.md

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/learning/debugging-workers.md

There are a number of links to https://developers.cloudflare.com/workers/reference/storage , which doesn't exist here. We should figure out what needs to be migrated and migrate it.

https://github.com/apollographql/gatsby-theme-apollo/blob/master/packages/gatsby-theme-apollo-docs/src/components/social-card.js

e.g. there could be a Cloudflare Docs engine template, for which then the product (e.g. Workers) adds its product logo, and perhaps even the title of the docs page is added as well, etc.

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/runtime-apis/fetch.md

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/learning/how-workers-works.md

(Not to be confused with #95, which is related but a separate issue.)

e.g. https://workers.cloudflaredocs.workers.dev/learning/how-workers-works

We should get an updated list of data center latitudes and longitudes for:

https://github.com/cloudflare/workers-docs-engine/blob/3d6cb82ec906d063e147497b8b3720923793cd7b/src/components/network-map.js#L6

Currently used on https://workers.cloudflaredocs.workers.dev/learning/how-workers-works

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/learning/fetch-event-lifecycle.md

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/runtime-apis/response.md

Migrate https://developers.cloudflare.com/workers/reference/apis/addEventListener/ here.

Prism supports it, so I believe we just need to augment prism-react-renderer with this.

https://github.com/PrismJS/prism/blob/master/components/prism-toml.js

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/runtime-apis/request.md

most if not all of the tutorials are getting new names/URLs during the redesign, we need to handle redirecting from the old URLs here: https://github.com/cloudflare/workers-docs/blob/master/workers-docs/workers-site/redirects/newDocs.js

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/learning/workers-metrics.md

After merging the v0 branch, which added a few dozen pages, the build is now breaking due to the app.js build exceeding KV’s limit:

@ispivey @rita3ko what should we do?

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/learning/security-model/index.md

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/learning/using-streams.md

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/runtime-apis/add-event-listener.md

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/runtime-apis/web-standards.md

In the old docs, /sites and /tooling/wrangler/sites/ contain info about Workers Sites. We need to migrate that here.

The old docs say:

Cloudflare Workers uses the V8 JavaScript engine from Google Chrome. The Workers runtime is updated at least once a week, to at least the version that is currently used by Chrome's stable release. This means you can safely use latest JavaScript features, with no need for "transpilers".

If this is still true, then it should get added to the new docs.

The placeholder image Gatsby displays is showing through underneath images that have already loaded (if they have transparency in them):

https://workers.cloudflaredocs.workers.dev/tutorials/deploy-a-react-app-with-create-react-app

This can’t only be a problem we’ve come across. A little Googling and I found this:

gatsbyjs/gatsby#16516

I may be misunderstanding the issue, but it’s unclear to me why the <span class="gatsby-resp-image-background-image"/> can’t just fade out (read: opacity: 0) after the main image loads.

An alternative/addition to footnotes worth considering:

Every tutorial will essentially need the same boilerplate about how to set up a Cloudflare Workers account, and then install & configure Wrangler.

Let’s see if we can make either one more reusable MDX components which tutorials can import, which would put that setup (or compose portions of it) inside the tutorial, possibly inside an expanding details/summary setup.

Something similar to the “Web”, “iOS”, ..., tabs here:

https://stripe.com/docs/payments/accept-a-payment

We’ve decided to separate what were previously called “Templates” and “Snippets” (in the current Template Gallery ¹) into two separate places, “Templates” and “Examples”. The design for the Examples section is now done #3. So what’s left is the new Templates section.

1.

There are lots of links to /quickstart , which doesn't exist here. We should migrate this content.

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/learning/how-the-cache-works.md

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/runtime-apis/request.md

https://github.com/cloudflare/workers-docs-engine/blob/master/src/content/runtime-apis/fetch-event.md

Before:

After:

Some of the snippets are pretty clear/readable, e.g.:

https://developers.cloudflare.com/workers/templates/pages/rewrite_links_html/

But others confusingly written, poorly formatted, etc., e.g.:

https://developers.cloudflare.com/workers/templates/pages/private_data_loss/

Let’s clean up the worst of these as we’re migrating content from what was once the “Template Gallery”

Use the gatsby-remark-copy-linked-files plugin (see #22 for an example).

the gatsby-remark-copy-linked-files plugin that was going to be added in @davidtsong's PR #22 seems to fix GIFs working on pages, but appears¹ to introduce a new issue, where any directory with an _index.md file begins building the URLs as $PATH/_index:

this was discovered during #21, but i don't want to scope creep out of the tutorials in that PR so opening this issue for us to continue tracking this.

1: this happened for me locally, and i would love to have someone else test and confirm that this happens for them too!

New location: https://github.com/cloudflare/cloudflare-docs (inside products/workers folder).

• Move docs-config.js
• Move src/content to products/workers/src/content
• Transfer over Github issues on this repo with label: content