git.iko.soy/urbit.org
on master help sign in
fixing the links to point to interface
e5eb1bdMatilde Park
content/understanding-urbit/roadmap.md+2−2
compare with master
unifiedsplit
@@ -1,6 +1,6 @@
1+++
1+++
2title = "Roadmap: OS 1 -> OS N"
2title = "Roadmap: OS 1 -> OS N"
3−description = "What Urbit will feel like to an everyday user"
3+description = "The core ideas that Urbit is built around"
4weight = 4
4weight = 4
5[extra]
5[extra]
6flatten_pagination = "true"
6flatten_pagination = "true"
@@ -10,7 +10,7 @@ hide_previous_title = "true"
10
10
11Today, we call Urbit an ‘OS 0’. It’s an evolving open source project with a live network. In 2020, we’re planning to ship OS 1 — the first minimal but complete release of Urbit.
11Today, we call Urbit an ‘OS 0’. It’s an evolving open source project with a live network. In 2020, we’re planning to ship OS 1 — the first minimal but complete release of Urbit.
12
12
13−We see Urbit’s primary advantage as bringing together groups to share a set of modules for communication and collaboration. As Urbit matures, the set of available modules grows and expands, and the system both stabilizes and becomes more secure.
13+As we discussed in the [last post](/understanding-urbit/interface), we see Urbit’s primary advantage as bringing together groups to share a set of modules for communication and collaboration. As Urbit matures, the set of available modules grows and expands, and the system both stabilizes and becomes more secure.
14
14
15Let’s walk through the sequence of milestones we have planned for 2020 and 2021.
15Let’s walk through the sequence of milestones we have planned for 2020 and 2021.
16
16
content/understanding-urbit/urbit-os.md+2−2
@@ -23,7 +23,7 @@ Today, we’re more or less back to the timesharing model of the 1970s. Urbit OS
23
23
24Let’s talk about how we think we’re going to pull this off from a technical standpoint, and our vision for using Urbit.
24Let’s talk about how we think we’re going to pull this off from a technical standpoint, and our vision for using Urbit.
25
25
26−If you’d like to skip ahead to what Urbit will be like to use [go ahead](/understanding-urbit/roadmap). Or if you’re someone who just wants to head to the source, [it’s here](https://github.com/urbit/urbit#urbit). In that case you may also want to [read the docs](https://urbit.org/docs/) to get up and running.
26+If you’d like to skip ahead to what Urbit will be like to use [go ahead](/understanding-urbit/interface). Or if you’re someone who just wants to head to the source, [it’s here](https://github.com/urbit/urbit#urbit). In that case you may also want to [read the docs](https://urbit.org/docs/) to get up and running.
27
27
28<img class="ba" src="https://media.urbit.org/site/understanding-urbit/technical-overview/technical-overview-kernel@2x.png">
28<img class="ba" src="https://media.urbit.org/site/understanding-urbit/technical-overview/technical-overview-kernel@2x.png">
29
29
@@ -49,7 +49,7 @@ This sounds like a lot — but the whole stack is incredibly compact. The whole
49
49
50But why did we build all this technology?
50But why did we build all this technology?
51
51
52−First and foremost, to deliver a better user experience. Urbit OS alone is just a new layer for personal computing in the cloud. But with this new layer we open up the possibility of building a completely unified interface for people to compute in the cloud. (If you’d like to skip to how we envision that interface [go for it](/understanding-urbit/roadmap).)
52+First and foremost, to deliver a better user experience. Urbit OS alone is just a new layer for personal computing in the cloud. But with this new layer we open up the possibility of building a completely unified interface for people to compute in the cloud. (If you’d like to skip to how we envision that interface [go for it](/understanding-urbit/interface).)
53
53
54From a broader perspective, it’s clear that connected computing is important and that it’s here to stay. We just want it to be as calm, simple and reliable as possible, and we don’t think can happen using existing technology.
54From a broader perspective, it’s clear that connected computing is important and that it’s here to stay. We just want it to be as calm, simple and reliable as possible, and we don’t think can happen using existing technology.
55
55