Skip to content

Commit 51f76f7

Browse files
committed
updating
1 parent 625e89f commit 51f76f7

File tree

1 file changed

+11
-16
lines changed

1 file changed

+11
-16
lines changed

website/pages/en/network/developing.mdx

Lines changed: 11 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
title: Developing
33
---
44

5-
Learn developer fundamentals and review the basics of a subgraph’s lifecycle. To start coding right away and build on The Graph, go to [Developer Quick Start](/quick-start/)
5+
Learn developer fundamentals and review the basics of a subgraph’s lifecycle. To start coding right away and build on The Graph, go to [Developer Quick Start](/quick-start/).
66

77
## Overview
88

99
As a developer, you need important data to build and power your dapps. Querying and indexing that blockchain data can be challenging, but The Graph provides a solution to this issue.
1010

1111
On The Graph, you can:
1212

13-
1. Create, deploy and publish subgraphs to The Graph using **Graph CLI** and [Subgraph Studio](https://thegraph.com/studio/).
13+
1. Create, deploy and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
1414
2. Use GraphQL to query live subgraphs and power dapps.
1515

1616
### What is GraphQL?
@@ -31,23 +31,21 @@ A subgraph is a custom API built on blockchain data. It extracts data from a blo
3131

3232
A subgraph primarily consists of the following files:
3333

34-
- `subgraph.yaml`: this YAML file contains the [subgraph manifest](/developing/creating-a-subgraph/#the-subgraph-manifest)
35-
- `subgraph.graphql`: this GraphQL schema defines what data is stored for your subgraph, and how to query it via [GraphQL](/developing/creating-a-subgraph/#the-graphql-schema)
36-
- `AssemblyScript Mappings`: [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) mappings translates data from the event data to the entities defined in your schema
34+
- `subgraph.yaml`: this YAML file contains the [subgraph manifest](/developing/creating-a-subgraph/#the-subgraph-manifest).
35+
- `subgraph.graphql`: this GraphQL schema defines what data is stored for your subgraph, and how to query it via [GraphQL](/developing/creating-a-subgraph/#the-graphql-schema).
36+
- `mappings`: this [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) mappings file translates data from the event data to the entities defined in your schema.
3737

3838
Learn the detailed specifics to [create a subgraph](/developing/creating-a-subgraph/).
3939

4040
### Subgraph Lifecycle
4141

42-
Here is a general view of a subgraph’s cycle:
42+
Here is a general view of a subgraph’s lifecycle:
4343

4444
![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
4545

4646
### Context for Subgraph Development
4747

48-
Great subgraphs start with a local development environment and unit tests. Developers can use `graph-cli,` `graph-ts,` and [Matchstick](/developing/unit-testing-framework/) to build robust subgraphs that deploy to The Graph Network.
49-
50-
> Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command line interface tool for building and deploying subgraphs in The Graph.
48+
Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs in The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs that deploy to The Graph Network.
5149

5250
## Deploy to Subgraph Studio
5351

@@ -58,11 +56,10 @@ Once defined, a subgraph can be deployed to [Subgraph Studio](/deploying/deployi
5856

5957
## Publish to the Network
6058

61-
When you are happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
59+
When you are happy with your subgraph, you can put it into production and [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. This ensures Indexers can index it.
6260

63-
- To put your subgraph into production and ensure indexers can index it, you must publish it to The Graph Network.
64-
- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
65-
- Published subgraphs have a corresponding NFT, which is then easily transferable.
61+
- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
62+
- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-and-deprecate-a-subgraph) by sending the NFT.
6663
- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
6764

6865
## Add Signal for Indexing
@@ -93,9 +90,7 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa
9390

9491
## Deprecating & Transferring Subgraphs
9592

96-
If you no longer need a published subgraph, you can deprecate or transfer a subgraph. Deprecating a subgraph returns any signaled GRT to [Curators](/network/curating/).
97-
98-
- To deprecate or transfer a subgraph, check out [this guide](/managing/transfer-and-deprecate-a-subgraph/#deprecating-a-subgraph).
93+
If you no longer need a published subgraph, you can deprecate or transfer a subgraph. Deprecating a subgraph returns any signaled GRT to [Curators](/network/curating/). To deprecate or transfer a subgraph, check out [this guide](/managing/transfer-and-deprecate-a-subgraph/#deprecating-a-subgraph).
9994

10095
## Network Economics
10196

0 commit comments

Comments
 (0)