docs(feat): prepare documentation for docs merge into developer portal #1606
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🚀 Deployed on https://pr-1606--dhis2-ui.netlify.app |
cjmamo
approved these changes
Oct 30, 2024
|
@Topener can you convert this into a draft if it's not ready yet for review? |
|
Once this PR is merged, do NOT delete the branch until a followup PR for the developer portal has been merged |
Topener
changed the title
Topener
force-pushed
the
devrel-18-prepare
branch
from
5e7a93b to
18ca35a
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements DEVREL-18
This is a PR to prepare the UI library documentation for the Developer Portal. Several Docusaurus breaking changes are covered here as well, as are a suite of other small changes.
Merging this will break links in current UI docs, so maybe developer portal should go live before this PR is merged, using this branch as the staging, and then after go-live a redirect should be included in this PR