Design how to represent entire sites using a description

Open
#96 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
graphql, typescript
Domain
api, web-dev

Research direction

The issue names no file, test, or entry point; start by reviewing the API structure and clarifying how routes, layouts, related components, and GraphQL data context should be represented. Done would be an agreed JSON description that captures those site elements and their relationships.

Written by the indexing model from the issue text.

Description

enhancement

A JSON should be able to capture routes, layouts, related components, data context for GraphQL queries.

Dominant language
TypeScript
Stars
56
Forks
77
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ReactFinland/graphql-api

All issues in ReactFinland/graphql-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.