git.iko.soy/urbit.org
on master help sign in
fixing the links to point to interface
commite5eb1bdd33d08ace191fa8d88160860b4a019f3d authorMatilde Park <matilde@tlon.io> dateThu 19 Dec 2019, 13:13 (7 years ago) parentde2d548
2 files changed+4−4
compare with master
unifiedsplit
content/understanding-urbit/roadmap.md+2−2 content/understanding-urbit/urbit-os.md+2−2
content/understanding-urbit/roadmap.md+2−2
@@ -1,6 +1,6 @@
11+++
22title = "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"
44weight = 4
55[extra]
66flatten_pagination = "true"
@@ -10,7 +10,7 @@ hide_previous_title = "true"
1010
1111Today, 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.
1212
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.
1414
1515Let’s walk through the sequence of milestones we have planned for 2020 and 2021.
1616
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
2323
2424Let’s talk about how we think we’re going to pull this off from a technical standpoint, and our vision for using Urbit.
2525
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.
2727
2828<img class="ba" src="https://media.urbit.org/site/understanding-urbit/technical-overview/technical-overview-kernel@2x.png">
2929
@@ -49,7 +49,7 @@ This sounds like a lot — but the whole stack is incredibly compact. The whole
4949
5050But why did we build all this technology?
5151
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).)
5353
5454From 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.
5555