-
-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New spec page structure #819
New spec page structure #819
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see my comment in the associated issue. I don't feel we should be reformatting these documents.
Blocking until that is resolved.
Let's discuss this Greg. I asked the docs team to do this. I have strong arguments for this change. |
I agree it needs to be discussed. It never was. We should use the issue. |
This is part of the Google Season of Docs projects and the issue has been there for months. My feeling is you think we are republishing, and we are just reorganizing and elevating our docs. If you think we shouldn't add the draft publication details like authors in this page that is fine. We can change that and other things as per the community feedback. We are going to reestructure the website docs....that is what the Docs strategy issue is about and why we applied to GSoD. |
It appears I misunderstood the purpose of this issue. The specification documents themselves are not changing, only the specifications page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Blessing. Great work wit this first PR.
I left some comments. Migration, JSON Hyper Schema and release notes need still a lot of work.
components/DocTable.tsx
Outdated
</Link> | ||
</td> | ||
</tr> | ||
<tr className='dark:hover:bg-slate-950 hover:bg-slate-300 '> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove this implementations section for now. When it is ready, we can add a link to the new tooling page.
pages/draft/2020-12/index.md
Outdated
type: docs | ||
authors: ['Austin Wright', 'Henry Andrews', 'Ben Hutton', 'Greg Dennis'] | ||
Metaschema: 'https://json-schema.org/draft/2020-12/schema' | ||
Implementations: 'https://bowtie.report/#/dialects/draft2020-12' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets remove the implementations metadata from here.
pages/draft/2020-12/index.md
Outdated
Metaschema: 'https://json-schema.org/draft/2020-12/schema' | ||
Implementations: 'https://bowtie.report/#/dialects/draft2020-12' | ||
Specification: 'https://json-schema.org/draft/2020-12/json-schema-core.html' | ||
Status: 'Stable' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove the status field as well.
pages/draft-06/index.md
Outdated
authors: ['Austin Wright', 'Henry Andrews', 'Ben Hutton', 'Greg Dennis'] | ||
Metaschema: 'https://json-schema.org/draft/2020-12/schema' | ||
Specification: 'https://json-schema.org/draft/2020-12/json-schema-core.html' | ||
Implementations: 'https://bowtie.report/#/dialects/draft2020-12' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove implementations and status details from all the drafts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noted.
pages/draft/2020-12/index.md
Outdated
- **Embedded Schemas and Bundling**: Provides guidance on bundling schemas into a Compound Schema Document. | ||
- **Vocabulary Changes**: Separates the `format` vocabulary into `format-annotation` and `format-assertion`. | ||
|
||
### Access all data connected to Draft 2020-12 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest calling this section just "Draft 2020-12 Documents"
pages/migration/index.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This page needs more work. We should call out here Alterschema https://github.com/sourcemeta/alterschema as the tool to help with the migration to newer schemas. Please speak with @jviotti (TSC member). He is probably the best person the speak with to create here a new great page.
Check examples in other languages like: https://www.asyncapi.com/docs/migration/migrating-to-v3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This page requires work as well. I think it requires an introduction, all the links and finally the release notes.
We should update the sidebar to add all the child pages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The JSON-hyper-schema page cannot carry all the release notes. What would be the usefulness of the release notes page?
I agree with having an introduction and updating the sidebar to carry all child pages. When you say 'all the links' - all the hyper-schema links, yes?
pages/release-note/index.page.tsx
Outdated
@@ -0,0 +1,46 @@ | |||
import React from 'react'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Folder name should be release-notes
pages/release-note/index.page.tsx
Outdated
import StyledMarkdown from '~/components/StyledMarkdown'; | ||
import { SectionContext } from '~/context'; | ||
|
||
export async function getStaticProps() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pages needs a lot of work. I'll try to push some code later today.
components/DocTable.tsx
Outdated
@@ -0,0 +1,78 @@ | |||
import React from 'react'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we refine the style of the table to be similar to this one (@DhairyaMajmudar )
https://developer.android.com/about/versions/15/release-notes?hl=es-419
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looking forward for the change : )
What kind of change does this PR introduce?
Documentation Enhancement

Issue Number:
Screenshots/videos:
Added
Summary
The Specification section of the docs is fixed to adapt to the proposed change in alignment with Diataxsis and issue #791
Does this PR introduce a breaking change?
No