API pages #257
Merged
API pages #257
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
|
I put an old API URL to the menu to merge it before releasing PostCSS 8 |
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.
New API will be in our alchemy design and on
postcss.org/api!I already moved API docs from JSDoc to TypeDoc as a part of better TypeScript support in PostCSS 8.0.
Now I wrote a custom TypeDoc→HTML generator to fit our design and PostCSS API specifics.
Thanks to @okonet for a very flexible design.
We will merge the PR during the PostCSS 8.0 release, so I am marking it as a draft just to collect the feedback.