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
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,6 @@ This repository contains code and content for the [IPFS Blog & News](https://blo
12
12
13
13
**If you just want to submit a link (event, academic paper, tutorial, video or news coverage) to add to the site, [use this easy form](https://airtable.com/shrNH8YWole1xc70I)!**
14
14
15
-
16
15
## For post authors/editors
17
16
18
17
While it's possible to manually PR a new blog post from a local build, **you are strongly encouraged to [use this site's Forestry integration](https://forestry.io) for drafting and editing new content.** Using Forestry offers you WYSIWYG editing (in addition to raw markdown mode), easy image upload/crop tools, and instant previews. If you're an IPFS core team member and don't have Forestry access, contact Jessica Schilling.
@@ -26,33 +25,37 @@ Forestry uses the `staging` branch as a work-in-progress scratchpad for blog con
26
25
- To switch between WYSIWYG and raw markdown while writing a blog post, choose "Raw Editor" or "WYSIWYG Editor" from the dots menu at the top right of the page (this is useful if you want to add any HTML, such as a video or Twitter embed):<br/>
27
26
28
27
### Forestry build preview tips
28
+
29
29
While WYSIWYG mode usually gives you a good enough idea of what a blog post will look like, you can also load Forestry's own _build preview_ in a new tab by clicking the eye icon at the top right of the page:<br/>
30
30
31
31
This build preview lets you preview changes to any content type (not just blog posts), and _does not_ require you to save your changes in order to see them.
32
32
33
33
A few tips:
34
+
34
35
- Click the eye icon to _regenerate_ a build preview at any time from a Forestry edit page. You may need to reload the build preview tab if you don't see changes come through immediately.
35
36
- Occasionally, a build preview page gets stuck at a URL ending in `forestry/pending` or simply won't load. In this case, try the following:
36
-
- Remove `forestry/pending` from the URL and try again.
37
-
- Check the Previews section of Forestry's [`Site > Settings` page](https://app.forestry.io/sites/lg5t7mxcqbr-da/#/settings/previews) to see the preview server's current status, start/stop/restart the server, or examine the logs for errors. Simply restarting the preview server can fix many problems.
38
-
- If all else fails, save your changes, wait a few minutes, and take a look at [Fleek's build of the latest version of the `staging` branch](https://ipfs-blog-staging.on.fleek.co/). It's a considerably slower build/deploy time, but does reflect the latest changes once it finishes deploying.
37
+
- Remove `forestry/pending` from the URL and try again.
38
+
- Check the Previews section of Forestry's [`Site > Settings` page](https://app.forestry.io/sites/lg5t7mxcqbr-da/#/settings/previews) to see the preview server's current status, start/stop/restart the server, or examine the logs for errors. Simply restarting the preview server can fix many problems.
39
+
- If all else fails, save your changes, wait a few minutes, and take a look at [Fleek's build of the latest version of the `staging` branch](https://ipfs-blog-staging.on.fleek.co/). It's a considerably slower build/deploy time, but does reflect the latest changes once it finishes deploying.
39
40
40
41
### To deploy to the live site
41
42
42
43
Changes you _save_ in Forestry are written directly to the `staging` branch and automatically generate a staging preview at https://ipfs-blog-staging.on.fleek.co/.
43
44
44
-
**Once a staged post is ready to go live, please PR `staging` to `main` using [this handy shortcut](https://github.com/ipfs/ipfs-blog/compare/main...staging?expand=1).***Note that if multiple posts are in-flight in staging and only one is approved to go live, your PR may need some massaging by a reviewer.*
45
+
**Once a staged post is ready to go live, please PR `staging` to `main` using [this handy shortcut](https://github.com/ipfs/ipfs-blog/compare/main...staging?expand=1).**_Note that if multiple posts are in-flight in staging and only one is approved to go live, your PR may need some massaging by a reviewer._
45
46
46
47
_Note for PR reviewers: While we continue to dogfood Forestry, please leave your edits in comments rather than making additional commits._ As our overall workflow continues to solidify, this direction may change.
47
48
48
49
### To add a URL redirect for a blog post
50
+
49
51
Please add a new line to [`src/.vuepress/redirects`](https://github.com/ipfs/ipfs-blog/blob/main/src/.vuepress/redirects) and make a PR of the change to `main`.
50
52
51
53
## For site developers
52
54
53
55
⚠️ **Important!** All _site development work_ (as opposed to blog posts) should be based on and merged into `main`, **not**`staging`.
54
56
55
57
### Build and run locally
58
+
56
59
This site is built in [Vuepress](https://vuepress.vuejs.org/guide/), and uses Vue/JavaScript for functional code and Markdown for post content.
57
60
58
61
To build a local copy, run the following:
@@ -81,6 +84,7 @@ To build a local copy, run the following:
81
84
You can close the local server with `CTRL` + `c`. To restart the local server, run `npm start` from inside the `ipfs-blog` directory.
82
85
83
86
### PR and preview
87
+
84
88
Once you're happy with your local changes, please make a PR **against the `main` branch**. Including detailed notes on your PR - particularly screenshots to depict any changes in UI - will help speed up approval and deployment.
85
89
86
90
All PRs against `main` automatically generate Fleek previews to make it easier to "check your work". You can view your PR's preview by clicking `Details` in the `fleek/build` check at the bottom of your PR page:<br/>
Feature parity with go-ipfs just got a whole lot closer!
14
14
15
15
<blockquoteclass="twitter-tweet"data-conversation="none"data-lang="en"><plang="en"dir="ltr">js-ipfs 0.30 has been released live at the <ahref="https://twitter.com/hashtag/IPFS?src=hash&ref_src=twsrc%5Etfw">#IPFS</a> Dev Meeting. Thank you everyone for all the love ❤️ <ahref="https://t.co/YB9NfGM7WC">https://t.co/YB9NfGM7WC</a> and big hi5 to <ahref="https://twitter.com/_alanshaw?ref_src=twsrc%5Etfw">@_alanshaw</a> for driving the whole release forward and being an awesome Lead Maintainer for <ahref="https://twitter.com/hashtag/JS?src=hash&ref_src=twsrc%5Etfw">#JS</a> <ahref="https://twitter.com/hashtag/IPFS?src=hash&ref_src=twsrc%5Etfw">#IPFS</a> 🚀 <ahref="https://t.co/6arftXUxBe">pic.twitter.com/6arftXUxBe</a></p>— David Dias (@daviddias) <ahref="https://twitter.com/daviddias/status/1016364733107228673?ref_src=twsrc%5Etfw">July 9, 2018</a></blockquote>
@@ -68,4 +68,4 @@ Would you like to contribute to the IPFS project and don't know how? Well, there
68
68
69
69
The best place to ask your questions about IPFS, how it works and what you can do with it is at [discuss.ipfs.io](http://discuss.ipfs.io). We are also available at the #ipfs channel on Freenode.
70
70
71
-
That is all for this post. Thank you for being part of the community. I bid you a good day!
71
+
That is all for this post. Thank you for being part of the community. I bid you a good day!
> URL safe CIDs, refs commands, DOM File support and more!
14
14
15
15
<blockquoteclass="twitter-tweet"data-lang="en"><plang="en"dir="ltr">A wild and excitable JS <ahref="https://twitter.com/hashtag/IPFS?src=hash&ref_src=twsrc%5Etfw">#IPFS</a> 0.36 just darted across the street and into the npm module store 🏇💨. It's got 🧬 Base32 encoded v1 CIDs, 👉 refs and refs local commands, 🗄 support for adding DOM File objects and loads more! <ahref="https://t.co/zIFEfQX325">https://t.co/zIFEfQX325</a></p>— Alan Shaw (@_alanshaw) <ahref="https://twitter.com/_alanshaw/status/1131145571408986112?ref_src=twsrc%5Etfw">May 22, 2019</a></blockquote>
@@ -180,4 +180,4 @@ Would you like to contribute to the IPFS project and don't know how? Well, there
180
180
181
181
# ⁉️ Do you have questions?
182
182
183
-
The best place to ask your questions about IPFS, how it works and what you can do with it is at [discuss.ipfs.io](http://discuss.ipfs.io). We are also available at the `#ipfs` channel on Freenode.
183
+
The best place to ask your questions about IPFS, how it works and what you can do with it is at [discuss.ipfs.io](http://discuss.ipfs.io). We are also available at the `#ipfs` channel on Freenode.
If you're a regular reader of the IPFS blog, you might notice something a little different around here: **The IPFS Starlog is now the new and improved**[**IPFS Blog & News**](/)**!**
11
+
12
+
If you're a regular reader of the IPFS blog, you might notice something a little different around here: **The IPFS Starlog is now the new and improved**[**IPFS Blog & News**](/)**!**
13
13
14
14
## What's new
15
15
16
16
Starting with rounds of user interviewing and testing at the end of 2020, we set about improving this blog to give the global IPFS community more of what readers asked for: more worldwide IPFS news, more links to tutorials and other learning resources, and an easier place to find information about things like IPFS events and the latest release notes for IPFS projects and repos. To that end, we're excited to say that this new IPFS Blog & News site is your home for **not only the latest from the IPFS blog, but also info on ...**
17
17
18
-
*[**Events**](/?category=Event), hackathons, and other virtual and real-world get-togethers
19
-
*[**News coverage**](/?category=News%20coverage) from global media sources
20
-
*[**IPFS tutorials**](/?category=Tutorial) and other how-tos from across the internet
21
-
*[**Videos**](/?category=Video) on IPFS and related projects that have made the blog team go "wow"
22
-
*[**Release notes**](/?category=Release%20notes) for `go-ipfs`, `js-ipfs`, GUI tools like IPFS Companion and IPFS Desktop, and other key projects and repos
-[**Events**](/?category=Event), hackathons, and other virtual and real-world get-togethers
19
+
-[**News coverage**](/?category=News%20coverage) from global media sources
20
+
-[**IPFS tutorials**](/?category=Tutorial) and other how-tos from across the internet
21
+
-[**Videos**](/?category=Video) on IPFS and related projects that have made the blog team go "wow"
22
+
-[**Release notes**](/?category=Release%20notes) for `go-ipfs`, `js-ipfs`, GUI tools like IPFS Companion and IPFS Desktop, and other key projects and repos
Plus, we've added **subject tags**, **author indexing**, and **text search** to make it easier to find just what you're looking for — and to explore new ideas and topics from there.
26
26
@@ -32,4 +32,4 @@ Ever wanted to be a citizen reporter? Here's your chance. As a member of the glo
32
32
33
33
## And thanks are in order ...
34
34
35
-
Big thanks to everyone in the IPFS community who was a part of the relaunch — suggesting features, taking part in user testing, writing the code, or adding blog posts and links. We look forward to your thoughts on the new blog & news site ... and don't forget, you can always submit news links, events, papers, tutorials or videos yourself by using [this handy form](https://airtable.com/shrNH8YWole1xc70I).
35
+
Big thanks to everyone in the IPFS community who was a part of the relaunch — suggesting features, taking part in user testing, writing the code, or adding blog posts and links. We look forward to your thoughts on the new blog & news site ... and don't forget, you can always submit news links, events, papers, tutorials or videos yourself by using [this handy form](https://airtable.com/shrNH8YWole1xc70I).
[IPFS](//ipfs.io/) is a new hypermedia distribution protocol, addressed by content and identities, aiming to make the web faster, safer, and more open. In these posts, we highlight some of the development that has happened in the past week. For anyone looking to get involved, follow the embedded hyperlinks, search the wealth of information on [GitHub](//github.com/ipfs) or join us on [IRC](//webchat.freenode.net/?channels=ipfs) (#ipfs on the Freenode network).
13
13
14
14
Here are some of the highlights for the [January 5th](//github.com/ipfs/pm/issues/77) Sprint:
@@ -53,4 +53,4 @@ Thanks, and see you next week! If you have cool things to share for the next wee
53
53
54
54
- Richard Littauer and Andrew Chin
55
55
56
-
_Submit feedback about this issue [here](//github.com/ipfs/weekly/issues/10), or send us [feedback about the IPFS Weekly in general](//github.com/ipfs/weekly/issues/7)._
56
+
_Submit feedback about this issue [here](//github.com/ipfs/weekly/issues/10), or send us [feedback about the IPFS Weekly in general](//github.com/ipfs/weekly/issues/7)._
[IPFS](//ipfs.io/) is a new hypermedia distribution protocol, addressed by content and identities, aiming to make the web faster, safer, and more open. In these posts, we highlight some of the development that has happened in the past week. For anyone looking to get involved, follow the embedded hyperlinks, search the wealth of information on [GitHub](//github.com/ipfs) or join us on [IRC](//webchat.freenode.net/?channels=ipfs) (#ipfs on the Freenode network).
13
13
14
14
If you would like to get this update as an email, sign up for our [weekly newsletter](http://eepurl.com/gL2Pi5)!
@@ -149,4 +149,4 @@ Thanks, and see you next week! If you have cool things to share for the next wee
149
149
150
150
- Richard Littauer and Andrew Chin
151
151
152
-
_Submit feedback about this issue [here](//github.com/ipfs/weekly/pull/14), or send us [feedback about the IPFS Weekly in general](//github.com/ipfs/weekly/issues/7)._
152
+
_Submit feedback about this issue [here](//github.com/ipfs/weekly/pull/14), or send us [feedback about the IPFS Weekly in general](//github.com/ipfs/weekly/issues/7)._
[IPFS](//ipfs.io/) is a new hypermedia distribution protocol, addressed by content and identities, aiming to make the web faster, safer, and more open. In these posts, we highlight some of the development that has happened in the past week. For anyone looking to get involved, follow the embedded hyperlinks, search the wealth of information on [GitHub](//github.com/ipfs) or join us on [IRC](//webchat.freenode.net/?channels=ipfs) (#ipfs on the Freenode network).
13
13
14
14
If you would like to get this update as an email, sign up for our [weekly newsletter](http://eepurl.com/gL2Pi5)!
@@ -112,4 +112,4 @@ Thanks, and see you next week! If you have cool things to share for the next wee
112
112
113
113
- Richard Littauer and Andrew Chin
114
114
115
-
_Submit feedback about this issue [here](https://github.com/ipfs/weekly/pull/16), or send us [feedback about the IPFS Weekly in general](//github.com/ipfs/weekly/issues/7)._
115
+
_Submit feedback about this issue [here](https://github.com/ipfs/weekly/pull/16), or send us [feedback about the IPFS Weekly in general](//github.com/ipfs/weekly/issues/7)._
0 commit comments