Skip to content
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

Created roadmap page for the Overview section #391

Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions components/Sidebar.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -281,6 +281,7 @@ export const DocsNav = () => {
label='What is JSON Schema?'
/>
<DocLink uri='/overview/sponsors' label='Sponsors' />
<DocLink uri='/overview/roadmap' label='Roadmap' />
<DocLink
uri='/overview/similar-technologies'
label='Similar Technologies'
Expand Down
35 changes: 35 additions & 0 deletions pages/overview/roadmap/index.page.tsx
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
import React from 'react'

Check failure on line 1 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`
import { getLayout } from '~/components/Sidebar'

Check failure on line 2 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`
import fs from 'fs'

Check failure on line 3 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`
import Head from 'next/head'

Check failure on line 4 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`
import { Headline1 } from '~/components/Headlines'

Check failure on line 5 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`
import matter from 'gray-matter'

Check failure on line 6 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`
import StyledMarkdown from '~/components/StyledMarkdown'

Check failure on line 7 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`
import { DocsHelp } from '~/components/DocsHelp'

Check failure on line 8 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`
import { SectionContext } from '~/context'

Check failure on line 9 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`

export async function getStaticProps() {
const block1 = fs.readFileSync('pages/overview/roadmap/roadmap.md', 'utf-8')

Check failure on line 12 in pages/overview/roadmap/index.page.tsx

View workflow job for this annotation

GitHub Actions / Linting, Formatting and Type checking

Insert `;`
const { content: block1Content } = matter(block1)
return {
props: {
blocks: [block1Content]
}
}
}

export default function ContentExample ({ blocks }: { blocks: any[] }) {
const newTitle = 'Roadmap'

return (
<SectionContext.Provider value='docs'>
<Head>
<title>{newTitle}</title>
</Head>
<Headline1>{newTitle}</Headline1>
<StyledMarkdown markdown={blocks[0]} />
<DocsHelp />
</SectionContext.Provider>
)
}
ContentExample.getLayout = getLayout
34 changes: 34 additions & 0 deletions pages/overview/roadmap/roadmap.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
---
section: docs
title: Roadmap 2023-24
---
## 2023/2024 Roadmap
Copy link
Collaborator

Choose a reason for hiding this comment

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

Great progress so far @praveen-rikhari !! Great work. I sent you a message in Slack with extended feedback but basically we need to build the board experience into the page accessing to the board items using the GitHub API so instead of a link or a screenshot we provide an amazing board experience with live content rendered.


👋 Dear JSON Schema Community,

We are thrilled to announce the completion of the JSON Schema roadmap for 23-24 🎉 , a result of dedicated efforts and collaboration within our community. We invite each of you to join us on this exciting journey as we strive to address the most significant challenges JSON Schema faces. Together, we can build a better future for JSON Schema!

To ensure transparency and inclusivity, we have documented our roadmap on GitHub. You can find all the details and progress updates by visiting the following link 👉 [JSON Schema Roadmap](https://github.com/orgs/json-schema-org/projects/14/views/13).

The roadmap is a result of the two-day in-person summit, where we identified the biggest problems we should be solving. For those interested in a deeper dive into the summit proceedings, including the agenda, notes, and write-up, we encourage you to explore the summit report [here](https://github.com/orgs/json-schema-org/discussions/391).

## Our key objectives for 23-24 are:

- Refine the Contributor's experience
- Define a strategy to better support implementers
- Identify a list of critical interfaces that implementations should have
- Complete the new version of the Spec
- Publish the new webpage
- Complete the OpenJS onboarding
- Research of existing implementations by language
- Define a sustainability strategy
- Define and roll out the documentation strategy
- Implement and scale the new governance model
- Enhance public communications strategy

We encourage you to review the roadmap in this [board](https://github.com/orgs/json-schema-org/projects/14/views/1). Each objective has its own dedicated GitHub issue. When checking each issue, you will notice that some have been marked as "unspecified," indicating the need for collaborative input from our community to define success criteria, deliverables, and task breakdowns.

### A Call for Collaborators!
The individuals assigned to each issue have taken up the responsibility to define, drive, and work on the respective tasks. However, we are actively looking for contributors! We welcome and encourage everyone to contribute to tasks where they feel they can add value.

Join Us to shape the future of JSON Schema
Loading