Skip to content

docs: create new guide for rdme@10#1284

Merged
emilyskuo merged 26 commits intonextfrom
emily/rm-13209-fork-main-rdme-docs-page-and-create-a-copy-for-v10
Jul 8, 2025
Merged

docs: create new guide for rdme@10#1284
emilyskuo merged 26 commits intonextfrom
emily/rm-13209-fork-main-rdme-docs-page-and-create-a-copy-for-v10

Conversation

@emilyskuo
Copy link
Copy Markdown
Contributor

@emilyskuo emilyskuo commented Jul 2, 2025

🚥 Resolves RM-13209, RM-11989

🧰 Changes

Updates to our rdme docs to be synced to the ReadMe Docs. As part of this

  • forks all pages we sync and updates everything to reflect new frontmatter format, general guidance, etc.
  • marked existing pages and legacy and reflected copy to reflect this
  • updates links throughout
  • updates CI workflow so we're doing rdme docs upload --dry-run runs on every push
  • gets alex running against MDX files again

🧬 QA & Testing

do the docs look good?

kanadgupta and others added 3 commits July 3, 2025 13:56
## 🧰 Changes

minor rearranging of the docs as part of
#1284. all of the docs that we're
syncing now live in a `synced/` directory, and the legacy pages live in
a subdirectory of that.
@kanadgupta kanadgupta added the documentation Improvements or additions to documentation label Jul 7, 2025
emilyskuo and others added 9 commits July 7, 2025 10:43
## 🧰 Changes

- [x] rewrites `rdme.mdx` for a post-refactored world
- [x] cleans up frontmatter (this is since we probably want to
hide/shuffle things around in readme itself and this allows us to do it
there!)
- [x] add callout for category URI normalization
- [x] add the category URI back to the main page once we determine where
the page will be living
Copy link
Copy Markdown
Contributor

@kanadgupta kanadgupta left a comment

Choose a reason for hiding this comment

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

just pushed up a few finishing touches and revived a few CI things — i'm happy with this if you are @emilyskuo!

- uses: readmeio/github-readme-sync@v2
with:
readme-oas-key: <<user>>:API_DEFINITION_ID
readme-oas-key: API_KEY:API_DEFINITION_ID
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

i brought back alex checks for MDX files and it was getting tripped up by these <<whatever>> statements so i just ripped 'em out


To see an example where multiple OpenAPI/Swagger files are synced in the same repository, check out [jesseyowell/oas-test-files](https://github.com/jesseyowell/oas-test-files).

</details>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

similar thing down here — alex was expecting this

@@ -1,7 +1,6 @@
---
title: 'GitHub Actions Example: Syncing Markdown'
category:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

per what we discussed offline, i added the category to the main page (e.g., documentation/synced/rdme.mdx) but omitted it from everywhere else so as to keep the source of truth for that attribute in our bidirectionally-synced repo.

@@ -1,10 +1,16 @@
name: Sync `documentation` directory to ReadMe
name: Sync docs to ReadMe
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

all the changes in this file are so we can get rdme docs upload dry runs working again 🥳

@kanadgupta kanadgupta marked this pull request as ready for review July 7, 2025 22:52
@emilyskuo emilyskuo merged commit 319674f into next Jul 8, 2025
9 checks passed
@emilyskuo emilyskuo deleted the emily/rm-13209-fork-main-rdme-docs-page-and-create-a-copy-for-v10 branch July 8, 2025 00:34
kanadgupta added a commit that referenced this pull request Jul 8, 2025
| 🚥 Resolves RM-13246 |
| :------------------- |

## 🧰 Changes

updates the formatting for our `this.warn()` statements so they're
surfaced properly in github actions annotations.

- [x] make sure everything else is merged in and refresh this branch
afterwards
- [x] do a dry run with the CI changes in
#1284 to ensure that warnings are
surfaced properly

## 🧬 QA & Testing

i confirmed that these are showing up properly:
https://github.com/readmeio/rdme/actions/runs/16131074838/job/45518517159
@kanadgupta
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 10.4.0-next.8 🎉

The release is available on:

Your semantic-release bot 📦🚀

kanadgupta added a commit that referenced this pull request Jul 8, 2025
)

| 🚥 Resolves RM-13226, RM-13227 |
| :------------------- |

## 🧰 Changes

- [x] marks all page upload commands as stable
- [x] updates migration guide to reflect command availability
- [x] updates command descriptions to reflect new frontmatter format
(will require links to the docs in
#1284)

## 🧬 QA & Testing

confirmed that all of the help screens and warnings are updated
accordingly!
@kanadgupta
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 10.4.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation released on @next released

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants