Name Date Size

..27-Apr.-20224 KiB

.eslintrcH A D21-Jan.-2021439

.gitignoreH A D06-Apr.-202117

.gitlab-ci/H01-Mar.-20224 KiB

.gitlab-ci.ymlH A D30-Mar.-20223.3 KiB

.run-scan-buildH A D16-Dec.-202181

CONTRIBUTING.mdH A D13-Oct.-20212.4 KiB

COPYINGH A D11-Jul.-201934.3 KiB

data/H19-May-20224 KiB

embed/H25-Jun.-20224 KiB

epiphany.doapH A D24-Jun.-20222.1 KiB

generate-canary-manifest.pyH A D03-May-20223.7 KiB

HACKING.mdH A D17-Feb.-202210.2 KiB

help/H03-Jun.-20224 KiB

lib/H03-Jun.-20224 KiB

meson.buildH A D17-Jun.-20225.5 KiB

meson_options.txtH A D17-Jun.-2022714

NEWSH A D19-May-2022283.3 KiB

org.gnome.Epiphany.Canary.json.inH A D17-Jun.-20224.6 KiB

org.gnome.Epiphany.jsonH A D13-May-20224.3 KiB

po/H03-Jul.-20224 KiB

post_install.pyH A D11-Jul.-20191,017

README.mdH A D07-Mar.-20225.8 KiB

src/H28-Jun.-20224 KiB

tests/H07-May-20224 KiB

third-party/H11-Aug.-20214 KiB

TODOH A D11-Jul.-2019837

README.md

1# GNOME Web
2
3GNOME Web (codename: Epiphany) is a GNOME web browser based on
4[the WebKit rendering engine](https://webkit.org/). The codename means "a
5usually sudden manifestation or perception of the essential nature or meaning of
6something" ([Merriam-Webster](https://www.merriam-webster.com/dictionary/epiphany)).
7
8Epiphany is opinionated.
9
10## Download and Install
11
12Epiphany is designed for Linux systems. The recommended way to install Epiphany
13is via [Flatpak](https://www.flatpak.org/). You may:
14
15 * [Download the latest stable version from Flathub](https://flathub.org/apps/details/org.gnome.Epiphany)
16   (recommended).
17 * [Download Epiphany Technology Preview](https://nightly.gnome.org/repo/appstream/org.gnome.Epiphany.Devel.flatpakref)
18   if you are adventurous and want to help test tomorrow's Epiphany today. It
19   is **not stable**.
20
21 * [Download Epiphany
22   Canary](https://nightly.gnome.org/repo/appstream/org.gnome.Epiphany.Canary.flatpakref)
23   if you are even more adventurous and want to help test the most recent
24   development versions of WebKitGTK and Epiphany. This flavor of Epiphany is
25   more likely to be **very unstable** because the code being built comes
26   directly from WebKit's SVN trunk branch and Epiphany's git master branch.
27 
28Epiphany is probably also available via your operating system's package manager,
29but such packages are often outdated and insecure. Flatpak is the best
30application distribution mechanism for Linux.
31
32## Building from Source
33
34### The Easy Way
35
36The recommended way to build Epiphany locally is using the flatpak-builder
37manifest with GNOME Builder. After installing Builder and launching it, you'll
38see the Select a Project page. Select Open, then select the toplevel Epiphany
39directory. Builder will detect the org.gnome.Epiphany.json flatpak-builder
40manifest and you will be able to build the project in Builder. All required
41dependencies will be provided by the manifest.
42
43### Building Manually
44
45Epiphany uses the [Meson build system](http://mesonbuild.com/). You can build
46Epiphany the same way you would any software that uses Meson. For example:
47
48```
49$ mkdir build && cd build
50$ meson ..
51$ ninja
52$ sudo ninja install
53```
54
55Meson is the best build system.
56
57You will have to install several pkg-config dependencies. If you are missing a
58dependency, meson will present an error that looks like this:
59
60```
61meson.build:84:0: ERROR:  Native dependency 'hogweed' not found
62```
63
64In RPM-based distributions, you can install the missing dependencies
65automatically. For example, in Fedora:
66
67```
68$ sudo dnf install 'pkgconfig(hogweed)'
69```
70
71In deb-based distributions:
72
73```
74$ sudo apt install $(apt-file search --package-only hogweed)
75```
76
77In other distributions, you must research each dependency to determine which
78package provides the required pkg-config file.
79
80### Rebuilding Dependencies
81
82If you need to rebuild dependencies, the recommended solution is to use JHBuild.
83See [the development page](https://wiki.gnome.org/Apps/Web/Development#Step_3:_Developing_Dependencies_with_Epiphany)
84for more information.
85
86## Manifesto
87
88A web browser is more than an application: it is a way of thinking, a way of
89seeing the world. Epiphany's principles are simplicity, standards compliance,
90and software freedom.
91
92### Simplicity
93
94Feature bloat and user interface clutter is evil.
95
96Epiphany aims to present the simplest interface possible for a browser. Simple
97does not necessarily mean less-powerful. The commonly-used browsers of today are
98too big, buggy, and bloated. Epiphany is a small browser designed for the web:
99not for mail, newsgroups, file management, instant messaging, or coffeemaking.
100The UNIX philosophy is to design small tools that do one thing and do it well.
101
102### Standards Compliance
103
104The introduction of nonstandard features in browsers could make it difficult
105or impossible to use alternative products like Epiphany if developers embrace
106them. Alternative standards-complying browsers might not be able to fully access
107websites making use of these features. The success of nonstandard features can
108ultimately lead one browser to dominate the market.
109
110Standards compliance ensures the freedom of choice. Epiphany aims to achieve
111this.
112
113### Software Freedom
114
115Epiphany is not just free of cost; more importantly, the source code is made
116available to you under a license that [respects your freedom](https://www.gnu.org/philosophy/philosophy.html).
117
118Just as GNOME exists to oppose proprietary desktop software, Epiphany opposes
119the dominance of the web by proprietary software web browsers. Today's chief
120offender is Google Chrome, a browser that purports to be open source, yet
121actually includes several proprietary components. In contrast, Epiphany is fully
122free software.
123
124## Human Interface
125
126Epiphany follows the [GNOME Human Interface Guidelines](https://developer.gnome.org/hig).
127Unless there are serious reasons to make an exception, not following the
128guidelines will be considered a bug.
129
130### GNOME Integration
131
132Epiphany's main goal is to be integrated with GNOME, as well as similar
133desktops (notably elementary OS). We don't aim to make Epiphany usable outside
134these environments.
135
136### Preferences
137
138We are cautious about adding new preferences. Preferences can be added when they
139make sense, but they should always be carefully-considered.
140[Preferences come with a cost](https://ometer.com/preferences.html).
141
142### Target Audience
143
144We target nontechnical users by design. This happens to be 90% of the user
145population. Technical details should not exposed in the interface.
146
147We target web users, not web developers. A few geek-oriented features, like the
148web inspector, are welcome so long as they are non-obtrusive.
149
150## Website
151
152[Epiphany has a website,](https://wiki.gnome.org/Apps/Web) though there is not
153very much content there.
154
155## Contact Us
156
157The recommended way to contact us is via the Epiphany mailing list
158<epiphany-list@gnome.org>.
159