From 5e9b13fa57f48bbbe08a166a6585e5bb2f34cdda Mon Sep 17 00:00:00 2001 From: waymobetta Date: Fri, 6 Oct 2023 09:57:16 -0700 Subject: [PATCH 01/16] remove test blog post --- Test Blog Post | 1 - 1 file changed, 1 deletion(-) delete mode 100644 Test Blog Post diff --git a/Test Blog Post b/Test Blog Post deleted file mode 100644 index 76f67758..00000000 --- a/Test Blog Post +++ /dev/null @@ -1 +0,0 @@ -This is a test blog post From e79f3fb0ce0a02878fff4588fb7ecfaab89e40e4 Mon Sep 17 00:00:00 2001 From: waymobetta Date: Fri, 6 Oct 2023 10:00:00 -0700 Subject: [PATCH 02/16] fix bold syntax --- posts/2023-09-29_gnomobile/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2023-09-29_gnomobile/README.md b/posts/2023-09-29_gnomobile/README.md index b6aa4f62..605a9811 100644 --- a/posts/2023-09-29_gnomobile/README.md +++ b/posts/2023-09-29_gnomobile/README.md @@ -70,7 +70,7 @@ If you want to add a new message to a blockchain, you need to actually interact Gno nodes run on GnoVMs (gnovm), and for the moment, these are only available on desktops. We believe it is possible to make them available on mobile as well, but we need to find clever ways to overcome the constraints of mobile devices (like putting the apps in the background (iOS), addressing network bandwidth limitations, and so on). 1. Developing a **decentralized push notification service** for *both* mobile and desktop apps. Getting notifications is now a standard (and very important) functionality of centralized apps. Technically, this happens via a central server. Naturally, having a centralized server is not possible for a p2p app, but there are other ways to implement notifications, and we are considering including them in the GnoMobile framework. -2. Making it possible for decentralized apps to **interact with the blockchain even if the network connection is poor or virtually unavailable**. Through the **[Wesh Network** protocol](https://wesh.network/), we are opening up the possibility of using alternative transport mediums to exchange messages between peers in an asynchronous but reliable manner in off-grid environments. Enabling reliable, secure, and censorship-resistant communication is our main cause at Berty Technologies. We want to open the door for p2p users to send messages and interact even in extreme situations or adverse scenarios, and Wesh Network is built specifically for this purpose. It is only natural to make it easier for developers to use it through the GnoMobile framework. +2. Making it possible for decentralized apps to **interact with the blockchain even if the network connection is poor or virtually unavailable**. Through the **[Wesh Network](https://wesh.network/)** protocol, we are opening up the possibility of using alternative transport mediums to exchange messages between peers in an asynchronous but reliable manner in off-grid environments. Enabling reliable, secure, and censorship-resistant communication is our main cause at Berty Technologies. We want to open the door for p2p users to send messages and interact even in extreme situations or adverse scenarios, and Wesh Network is built specifically for this purpose. It is only natural to make it easier for developers to use it through the GnoMobile framework. 3. Advancing **edge networking for enhanced blockchain resilience**. Edge networking refers to bringing functionality like computing power or storage closer to the user so that they don't need to travel through the whole Internet to interact with a server. The same edge concept can be applied to bring the necessary services to interact with the blockchain closer to each p2p user. For example, hosting a copy of the blockchain so a user can sync it or even execute smart contracts. Having these fundamental services closer to the p2p users is especially important in the case of mobile apps. We want to offer developers the possibility of taking advantage of the edge networking benefits by allowing them to use, for instance, network address redirections or special HTTP headers in the configuration of their applications. In all honesty, it’s hard not to get excited about all the different possibilities that lie ahead for GnoMobile, but we’re keeping our focus on shipping V1 for now and collecting feedback from the community. After that, well, we hope you’ll stick around to see what happens next! From 655cb918e29a425384e82f9b4d557c4a523f5b6f Mon Sep 17 00:00:00 2001 From: waymobetta Date: Fri, 6 Oct 2023 10:21:03 -0700 Subject: [PATCH 03/16] fix spacing --- posts/2023-09-29_gnomobile/README.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/posts/2023-09-29_gnomobile/README.md b/posts/2023-09-29_gnomobile/README.md index 605a9811..c0a46128 100644 --- a/posts/2023-09-29_gnomobile/README.md +++ b/posts/2023-09-29_gnomobile/README.md @@ -21,9 +21,21 @@ Simply put, GnoMobile is a framework for developing Gno mobile applications. Thi For communication between the mobile app and the Gno code, GnoMobile uses [gRPC](https://grpc.io/), a well-supported framework that sends and receives Google Protobuf messages. Even though the core Gno code is written in Go, the app code can use React Native, Java, Swift, etc. The following system diagram shows how gRPC is used.
- +
-. +
+
+
+
+
+
+
+
+
+
+
+
+  Moving from the bottom to the top, this is how the flow looks: From 8837c015863cf3125af7f86f8355510af9d95317 Mon Sep 17 00:00:00 2001 From: jon roethke Date: Sat, 7 Oct 2023 14:48:39 -0700 Subject: [PATCH 04/16] Update posts/2023-09-29_gnomobile/README.md Co-authored-by: Manfred Touron <94029+moul@users.noreply.github.com> --- posts/2023-09-29_gnomobile/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2023-09-29_gnomobile/README.md b/posts/2023-09-29_gnomobile/README.md index c0a46128..21bed002 100644 --- a/posts/2023-09-29_gnomobile/README.md +++ b/posts/2023-09-29_gnomobile/README.md @@ -21,7 +21,7 @@ Simply put, GnoMobile is a framework for developing Gno mobile applications. Thi For communication between the mobile app and the Gno code, GnoMobile uses [gRPC](https://grpc.io/), a well-supported framework that sends and receives Google Protobuf messages. Even though the core Gno code is written in Go, the app code can use React Native, Java, Swift, etc. The following system diagram shows how gRPC is used.
- + ![](https://github-production-user-asset-6210df.s3.amazonaws.com/109347079/267934754-e4da6fec-a586-4ebe-97cc-3b3ad7f79370.jpg)


From dc9ef94d0df9db6a37c357b73fbc10cb58bb931b Mon Sep 17 00:00:00 2001 From: jon roethke Date: Tue, 10 Oct 2023 08:20:22 -0700 Subject: [PATCH 05/16] Update posts/2023-09-29_gnomobile/README.md Co-authored-by: Manfred Touron <94029+moul@users.noreply.github.com> --- posts/2023-09-29_gnomobile/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2023-09-29_gnomobile/README.md b/posts/2023-09-29_gnomobile/README.md index 21bed002..36c0c14e 100644 --- a/posts/2023-09-29_gnomobile/README.md +++ b/posts/2023-09-29_gnomobile/README.md @@ -82,7 +82,7 @@ If you want to add a new message to a blockchain, you need to actually interact Gno nodes run on GnoVMs (gnovm), and for the moment, these are only available on desktops. We believe it is possible to make them available on mobile as well, but we need to find clever ways to overcome the constraints of mobile devices (like putting the apps in the background (iOS), addressing network bandwidth limitations, and so on). 1. Developing a **decentralized push notification service** for *both* mobile and desktop apps. Getting notifications is now a standard (and very important) functionality of centralized apps. Technically, this happens via a central server. Naturally, having a centralized server is not possible for a p2p app, but there are other ways to implement notifications, and we are considering including them in the GnoMobile framework. -2. Making it possible for decentralized apps to **interact with the blockchain even if the network connection is poor or virtually unavailable**. Through the **[Wesh Network](https://wesh.network/)** protocol, we are opening up the possibility of using alternative transport mediums to exchange messages between peers in an asynchronous but reliable manner in off-grid environments. Enabling reliable, secure, and censorship-resistant communication is our main cause at Berty Technologies. We want to open the door for p2p users to send messages and interact even in extreme situations or adverse scenarios, and Wesh Network is built specifically for this purpose. It is only natural to make it easier for developers to use it through the GnoMobile framework. +2. Making it possible for decentralized apps to **interact with the blockchain even if the network connection is poor or virtually unavailable**. Through the [**Wesh Network** protocol](https://wesh.network/), we are opening up the possibility of using alternative transport mediums to exchange messages between peers in an asynchronous but reliable manner in off-grid environments. Enabling reliable, secure, and censorship-resistant communication is our main cause at Berty Technologies. We want to open the door for p2p users to send messages and interact even in extreme situations or adverse scenarios, and Wesh Network is built specifically for this purpose. It is only natural to make it easier for developers to use it through the GnoMobile framework. 3. Advancing **edge networking for enhanced blockchain resilience**. Edge networking refers to bringing functionality like computing power or storage closer to the user so that they don't need to travel through the whole Internet to interact with a server. The same edge concept can be applied to bring the necessary services to interact with the blockchain closer to each p2p user. For example, hosting a copy of the blockchain so a user can sync it or even execute smart contracts. Having these fundamental services closer to the p2p users is especially important in the case of mobile apps. We want to offer developers the possibility of taking advantage of the edge networking benefits by allowing them to use, for instance, network address redirections or special HTTP headers in the configuration of their applications. In all honesty, it’s hard not to get excited about all the different possibilities that lie ahead for GnoMobile, but we’re keeping our focus on shipping V1 for now and collecting feedback from the community. After that, well, we hope you’ll stick around to see what happens next! From 2652e9376dcd04c61c390748a142b0f74c32133d Mon Sep 17 00:00:00 2001 From: jon roethke Date: Tue, 10 Oct 2023 11:33:45 -0700 Subject: [PATCH 06/16] Update posts/2023-09-29_gnomobile/README.md Co-authored-by: Manfred Touron <94029+moul@users.noreply.github.com> --- posts/2023-09-29_gnomobile/README.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/posts/2023-09-29_gnomobile/README.md b/posts/2023-09-29_gnomobile/README.md index 36c0c14e..a34b60ed 100644 --- a/posts/2023-09-29_gnomobile/README.md +++ b/posts/2023-09-29_gnomobile/README.md @@ -23,19 +23,6 @@ For communication between the mobile app and the Gno code, GnoMobile uses [gRPC]
![](https://github-production-user-asset-6210df.s3.amazonaws.com/109347079/267934754-e4da6fec-a586-4ebe-97cc-3b3ad7f79370.jpg)
-
-
-
-
-
-
-
-
-
-
-
-
-  Moving from the bottom to the top, this is how the flow looks: From b6f3edcd9e465dbbf04f06e671b2a6eabf330ca7 Mon Sep 17 00:00:00 2001 From: waymobetta Date: Tue, 10 Oct 2023 09:34:17 -0700 Subject: [PATCH 07/16] update deprecated package --- gnoblog-cli/client.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnoblog-cli/client.go b/gnoblog-cli/client.go index c3740df9..c1d01b85 100644 --- a/gnoblog-cli/client.go +++ b/gnoblog-cli/client.go @@ -6,7 +6,7 @@ import ( "context" "flag" "fmt" - "io/ioutil" + "io" "log" "os" "strings" @@ -96,7 +96,7 @@ func run(args []string) error { } if !opts.Debug { - log.SetOutput(ioutil.Discard) + log.SetOutput(io.Discard) } if err := root.Run(context.Background()); err != nil { From 650ea53330219293e16e2191ecbe4ab9633b4a4d Mon Sep 17 00:00:00 2001 From: waymobetta Date: Tue, 10 Oct 2023 12:19:16 -0700 Subject: [PATCH 08/16] fix: add proper tag formatting --- gnoblog-cli/post.go | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/gnoblog-cli/post.go b/gnoblog-cli/post.go index 721954b5..4b0dda3e 100644 --- a/gnoblog-cli/post.go +++ b/gnoblog-cli/post.go @@ -3,6 +3,7 @@ package main import ( "fmt" "io" + "strings" "time" "github.com/adrg/frontmatter" @@ -24,6 +25,18 @@ func parsePost(reader io.Reader) (*post, error) { return nil, fmt.Errorf("invalid post: %w", err) } p.Body = string(rest) + p.Tags = removeWhitespace(p.Tags) return &p, nil } + +// removeWhitespace loops over a slice of tags (strings) and truncates each tag +// by removing whitespace +// ie, []string{"example spaced tag"} -> []string{"examplespacedtag"} +func removeWhitespace(tags []string) []string { + for index, tag := range tags { + tags[index] = strings.Replace(tag, " ", "", -1) + } + + return tags +} From 6fae19f0ed25dcb0997e3399604c1d4c12c93d7c Mon Sep 17 00:00:00 2001 From: leohhhn Date: Fri, 13 Oct 2023 16:32:02 +0200 Subject: [PATCH 09/16] WIP add contributions.md & style guide --- .gitignore | 3 +++ contributing/contributions.md | 22 ++++++++++++++++++++++ contributing/style-guide.md | 20 ++++++++++++++++++++ 3 files changed, 45 insertions(+) create mode 100644 contributing/contributions.md create mode 100644 contributing/style-guide.md diff --git a/.gitignore b/.gitignore index 3fd1dd20..2b3f5a6d 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1,5 @@ reporting/reporting reporting/output +.idea +posts/.DS_Store +.DS_Store \ No newline at end of file diff --git a/contributing/contributions.md b/contributing/contributions.md new file mode 100644 index 00000000..a2bf8421 --- /dev/null +++ b/contributing/contributions.md @@ -0,0 +1,22 @@ +# Contributing to the Gno Blog + +Thank you for considering a contribution to the Gno Blog. We appreciate all and every open-source contribution to the Gno.land project, as everything we do revolves around open-source. +Below, you will find guidelines on how to submit a blog post to the Gno Blog. + +### What we are looking for + +- sadad +- asdadasd +- asdadad +- ad + +### Contribution process + +If you've considered the previous section and would like to contribute to the Gno Blog, here are the steps to follow: +- Write a blog post you'd like to see included to the Gno Blog, while strictly following the [Style Guide](./style-guide.md) +- Submit a PR using [this template](templatePR) to this repo, and ping @waymobetta or @leohhhn for a review + +After your blog post passes the review process, it will be merged into `main` and shortly after deployed on-chain. + + + diff --git a/contributing/style-guide.md b/contributing/style-guide.md new file mode 100644 index 00000000..1785e9e6 --- /dev/null +++ b/contributing/style-guide.md @@ -0,0 +1,20 @@ +# Gno Blog Style Guide + +This style guide offers rules and preferences for contributing to the Gno Blog. +Below are some rules to follow when writing a blog post. + +1. All Gno Blog posts are written in standard Markdown. Follow the formatting for headers, links, bold, italic, strikethrough, etc. as you usually would. +2. Check your content for spelling and grammatical mistakes before submitting. +3. Use the Oxford comma. +4. Make sure the target reader is addressed consistently. +5. Make sure the product, company, tech, and other names are accurate. +6. Fact-check your content. +7. If your post contains images, please add a `src` folder to contain them, and link to them in Markdown. +8. Include front-matter in your blog post, detailing the following: + 1. title, + 2. publication_date, + 3. slug, + 4. tags, + 5. authors. + +If you're unsure of how to style or format something, take a look at previous blog posts, or ping @waymobetta or @leohhhn for help. \ No newline at end of file From 7c574fa3464574ff21ee658c90b27aa18e0abce7 Mon Sep 17 00:00:00 2001 From: leohhhn Date: Mon, 16 Oct 2023 10:05:04 +0200 Subject: [PATCH 10/16] updated structure & contributing.md --- CONTRIBUTING.md | 52 +++++++++++++++++++++++++++++++++++ contributing/contributions.md | 22 --------------- contributing/style-guide.md | 20 -------------- 3 files changed, 52 insertions(+), 42 deletions(-) create mode 100644 CONTRIBUTING.md delete mode 100644 contributing/contributions.md delete mode 100644 contributing/style-guide.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 00000000..8e5af435 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,52 @@ +# Contributing to the Gno Blog + +Thank you for considering a contribution to the Gno Blog. We appreciate all and every open-source contribution to the Gno.land project, as everything we do revolves around open-source. +Below, you will find guidelines on how to submit a blog post to the Gno Blog. + +If you are unsure about something, please don’t hesitate to reach out for help by opening an issue here, on Discord, or directly to the Gno.land DevRel team. +Likewise, if you have an idea on how to improve this guide, go for it as well. + +### What we are looking for +We’re seeking contributions that will bring value to our growing community of gnomes. If you can bring technical expertise or a different perspective to the table, we want to hear from you. Please ensure your article is written in high-quality text and formatted according to the specifications below. We don’t tolerate plagiarism, excessive self-promotion, link spamming, SEO stuffing, or hate speech. + +Below are topics of particular interest to us, but we’re open to all suggestions, so if you have an idea that’s not on the list, but you believe will make great reading, feel free to submit your story. + +- Web3 news and developments and how they impact our community (e.g. legislation, industry trends, technical advances) +- Gno ecosystem news (e.g. interesting new realms/apps, newly-added core functionality, etc.) +- Technical deep dives (e.g. language comparisons, pros and cons, examining the core stack) +- Tutorials and how-to guides +- Useful intros about basic concepts in Gno.land (e.g. package/realm distinction) +- General content that helps explain reasoning or thought processes (e.g. writing the entire stack in Go vs implementing components in Rust) +- Op-ed pieces and alternative views (e.g. building effective governance, decentralizing social media, the importance of censorship-resistant tools) + +### Contribution process + +If you've considered the previous section and would like to contribute to the Gno Blog, here are the steps to follow: +- Write a blog post you'd like to see included to the Gno Blog, while strictly following the [Style Guide](#gno-blog-style-guide). +- Submit a PR using [this template](templatePR), while following the structure of the folders & naming, as shown in the example blog post. +- Ping the Gno.land DevRel team, @waymobetta & @leohhhn for a review. + +After your blog post passes the review process, it will be merged into the `main` branch and shortly after deployed on-chain. + +## Gno Blog Style Guide + +This style guide offers rules and preferences for contributing to the Gno Blog. +Below are some rules to follow when writing a blog post. + +1. All Gno Blog posts are written in standard Markdown. Follow the formatting for headers, links, bold, italic, strikethrough, etc. as you usually would. +2. Check your content for spelling and grammatical mistakes before submitting. +3. Use the Oxford comma. +4. Make sure the target reader is addressed consistently. +5. Make sure the product, company, tech, and other names are accurate. +6. Fact-check your content. +7. If your post contains images, please add a `src` folder to contain them, and link to them in Markdown. +8. Include front-matter in your blog post, detailing the following: + 1. title, + 2. publication_date, + 3. slug, + 4. tags, + 5. authors. + +If you're unsure of how to style or format something, take a look at previous blog posts in this repo, or ping @waymobetta or @leohhhn for help. + + diff --git a/contributing/contributions.md b/contributing/contributions.md deleted file mode 100644 index a2bf8421..00000000 --- a/contributing/contributions.md +++ /dev/null @@ -1,22 +0,0 @@ -# Contributing to the Gno Blog - -Thank you for considering a contribution to the Gno Blog. We appreciate all and every open-source contribution to the Gno.land project, as everything we do revolves around open-source. -Below, you will find guidelines on how to submit a blog post to the Gno Blog. - -### What we are looking for - -- sadad -- asdadasd -- asdadad -- ad - -### Contribution process - -If you've considered the previous section and would like to contribute to the Gno Blog, here are the steps to follow: -- Write a blog post you'd like to see included to the Gno Blog, while strictly following the [Style Guide](./style-guide.md) -- Submit a PR using [this template](templatePR) to this repo, and ping @waymobetta or @leohhhn for a review - -After your blog post passes the review process, it will be merged into `main` and shortly after deployed on-chain. - - - diff --git a/contributing/style-guide.md b/contributing/style-guide.md deleted file mode 100644 index 1785e9e6..00000000 --- a/contributing/style-guide.md +++ /dev/null @@ -1,20 +0,0 @@ -# Gno Blog Style Guide - -This style guide offers rules and preferences for contributing to the Gno Blog. -Below are some rules to follow when writing a blog post. - -1. All Gno Blog posts are written in standard Markdown. Follow the formatting for headers, links, bold, italic, strikethrough, etc. as you usually would. -2. Check your content for spelling and grammatical mistakes before submitting. -3. Use the Oxford comma. -4. Make sure the target reader is addressed consistently. -5. Make sure the product, company, tech, and other names are accurate. -6. Fact-check your content. -7. If your post contains images, please add a `src` folder to contain them, and link to them in Markdown. -8. Include front-matter in your blog post, detailing the following: - 1. title, - 2. publication_date, - 3. slug, - 4. tags, - 5. authors. - -If you're unsure of how to style or format something, take a look at previous blog posts, or ping @waymobetta or @leohhhn for help. \ No newline at end of file From a1aeb82d9a08133177f207362f16ca653dd6b483 Mon Sep 17 00:00:00 2001 From: leohhhn Date: Mon, 16 Oct 2023 10:07:44 +0200 Subject: [PATCH 11/16] add details --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8e5af435..b5032893 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -23,7 +23,7 @@ Below are topics of particular interest to us, but we’re open to all suggestio If you've considered the previous section and would like to contribute to the Gno Blog, here are the steps to follow: - Write a blog post you'd like to see included to the Gno Blog, while strictly following the [Style Guide](#gno-blog-style-guide). -- Submit a PR using [this template](templatePR), while following the structure of the folders & naming, as shown in the example blog post. +- Submit a PR using [this template](templatePR), while following the structure of the folders & naming, as shown in the example blog post. Do not remove or replace the example blog post. - Ping the Gno.land DevRel team, @waymobetta & @leohhhn for a review. After your blog post passes the review process, it will be merged into the `main` branch and shortly after deployed on-chain. From 44660a6a0dc9705d1ffa99627dcbe24dfe14d87b Mon Sep 17 00:00:00 2001 From: leohhhn Date: Mon, 16 Oct 2023 10:17:42 +0200 Subject: [PATCH 12/16] remove wrong detail --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b5032893..d2fcecb6 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -23,7 +23,7 @@ Below are topics of particular interest to us, but we’re open to all suggestio If you've considered the previous section and would like to contribute to the Gno Blog, here are the steps to follow: - Write a blog post you'd like to see included to the Gno Blog, while strictly following the [Style Guide](#gno-blog-style-guide). -- Submit a PR using [this template](templatePR), while following the structure of the folders & naming, as shown in the example blog post. Do not remove or replace the example blog post. +- Submit a PR using [this template](templatePR), while following the structure of the folders & naming, as shown in the example blog post. - Ping the Gno.land DevRel team, @waymobetta & @leohhhn for a review. After your blog post passes the review process, it will be merged into the `main` branch and shortly after deployed on-chain. From 7f62a464442b45af55466f82de568ea272c20c7e Mon Sep 17 00:00:00 2001 From: leohhhn Date: Mon, 16 Oct 2023 10:46:33 +0200 Subject: [PATCH 13/16] add template PR link --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d2fcecb6..9e26081b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -23,7 +23,7 @@ Below are topics of particular interest to us, but we’re open to all suggestio If you've considered the previous section and would like to contribute to the Gno Blog, here are the steps to follow: - Write a blog post you'd like to see included to the Gno Blog, while strictly following the [Style Guide](#gno-blog-style-guide). -- Submit a PR using [this template](templatePR), while following the structure of the folders & naming, as shown in the example blog post. +- Submit a PR using [this template](https://github.com/gnolang/blog/pull/35), while following the structure of the folders & naming, as shown in the example blog post. - Ping the Gno.land DevRel team, @waymobetta & @leohhhn for a review. After your blog post passes the review process, it will be merged into the `main` branch and shortly after deployed on-chain. From f523db49aac7c908457b182aa8376682fcdbcfac Mon Sep 17 00:00:00 2001 From: leohhhn Date: Mon, 16 Oct 2023 10:49:31 +0200 Subject: [PATCH 14/16] added contributing to README --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 2f21d415..676bf68b 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,10 @@ powered by the [`p/demo/blog` library](https://github.com/gnolang/gno/tree/maste The blog posts are written in markdown format, and include a frontmatter prefix to define metadata. +## Contributing a blog post + +See [CONTRIBUTING.md](./CONTRIBUTING.md). + ## CLI ([`./gnoblog-cli`](./gnoblog-cli)) _See [#1](https://github.com/gnolang/blog/issues/1)_ From f051d8074534823fb655bb29ecac172cb15fb2de Mon Sep 17 00:00:00 2001 From: waymobetta Date: Mon, 16 Oct 2023 11:05:52 -0700 Subject: [PATCH 15/16] feat: add tags section, links + cleanup --- CONTRIBUTING.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9e26081b..fed6514b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -41,12 +41,13 @@ Below are some rules to follow when writing a blog post. 6. Fact-check your content. 7. If your post contains images, please add a `src` folder to contain them, and link to them in Markdown. 8. Include front-matter in your blog post, detailing the following: - 1. title, - 2. publication_date, - 3. slug, - 4. tags, - 5. authors. - -If you're unsure of how to style or format something, take a look at previous blog posts in this repo, or ping @waymobetta or @leohhhn for help. + 1. Title + 2. Publication date + 3. Slug + 4. [Tags](#tags) + 5. Authors +#### Tags +Tags, or [hashtags](https://en.wikipedia.org/wiki/Hashtag), should be lowercase and without spaces; eg, #foobar NOT #FooBar. +If you're unsure of how to style or format something, take a look at the [example blog post PR](https://github.com/gnolang/blog/pull/35) or review the other [blog posts in this repo](posts) for inspiration; as a last resort, message [@waymobetta](https://github.com/waymobetta) or [@leohhhn](https://github.com/leohhhn) for help within your PR or issue thread. From 680abefe0890809545fa18649164a58d427020d1 Mon Sep 17 00:00:00 2001 From: waymobetta Date: Mon, 16 Oct 2023 13:20:58 -0700 Subject: [PATCH 16/16] fix: add profile links --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fed6514b..0f2371f8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -24,7 +24,7 @@ Below are topics of particular interest to us, but we’re open to all suggestio If you've considered the previous section and would like to contribute to the Gno Blog, here are the steps to follow: - Write a blog post you'd like to see included to the Gno Blog, while strictly following the [Style Guide](#gno-blog-style-guide). - Submit a PR using [this template](https://github.com/gnolang/blog/pull/35), while following the structure of the folders & naming, as shown in the example blog post. -- Ping the Gno.land DevRel team, @waymobetta & @leohhhn for a review. +- Ping the Gno.land DevRel team, [@waymobetta](https://github.com/waymobetta) and [@leohhhn](https://github.com/leohhhn) for a review. After your blog post passes the review process, it will be merged into the `main` branch and shortly after deployed on-chain.