Skip to content

Commit d8c8bec

Browse files
committed
📝 add Verso page content and Profiles whitepaper
1 parent 5a9d752 commit d8c8bec

File tree

3 files changed

+57
-1
lines changed

3 files changed

+57
-1
lines changed

.gitattributes

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
*.pdf filter=lfs diff=lfs merge=lfs -text

content/pages/verso.md

Lines changed: 56 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,5 +3,60 @@ title = "Verso Browser"
33
path = "verso"
44
+++
55

6-
soon
6+
## Introduction
7+
8+
While `Verso` is in the early stages of development, it's beneficial to understand why it exists.
9+
10+
There are many browsers on the market already, no doubt. Different visions, different budgets.
11+
It's typically a product, that users get for free... despite the fact it is one of the most important tools they use.
12+
The gateway to the `World Wide Web`.
13+
14+
Although, it's only free price-wise. Users usually pay with data, thus they convert themselves to the product.
15+
Many browsers attempt to achieve different goals, and while doing so: play various games.
16+
We are a bit different, **we don't participate in this market competition, we don't have a play**.
17+
18+
## ... then what is this about?
19+
20+
We like to say, it's fluid. In the long run, we'd like to offer an alternative to all the competing browsers, sure.
21+
But not the way you imagine. `Verso` is an experimental browser, and most probably it will remain as such.
22+
23+
If we would like to compete, then we just could make a new browser based on `Verso`, give it a new name, and go!
24+
But instead of it, we focus on the technology.
25+
26+
## What's the fuss about technology?
27+
28+
**We love technology**. We are the kind of people, who not settling down for some "okay" solution.
29+
We are looking for the best solutions that the situation allows, and continuously fixing up and improving everything we can.
30+
31+
In this very mindset, [Rust] and [Servo] were born more than a decade ago.
32+
Both were developed in tandem, to look for new ways of making the technology scene better.
33+
`Rust` is for ensuring memory safety and mitigating other security-critical issues,
34+
while `Servo` is for researching new ways to have newer and better approaches for browsers.
35+
36+
And this is what we are doing here too: developing technology that could be a base for many other new things.
37+
If you think about `Servo` as a web browser engine based on `Rust`,
38+
then think about `Verso` as a web browser framework (based on `Servo`)!
39+
40+
**What you easily could use as a base to ship your own browser**.
41+
42+
### Contribution
43+
44+
It's still unclear what kind of contributions we are after, but any help is appreciated!
45+
To chat with us about the projects, goals, and visions: you could join [our Zulip][zulip].
46+
47+
For the code, check the [GitHub repository][gh-repo]! Especially the `.github/CONTRIBUTING.md`.
48+
49+
## Whitepapers
50+
51+
Sometimes, a few whitepapers could pop up.
52+
They are usually about ideas already matured for a while and are part of some future vision.
53+
...but unless it's over `v1.0`, don't handle it too seriously.
54+
55+
- [Next Generation Browser Profiles Workflow][wp-profiles] (v0.1)
56+
57+
[Rust]: https://rust-lang.org
58+
[Servo]: https://servo.org
59+
[gh-repo]: https://github.com/versotile-org/verso
60+
[zulip]: https://versotile.zulipchat.com/
61+
[wp-profiles]: /whitepapers/verso-wp_profiles_v0.1.pdf
762

131 Bytes
Binary file not shown.

0 commit comments

Comments
 (0)