You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+29-25Lines changed: 29 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,9 @@ All commands are run from the root of the project, from a terminal:
53
53
|`bun run preview`| Preview your build locally, before deploying |
54
54
|`bun run astro ...`| Run CLI commands like `astro add`, `astro check`|
55
55
|`bun run astro -- --help`| Get help using the Astro CLI |
56
+
|`bun run format`| Format all files with Prettier |
57
+
|`bun run format:check`| Check code formatting for all files |
58
+
|`bun run lint`| Run Linting |
56
59
57
60
You can substitute the `bun` commands with whatever package manager of your choice uses.
58
61
@@ -68,22 +71,22 @@ Thank You for Contributing! We appreciate your effort to write a blog post and s
68
71
69
72
**Typical Target Audience:**
70
73
71
-
* Technically-inclined users interested in Interledger development.
72
-
* Technically-inclined users interested in financial services technologies, innovations, or developments.
73
-
* Users keen on topics like APIs, data analytics, metrics, analysis, and quantitative assessment for digital networks.
74
-
* Users interested in privacy and related technologies.
74
+
- Technically-inclined users interested in Interledger development.
75
+
- Technically-inclined users interested in financial services technologies, innovations, or developments.
76
+
- Users keen on topics like APIs, data analytics, metrics, analysis, and quantitative assessment for digital networks.
77
+
- Users interested in privacy and related technologies.
75
78
76
79
**Possible Content Framework:**
77
80
78
81
If you're unsure how to structure your writing, you can use this as a guide.
79
82
80
-
* Introduction / main point
81
-
* Context - Interledger’s perspective / stance / commitment on the topic being written [broader categories like privacy, metrics for growth, Digital Financial Inclusion etc.]
82
-
* The Challenge (or) The Problem
83
-
* The Solution
84
-
* The How / implementation
85
-
* Roadmap - short-term / long-term
86
-
* Note: A call to action (CTA) will be included automatically at the bottom of every post.
83
+
- Introduction / main point
84
+
- Context - Interledger’s perspective / stance / commitment on the topic being written [broader categories like privacy, metrics for growth, Digital Financial Inclusion etc.]
85
+
- The Challenge (or) The Problem
86
+
- The Solution
87
+
- The How / implementation
88
+
- Roadmap - short-term / long-term
89
+
- Note: A call to action (CTA) will be included automatically at the bottom of every post.
87
90
88
91
Ideal Word Count: Between 1,000 and 2,500 words, with links to relevant documents/pages for a deeper understanding.
89
92
@@ -93,28 +96,29 @@ Discuss Ideas: Before starting, share your blog post ideas with the tech team to
93
96
94
97
Copy the Template: Begin your draft using [this Google Doc template](https://docs.google.com/document/d/1L7vzsYORg9xmf72ljTdmyekpq2vJ7eQZ9atM2uAXgUM/edit?usp=sharing) to maintain a consistent format.
95
98
96
-
Review Process##
99
+
Review Process##
97
100
98
101
Initial Reviews:
99
102
100
-
* Once your draft is ready, request specific reviewers or ask for feedback on the #tech-team Slack channel.
101
-
* Incorporate feedback and refine the blog post.
103
+
- Once your draft is ready, request specific reviewers or ask for feedback on the #tech-team Slack channel.
104
+
- Incorporate feedback and refine the blog post.
102
105
103
106
Finalizing:
104
107
105
-
* When the draft is stable, create a pull request in the [interledger.org-developers](https://github.com/interledger/interledger.org-developers) GitHub repo.
106
-
* Please add links where appropriate so people can easily click to learn more about the concepts you reference.
107
-
* Include all images used in the post in the PR.
108
-
* No-one is expected to know the ins and outs of Astro (the framework that powers our site), so please tag Sarah as a reviewer to ensure everything Astro-related is in order.
108
+
- When the draft is stable, create a pull request in the [interledger.org-developers](https://github.com/interledger/interledger.org-developers) GitHub repo.
109
+
- Please add links where appropriate so people can easily click to learn more about the concepts you reference.
110
+
- Include all images used in the post in the PR.
111
+
- No-one is expected to know the ins and outs of Astro (the framework that powers our site), so please tag Sarah as a reviewer to ensure everything Astro-related is in order.
109
112
110
-
### Working with Visuals
113
+
### Working with Visuals
111
114
112
-
* If you need an illustration, submit a design request in advance to Madalina via the #design Slack channel using the design request form.
113
-
* Before uploading images to GitHub, run them through an image optimizer such as [TinyPNG](https://tinypng.com/).
114
-
* Ensure images are appropriately sized; feel free to ask Madalina or Sarah for assistance.
115
+
- If you need an illustration, submit a design request in advance to Madalina via the #design Slack channel using the design request form.
116
+
- Before uploading images to GitHub, run them through an image optimizer such as [TinyPNG](https://tinypng.com/).
117
+
- Ensure images are appropriately sized; feel free to ask Madalina or Sarah for assistance.
115
118
116
119
### Publishing Your Blog Post
117
120
118
-
* Remember: merging the pull request will publish the blog post immediately.
119
-
* Ensure the publishing date in the blog post metadata matches the intended release date.
120
-
* Check with Ioana to confirm the publishing date and keep a consistent posting schedule. Ioana will also handle social media promotion.
121
+
- Remember: merging the pull request will publish the blog post immediately.
122
+
- Ensure the publishing date in the blog post metadata matches the intended release date.
123
+
- Check with Ioana to confirm the publishing date and keep a consistent posting schedule. Ioana will also handle social media promotion.
124
+
- Run `bun run format` and `bun run lint` to format your code and check for issues before creating a pull request.
0 commit comments