Skip to content

v15 docs audit - #240

Merged
vdikransamarjian merged 1 commit into
mainfrom
dikran/v15-updates
Oct 20, 2026
Merged

vdikransamarjian merged 1 commit into
mainfrom
dikran/v15-updates

Conversation

@vdikransamarjian

Copy link
Copy Markdown
Contributor

💸 TL;DR

This update aligns Next and 0.15 documentation with the release:

  • Makes migration from devvit.yaml to devvit.json an explicit requirement before upgrading.
  • Documents removal of the wiki revision-ID string overload and shows the supported options-object call.
  • Clarifies that blocks and @devvit/public-api remain supported but deprecated, with legacy and Devvit Web examples kept separate.
  • Adds examples for custom expanded-mode titles and navigation between entries while already expanded.

The wiki guide is available in both versions, and examples follow the existing docs’ tone.

Why the large diff? We regenerated the stale development reference from released @devvit/reddit@0.15.0, touching 378 generated files. 318 only update the version label from 0.15.0-dev to 0.15.0.

The corpus now includes the changelog and updated guidance. It was flagged to me that corpus was out of date.

@@ -1,4 +1,4 @@
[**@devvit/reddit v0.15.0-dev**](../../README.md)
[**@devvit/reddit v0.15.0**](../../README.md)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🔕 I think this will immediately be overwritten the next time there's a release. There's no harm in doing this, and I hope I'm wrong, but just calling it out in case this happens again in a week.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

:( @ben-harris-5 can we not let it get overwritten?

@vdikransamarjian
vdikransamarjian merged commit f9475d9 into main Oct 20, 2026
2 checks passed
@vdikransamarjian
vdikransamarjian deleted the dikran/v15-updates branch October 20, 2026 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants