When going into the API reference pages, the API playground omits the lexicon name. To be more specific, instead of seeing (for example) https://bsky.social/xrpc/app.bsky.feed.getPostThread, you instead see https://bsky.social/xrpc.

Below is a video showcasing this issue:

Because of this, attempting to test any APIs would lead to 404 errors.

(My apologies for the weird lines in the video: I'm not too sure why it's doing that.)

The "MDX" files frequently fail to build due to syntax errors. Would be good to have a basic CI which would try to build the existing files, if not additionally do other API auto-docs compilation.

Since there is no type definition for record in the API reference, important usage of the API is unclear.
In particular, there is a concern that developers who do not use the official SDK will not be able to find a way to follow or like.

Explain how to generate a bearer token here: https://www.docs.bsky.app/docs/api/at-protocol-xrpc-api or update endpoints to publicly accessible ones that don't require bearer tokens

Documentation describes the function of endpoint "app.bsky.actor.getProfile" as "Get detailed profile view of an actor. Does not require auth, but contains relevant metadata with auth", however requests not containing a Bearer return 401.

We need to:

• Make it clear how obtain a bearer token (the docs are currently vague about this)
• Split APIs into read-only and requiring auth. Make that distinction clear. Possibly even with icons in the sidebar
• Integrate this information into the runnable HTTP widget. Make it easy to get bearer token right there for any API call or, for publicly available APIs, not require it at all
• Make sure the instructions and code snippets for any public API don't force you to enter the token. Just like our PWI is able to access those endpoints without logging in

The fetch api is now included in the LTS version of NodeJS by default:

https://nodejs.org/dist/latest-v21.x/docs/api/globals.html#fetch

JS examples for using the atproto api should probably include fetch examples, and optionally make these examples the default visible example when clicking on NodeJS.

New docs site is missing the cryptography page from the old site:

• https://atproto.com/specs/cryptography

Old site search results for secp256k1

New site search results for secp256k1

When I went to the showcase page and clicked the "Submit your project here" there were no instructions or best practices to follow. I went through previous PRs that added items to the showcase and figured it so I just submitted my first showcase project #121!

I'm not saying it needs a detailed walk through, but any mention of submissions in the Readme would be nice if that's where the submission link directs to.
Questions that would be helpful to know

• Where are the submissions located? (src/data/users.tsx)
• Where should I put my submission? Is there any order, or just at the end? (I just assumed the end)
• Where should I put the image?
• What are the image requirements/limitations?
• What are the qualifiers for each of the tags?
• What needs to be included in the submission object?
• What should the PR look like?

This added documentation could be as simple as

Submitting to the Community Showcase

1. Fork the bsky-docs repo
2. In src/data/users.tsx, add your submission with {include required info}
3. (Optional) Add photo to src/data/showcase/ {include image requirements/limitations}
4. Commit changes to a branch in your fork
5. Make a PR to merge your branch into the main bsky-docs {include what's needed in the PR}
6. Done! (?)

I'm also more than happy to make a PR to add this, but I don't have the answers to all of the questions right now.

The curl, python, etc code examples on the right are somehow not updated with the actual endpoint being viewed. The URL is always just a base URL (doesn't include the path), the requests are always GET (even for POST endpoints), and no body or query params are included.

I spent an hour or two poking around and can't figure out why this isn't happening. There are just a ton of layers of abstractions/plugins/packages and i'm not familiar with MDX/React to debug this myself.

severity is introduced as being one of "alert, inform, or none" but in the "Custom label values" table and examples I see "warning, alert, inform, or none"

Just curious if "alert" was formerly called "warning" and the docs need to be updated or if I'm misunderstanding something on how labels work.

I propose a little rework on the https://www.docs.bsky.app/docs/get-started page:

• Let's show a read-only example first. E.g. showing a list of someone's posts. This is to demonstrate how easy it is to get started, and that you don't need a "developer account" or an "API key" or all the stuff that's usually necessary to hit an API.
• Let's make this example runnable directly on the page. E.g. via StackBlitz. I'm obviously biased but I think a React example like https://www.docs.bsky.app/docs/starter-templates/clients would be nice (except runnable and showing a list of posts rather than a list of feeds).
• Then let's move the part that requires authentication (posting) down the page a bit. So that it comes after the read-only example. Could be an extension to the first example. (E.g. the example switches to showing own posts -> and then shows how you can add a new one.)

So by the end of the page you kind of see a minimal workable client.

The current daily automation seems to re-generate examples using the current day as the datetime/timestamp, resulting in a lot of git history churn.

I had 4 tabs open with the same link to: https://www.docs.bsky.app/docs/api/com-atproto-server-create-account

One of the tabs showed the following error:

Hi

(For starter user ) I detect the following issue

the sample provided here is really confusing
https://github.com/bluesky-social/bsky-docs/blob/main/docs/tutorials/viewing-feeds.mdx?plain=1#L39

is

const { data } = await agent.getTimeline({
  cursor: "...",
  limit: 30,
});

If I keep the example provided, it generates 500 error (expect 4xx)
⚠️ there is most definitely a bug to create for the backend side, if anyone can create it, or tell me where to create it. This contributes to the resolution of this ticket (having a linked issue created)

and according to the doc, cursor default is empty.
So if I replace "..." by "" ; then I got no issue.

Regards