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

New information architecture #1194

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

valeriahhdez
Copy link
Contributor

@valeriahhdez valeriahhdez commented Dec 21, 2024

What kind of change does this PR introduce?
This PR changes the information architecture of the documentation with the following changes:

  • Aligns content buckets to the diataxis framework to documentation.
  • Creates a new content bucket for Guides (to be populated)
  • Restructures the navigation of the Reference content bucket by eliminating deep nesting.
  • Edits titles for consistency and clarity.
  • Reallocates documents to create a coherent organization.
  • Adds an Overview page providing context and expectations for each content bucket and the Reference sections that contain nested documents.

**Issue Number:

Screenshots/videos:

If relevant, did you update the documentation?
Yes, I made changes to several documents within the reference content bucket.

Summary

This PR addresses the needs of the GSoD project, more specifically, milestone 5 of the documentation strategy.

The problem: we need to reorganize the information in a coherent way to onboard people new to JSON Schema and make it easier for readers to find what they’re looking for.

The goals:

  • To streamline developer workflows by revamping our documentation architecture with the diataxis approach.

  • To conduct a style overhaul for a more intuitive and cohesive developer experience.

You can see a slide deck summarizing this work here.

Does this PR introduce a breaking change? No

@valeriahhdez valeriahhdez self-assigned this Dec 21, 2024
@valeriahhdez valeriahhdez requested a review from a team as a code owner December 21, 2024 15:41
@valeriahhdez valeriahhdez added this to the Docs Release 5 milestone Dec 22, 2024
Copy link
Member

@DhairyaMajmudar DhairyaMajmudar left a comment

Choose a reason for hiding this comment

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

@valeriahhdez pls. resolve the failing lint workflow. For doing so you've to run the command yarn run lint:fix

import Head from 'next/head';
import { Headline1 } from '~/components/Headlines';
import { SectionContext } from '~/context';
import Card from '~/components/Card';
Copy link
Member

Choose a reason for hiding this comment

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

Pls. remove this unused import

Copy link

github-actions bot commented Jan 6, 2025

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
website ✅ Ready (View Log) Visit Preview a01a0bc

Copy link

codecov bot commented Jan 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (27398a9) to head (a01a0bc).
Report is 35 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1194   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          373       373           
  Branches        94        94           
=========================================
  Hits           373       373           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@valeriahhdez valeriahhdez added Status: In Progress This issue is being worked on, and has someone assigned. 📝 Documentation Indicates improvements or additions to documentation. ✨ Enhancement Indicates that the issue suggests an improvement or new feature. Status: Review Needed The issue has a PR attached to it which needs to be reviewed. and removed Status: In Progress This issue is being worked on, and has someone assigned. labels Jan 11, 2025
@valeriahhdez
Copy link
Contributor Author

Hi @benjagm,

Can you please review this PR?

@valeriahhdez valeriahhdez requested a review from benjagm January 12, 2025 12:33
@DhairyaMajmudar DhairyaMajmudar self-requested a review January 14, 2025 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📝 Documentation Indicates improvements or additions to documentation. ✨ Enhancement Indicates that the issue suggests an improvement or new feature. Status: Review Needed The issue has a PR attached to it which needs to be reviewed.
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

[📝 Docs]: Improve documentation's information architecture
2 participants