Note: Ubuntu distributes GNOME Software as a Snap in versions 20.04 to 23.04, and replaced it with App Center in 23.10 and newer—neither of which support installing Flatpak apps. Installing the Flatpak plugin will also install a deb version of GNOME Software, resulting in two "Software" apps being installed at the same time on Ubuntu 20.04 to 23.04, and a single new "Software" app on Ubuntu 23.10 and newer.
Flatpak is installed by default on Fedora Workstation, Fedora Silverblue, and Fedora Kinoite. To get started, all you need to do is enable Flathub, which is the best way to get Flatpak apps. Flathub is pre-configured as a part of the Third-Party Repositories. Alternatively, you can download and install the Flathub repository file.
The above links should work on the default GNOME and KDE Fedora installations, but if they fail for some reason you can manually add the Flathub remote by running:
Flatpak is installed by default on Manjaro 20 or higher.
+
To enable its support, navigate to the Software Manager (Add/Remove Programs)
+
Click on the triple line menu [or dots depending on the Desktop Environment] on the right, in the drop down menu select "Preferences"
+
Navigate to the "Flatpak" tab and slide the toggle to Enable Flatpak support (it is also possible to enable checking for updates, which is recommended).
'
+ - name: Restart
+ text: '
+
To complete setup, restart your system. Now all you have to do is install apps!
Flatpak applications can be installed on ChromeOS with the Crostini Linux compatibility layer. This is not available for all ChromeOS devices, so you should ensure your device is compatible before proceeding. A list of compatible devices is maintained here.
+ steps:
+ - name: Enable Linux support
+ text: '
+
Navigate to chrome://os-settings, and scroll down to Developers and turn on Linux development environment. ChromeOS will take some time downloading and installing Linux.
'
+ - name: Start a Linux terminal
+ text: '
+
Press the Search/Launcher key, type "Terminal", and launch the Terminal app.
'
+ - name: Install Flatpak
+ text: '
+
To install Flatpak, run the following in the terminal:
To complete setup, restart Linux. You can do this by right-clicking terminal, and then clicking "Shut down Linux". Now all you have to do is install apps!
'
+
+- name: Red Hat Enterprise Linux
+ logo: "redhat.svg"
+ introduction: >
+
Flatpak is installed by default on Red Hat Enterprise Linux Workstation 9 and newer. To get started, all you need to do is enable Flathub, which is the best way to get Flatpak apps. Just download and install the Flathub repository file.
+
To install Flatpak on Red Hat Enterprise Linux Workstation 8 or older, run the following in a terminal:
The above links should work on the default Red Hat Enterprise Linux Workstation 9 installation, but if they fail for some reason you can manually add the Flathub remote by running:
+ flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
+
+- name: Linux Mint
+ logo: "mint.svg"
+ introduction: >
+
Flatpak support is built into Linux Mint 18.3 and newer—no setup required!
Flatpak is available in the default repositories of all currently maintained openSUSE Leap and openSUSE Tumbleweed versions.
+
If you prefer a graphical installation, you can install Flatpak using a "1-click installer" from software.opensuse.org. If your distribution version is not shown by default, click Show under Unsupported distributions category and then select from the list.
+
Alternatively, install Flatpak from the command line using Zypper:
Flatpak is installed by default on Rocky Linux 8 and newer, when installed with a software selection that includes GNOME (Server with GUI, Workstation). If you are using such a system, you may skip this step. To install Flatpak on Rocky Linux, run the following in a terminal:
Flatpak is installed by default on CentOS Stream 8 and newer, when using GNOME. To get started, all you need to do is enable Flathub, which is the best way to get Flatpak apps. Just download and install the Flathub repository file.
Flatpak is installed by default on AlmaLinux 8 and newer, when using GNOME. To get started, all you need to do is enable Flathub, which is the best way to get Flatpak apps. Just download and install the Flathub repository file.
Flatpak can be installed from the community repository. Run the following in a terminal:
+ doas apk add flatpak"
+ - name: Install the Software Flatpak plugin
+ text: "
+
You can install the Flatpak plugin for either the GNOME Software (since v3.13) or KDE Discover (since v3.11), making it possible to install apps without needing the command line. To install, for GNOME Software run:
+ doas apk add gnome-software-plugin-flatpak
+
For KDE Discover run:
+ doas apk add discover-backend-flatpak"
+ - name: Add the Flathub repository
+ text: '
+
Flathub is the best place to get Flatpak apps. To enable it, download and install the Flathub repository file or run:
Flatpak support is built into OpenMandriva for all actively supported versions, starting from the stable/fixed release 'Rock 5.0', through the development release 'Cooker', and ending with the rolling release 'ROME'.
+
Flatpak comes with the pre-configured Flathub repository.
elementary OS 5.1 and newer comes with Flatpak support out of the box. For non-curated apps, head to Flathub to install any app using the big "Install" button, and open the downloaded `.flatpakref` file with Sideload.
+
Note: After installing one app from a remote like Flathub, all other apps from that remote will also automatically show up in AppCenter.
Flatpak is installed by default on PureOS. To get started, all you need to do is enable Flathub, which is the best way to get Flatpak apps. Just download and install the Flathub repository file.
To complete setup, restart your system. Now all you have to do is install apps!
'
+
+- name: MX Linux
+ logo: "mxlinux.svg"
+ steps:
+ - name: Enable Flatpak through the Software Manager
+ text: '
+
Flatpak support is built in from MX 18 and later. It is only required to activate the Flathub repository following these instructions:
+
Open MX Package Installer (open the menu and look in MX Tools), select the "Flatpaks" tab, to activate the repository you will need to enter the root password.
'
+ - name: Restart
+ text: '
+
To complete setup, restart your system. Now all you have to do is install apps!
-:markdown
- # Announcing Flatpak – Next Generation Linux Applications
-
- Stockholm, Sweden – 20th June 2016 – The development team behind Flatpak is excited to announce the general availablity of their new framework for desktop applications on Linux. Previously named xdg-app, [Flatpak is available on a range of major Linux distributions](http://flatpak.org/getting.html).
-
- ## Build once, run anywhere
-
-
-
- The Linux desktop has long been held back by platform fragmentation. This has been a burden on developers, and creates a high barrier to entry for third party application developers. Flatpak aims to change all that. From the very start its primary goal has been to allow the same application to run across a myriad of Linux distributions and operating systems. In doing so, it greatly increases the number of users that application developers can easily reach.
-
- Speaking about the goals behind Flatpak, Alexander Larsson, its lead developer, said: “Application developers on Linux have always been prevented from having a direct relationship with their users. With Flatpak we're aiming to change that, so developers know exactly what their users are getting. With this launch we are making that goal a reality.”
-
- Flatpak has been available for a range of Linux distributions for several weeks. It allows application developers to build against a series of stable platforms (known as runtimes), as well as to bundle libraries directly within their applications. Flatpak is also standards compliant, offering support for the [Open Container Initiative](https://www.opencontainers.org/) specification.
-
- A growing range of applications are already available as Flatpaks, including Firefox, LibreOffice, the GIMP, InkScape, MyPaint, Darktable, and a large number of stock GNOME applications. [flatpak.org provides instructions on how to easily try these yourself](/apps.html). Linux desktops are also adopting Flatpak. A fully functional GNOME runtime has been available since March: this allows application developers to build and distribute Flatpaks using the GNOME development stack. Work on a similar runtime for KDE is proceeding.
-
- Not only does Flatpak provide cross-distribution installation, but it also allows forward compatibility. Michael Meeks, Director of [The Document Foundation](https://www.documentfoundation.org/), said: “Until now, building a LibreOffice that works for every Linux user has involved some horrible compromises caused by the need to build our binaries on an ancient Linux version to get good forward compatibility. Flatpak will enable us (as a Linux ISV) to distribute a better LibreOffice, with up-to-date dependencies and a platform that can run on many systems. I'm excited to see that happen.”
-
- ## Security first
-
- Another area where the Linux desktop has been weak is security: it has never had a viable model for isolating applications, or for gatekeeping access to user data. This is another area where Flatpak aims to upset the status quo. To this end, it has been built from the ground up with security in mind.
-
- Flatpak apps are sandboxed. From within the sandbox, the only things the app can “see” are itself and a limited set of libraries and operating system interfaces. This effectively isolates apps from each other as well as from the host system and makes it much harder for applications to steal user data or exploit one another.
-
- Initial Flatpak releases have concentrated on application building, distribution and installation, and while the foundations of sandboxing are in place, there are still missing pieces. “The next major Flatpak release will be all about sandboxing”, says Larsson. “Application authors will see a much more complete set of interfaces for interacting with the operating system from within a sandbox.”
-
- Another major part of this work is the widescale move towards the Wayland display server on Linux. X11 is inherently insecure, which makes it impossible to sandbox applications that are using it. In that sense, the growing maturity of Wayland complements Flatpak's emergence, and paves the way for much more complete security model for Linux distributions.
-
- ## Background to Flatpak
-
- [](/img/CC-BY-SA-4.0-Garrett-LeSage.jpg)
-
- Flatpak is the brainchild of Alexander Larsoon, Principal Software Engineer at Red Hat. Larson has been working in the Linux desktop space for 18 years. He was the principal author of GVfs (GNOME's Virtual Filesystem) and has done critical work on Docker, the SPICE protocol, the Gecko rendering engine, GLib and GTK+. He has considerable experience in the area of application bundling.
-
- Flatpak builds on several cutting edge technologies. Under the hood, it makes significant use of [OSTree](https://ostree.readthedocs.org), which can be described as “Git for large binaries”. This provides much of the functionality for hosting software repositories. It also makes Flatpak extremely efficient: applications and libraries that are installed with Flatpak are de-duplicated, saving disk space; “static deltas” reduce the size of downloads for software updates.
-
- For sandboxing, Flatpak makes use of the [Bubblewrap](https://github.com/projectatomic/bubblewrap) utilty, as well as several Linux kernel features (such as cgroups and namespaces), which helps to make it portable across distributions.
-
- ## Rapid community growth and adoption
-
- It is well known that Fedora is making plans around Flatpak. Commenting on Flatpak, Christian F.K. Schaller (Senior Manager at Red Hat and member of the Fedora Workstation Working Group) stated: “The Fedora Workstation team are very excited about Flatpak and the prospects it brings for making the Linux desktop easier to develop for. We plan to continue supporting this effort going forward and help advocate it to a wider audience."
-
- There is also interest from other parties. One early adopter of Flatpak is [Endless Computers](https://endlessm.com/). Speaking about the launch of Flatpak, Jonathan Blandford (VP of Software Engineering at Endless) said: “The Flatpak launch represents a major milestone in providing a unified context for Linux developers. At Endless, we’re proud to be a part of this movement and have fully embraced Flatpak by readily converting all of our applications for our upcoming release and continuing to build new Flatpak apps. We encourage others to do so as well in what we hope to be a revolution among Linux app creation and adoption.”
-
- 
-
- Other distributions are showing interest, as well as other Free Software companies. Simon McVittie is Senior Software Engineer at Collabora and a Debian developer, and is himself looking to Flatpak: “Bringing Flatpak technology into Debian enables us to run applications in a predictable environment with their most suitable library stack, without compromising the base OS's stability and flexibility. Flatpak also retains the ability to deploy security updates, making it a significant enhancement for the many Debian-based desktop and embedded distributions, both in the community and in commercial products.”
-
- One reason for the increasing interest in Flatpak is due to its adaptability and the fact that it is a genuinely upstream project. It can be used and adapted as part of downstream and bespoke solutions, is hosted on Freedesktop.org and Github, and is licensed with the LGPL, with no copyright assignment or contributor license agreement required.
-
- Larsson is obviously pleased by the momentum behind Flatpak. “It's exciting to see the growing interest in what we are doing, as developers realise the possibilities of the technology,” he said.
-
- More information about Flatpak can be found on [flatpak.org](http://flatpak.org/).
-
-
-
diff --git a/source/404.html.haml b/source/404.html.haml
index 7b765177..967260ac 100644
--- a/source/404.html.haml
+++ b/source/404.html.haml
@@ -1,14 +1,13 @@
---
-title: Flatpak -- page not found
+title: Flatpak—page not found
description: 404 Page not Found
---
%section#notfound
.container
.row
- .col-lg-10.col-lg-offset-1
- %h1.section-heading.text-center Oops
+ .col-lg-5.col-lg-offset-4
%p
= partial "404.svg"
%p.centered
- The page you're looking for is no longer there.
+ Sorry, that page can't be found.
diff --git a/source/CNAME b/source/CNAME
deleted file mode 100644
index fa2d5223..00000000
--- a/source/CNAME
+++ /dev/null
@@ -1 +0,0 @@
-flatpak.org
diff --git a/source/_app-grid.svg b/source/_app-grid.svg
deleted file mode 100644
index 43ada80b..00000000
--- a/source/_app-grid.svg
+++ /dev/null
@@ -1,1785 +0,0 @@
-
-
diff --git a/source/_distro-grid.svg b/source/_distro-grid.svg
deleted file mode 100644
index 1db449f4..00000000
--- a/source/_distro-grid.svg
+++ /dev/null
@@ -1,432 +0,0 @@
-
-
diff --git a/source/_footer.haml b/source/_footer.haml
index 766303d5..fb0f091a 100644
--- a/source/_footer.haml
+++ b/source/_footer.haml
@@ -2,8 +2,8 @@
.container
.row
.col-lg-3.col-lg-offset-1.col-sm-3.hidden-xs
- %a.navbar-brand.page-scroll{:href => "#page-top"}
- =image_tag '/img/logo.svg', :title => 'Flatpak', :class => 'full'
+ %a.navbar-brand.page-scroll{:href => "#page-top"}
+ =partial "logo.svg"
%ul.col-lg-7.col-lg-offset-0.col-sm-8.col-sm-offset-0.col-xs-7.col-xs-offset-2
%li.toplevel
= link_to "Home", "/index.html"
@@ -29,3 +29,10 @@
:css
#twitterbird path { transition: fill 400ms ease-in-out; }
#twitterbird path:hover { fill: #fff !important; }
+ .col-lg-1.col-sm-1.col-xs-1
+
+ =partial "mastodon.svg"
+
+ :css
+ #mastodonlogo path { transition: fill 400ms ease-in-out; }
+ #mastodonlogo path:hover { fill: #fff !important; }
diff --git a/source/_logo.svg b/source/_logo.svg
new file mode 100644
index 00000000..8c113579
--- /dev/null
+++ b/source/_logo.svg
@@ -0,0 +1 @@
+
diff --git a/source/_mastodon.svg b/source/_mastodon.svg
new file mode 100644
index 00000000..dec86e3e
--- /dev/null
+++ b/source/_mastodon.svg
@@ -0,0 +1,40 @@
+
+
diff --git a/source/_twitter.svg b/source/_twitter.svg
index 8cf459dd..10c6f887 100644
--- a/source/_twitter.svg
+++ b/source/_twitter.svg
@@ -22,4 +22,4 @@
id="twitterbird">
\ No newline at end of file
+ d="m 2000,1432.96 c -73.58,-32.64 -152.67,-54.69 -235.66,-64.61 84.7,50.78 149.77,131.19 180.41,227.01 -79.29,-47.03 -167.1,-81.17 -260.57,-99.57 -74.84,79.75 -181.48,129.57 -299.5,129.57 -226.6,0 -410.328,-183.71 -410.328,-410.31 0,-32.16 3.628,-63.48 10.625,-93.51 -341.016,17.11 -643.368,180.47 -845.739,428.72 -35.324,-60.6 -55.5583,-131.09 -55.5583,-206.29 0,-142.36 72.4373,-267.95 182.5433,-341.53 -67.262,2.13 -130.535,20.59 -185.8519,51.32 -0.0391,-1.71 -0.0391,-3.42 -0.0391,-5.16 0,-198.803 141.441,-364.635 329.145,-402.342 -34.426,-9.375 -70.676,-14.395 -108.098,-14.395 -26.441,0 -52.145,2.578 -77.203,7.364 C 276.391,476.219 427.926,357.578 607.48,354.281 467.051,244.219 290.129,178.621 97.8828,178.621 64.7617,178.621 32.0977,180.57 0,184.359 181.586,67.9414 397.27,0 628.988,0 1383.72,0 1796.45,625.238 1796.45,1167.47 c 0,17.79 -0.41,35.48 -1.2,53.08 80.18,57.86 149.74,130.12 204.75,212.41" />
diff --git a/source/about.html.haml b/source/about.html.haml
index c1125e13..a8cac871 100644
--- a/source/about.html.haml
+++ b/source/about.html.haml
@@ -1,44 +1,160 @@
---
-title: Flatpak - the future of application distribution
+title: Flatpak—the future of application distribution
description: About Flatpak
---
%section#about
.container
.row
- .col-lg-10.col-lg-offset-1
- %h1.section-heading.text-center About
+ .col-lg-8.col-lg-offset-2
+ %h1.section-heading.text-center About Us
%hr.primary
%p
- Flatpak might be a new technology, but it's not a new idea. It grew out of the experience of long-standing Linux desktop engineers, and has been in the planning for years.
+ Flatpak is developed by an independent community, made up of contributors, volunteers and supporting organizations. It is a true upstream open source project, dedicated to providing technology and services that can be used by all, with no vendor lock-in. We have strong links to other Free Software projects, including the Freedesktop project.
%p
- Flatpak is developed by an independent community, made up of contributors, volunteers and supporting organizations. Its lead developer is Alex Larsson, Principal Engineer at Red Hat. Alex has been working on critical open source projects for almost 20 years and is an expert in containerization and Linux subsystems.
- %p
- All our code is freely available, with no contributor agreement required. We have strong links with other Free Software projects, including the Freedesktop project. If you are a member of a Free Software project, we'd love to have you involved.
- .row.largegap
- .col-lg-10.col-lg-offset-1
- %h3 Get involved
- %p
- Flatpak's goals are ambitious and there are many opportunities to help - new contributors and participating organizations are extremely welcome, and we encourage you to get in touch.
- .col-lg-12.text-center
+ All our code is freely available, with no contributor agreement required. Volunteers and contributing organizations are welcome, as equal partners.
+ .row
+ .col-lg-8.col-lg-offset-2
+ %h1.section-heading.text-center Contact
+ %hr.primary
.row
.col-lg-2.col-xs-4.col-lg-offset-4
.right.toneddown Mailing list
.col-lg-4.col-xs-8
- =link_to "flatpak@lists.freedesktop.org", "http://lists.freedesktop.org/mailman/listinfo/flatpak"
+ =link_to "flatpak at lists.freedesktop.org", "https://lists.freedesktop.org/mailman/listinfo/flatpak"
+ .row
+ .col-lg-4.col-xs-2.col-lg-offset-2
+ .right.toneddown Private mailing list for security issues
+ .col-lg-4.col-xs-8
+ =link_to "flatpak-security at lists.freedesktop.org", "https://lists.freedesktop.org/mailman/listinfo/flatpak-security"
.row
.col-lg-2.col-xs-4.col-lg-offset-4
- .right.toneddown IRC
+ .right.toneddown Matrix
.col-lg-4.col-xs-8
- =link_to "#flatpak on Freenode", "irc://freenode.net:6697/flatpak"
+ =link_to "#flatpak on Matrix.org", "https://matrix.to/#/#flatpak:matrix.org"
.row
.col-lg-2.col-xs-4.col-lg-offset-4
- .right.toneddown Github project
+ .right.toneddown GitHub
.col-lg-4.col-xs-8
- =link_to "github.com/flatpak/flatpak", "https://github.com/flatpak/flatpak"
+ =link_to "github.com/flatpak", "https://github.com/flatpak"
.row.largegap
- .col-lg-10.col-lg-offset-1
+ .col-lg-8.col-lg-offset-2
%p
Issues with this website can be reported through its
= succeed "." do
- =link_to "Github project", "https://github.com/flatpak/flatpak.github.io/issues"#
+ =link_to "GitHub project", "https://github.com/flatpak/flatpak.github.io/issues"#
+ .row.largegap
+ .col-lg-8.col-lg-offset-2
+ %h1.section-heading.text-center Flatpak History
+ %hr.primary
+ .timeline.mediumgap
+ .date August 2007
+ .description
+ Alexander Larsson releases Glick, his first app bundling framework
+ .date November 2011
+ .description
+ Glick 2 is released, a modernized version of the first Glick framework
+ .date July 2012
+ .decription
+ “GNOME OS” session held at GUADEC, includes initial planning for a new app bundling format
+ .date September 2012
+ .description
+ Alexander Larsson releases experimental “bundler” framework
+ .date January 2013
+ .description
+ “Linux Apps” proposal discussed at the GNOME Developer Experience hackfest, Brussels
+ .date December 2014
+ .description
+ Work begins on xdg-app, which later becomes Flatpak
+ .date March 2015
+ .descripton
+ xdg-app 0.1 released, the very first version of Flatpak
+ .date December 2015
+ .description
+ GNOME's “Software” gains the ability to install xdg-app applications
+ .date May 2016
+ .description
+ xdg-app renamed to Flatpak, 0.6.0 released;
+ = succeed " included endorsements by Red Hat, Endless Computers and Collabora" do
+ =link_to "accompanying press release", "https://flatpak.org/press/2016-06-21-flatpak-released.html"
+ .date June 2016
+ .description
+ Work on desktop portals security framework begins
+ .date June 2016
+ .description
+ LibreOffice is the first major application to adopt Flatpak for publishing on Linux
+ .date July 2016
+ .description
+ GTK+ 3.21.4 released with initial support for the portals framework
+ .date August 2016
+ .description
+ Endless OS 3.0 released, the first publicly available OS to use Flatpak by default. Adoption of Flatpak by Apertis IVI also becomes public knowledge.
+ .date November 2016
+ .description
+ ClearLinux announces their adoption of Flatpak
+ .date December 2016
+ .description
+ Flatpak 0.8.0 released, the start of the first stable series with long-term support
+ .date May 2017
+ .description
+ Initial soft launch of Flathub hosting service
+ .date May 2017
+ .description
+ KDE Plasma 5.10 released with initial support for portals
+ .date October 2017
+ .description
+ Flatpak 0.10.0 released, marking the start of the second supported stable release series
+ .date October 2017
+ .description
+ KDE Plasma 5.11 released, “Discover” gains the ability to install Flatpak apps
+ .date October 2017
+ .description
+ GIMP adopts Flatpak to publish on Linux
+ .date November 2017
+ .description
+ Linux Mint 18.3 released, includes out of the box Flatpak integration
+ .date August 2018
+ .description
+ Flatpak 1.0 released, the first release in a new stable series, with major new features; Flathub beta period ends; Freedesktop runtime 18.08 released with new support period policy
+ .date September 2018
+ .description
+ KDE introduces the KDE Testing Applications Flatpak repository;
+ =link_to "commit", "https://invent.kde.org/packaging/flatpak-kde-applications/-/commit/2d759a0d601942c3cf3a1d6a562942da543f7f83"
+ .date December 2019
+ .description
+ elementary OS 5.1 Hera released, includes out of the box Flatpak integration
+ .date April 2020
+ .description
+ Mozilla adopts Flatpak to publish Firefox on Linux
+ .date April 2020
+ .description
+ System76 releases Pop!_OS 20.04, includes out of the box Flatpak integration
+ .date October 2021
+ .description
+ 1Password adopts Flatpak to publish on Linux
+ .date Febuary 2022
+ .description
+ Valve releases the Steam Deck; a handheld video game console with out of the box Flatpak and Flathub integration
+ .date Febuary 2022
+ .description
+ OBS Studio adopts Flatpak to publish on Linux
+ .date May 2022
+ .description
+ Red Hat Enterprise Linux Workstation 9 released, includes out of the box Flatpak integration
+ .date October 2022
+ .description
+ Flathub introduces verified status;
+ =link_to "commit", "https://github.com/flathub/website/commit/5aae6b759b15ae26c155a0c8c18f13ca0da29ee3"
+ .date April 2023
+ .description
+ Purism introduces Flatpak and the PureOS Flatpak repository;
+ =link_to "announcement", "https://puri.sm/posts/introducing-flatpaks-on-pureos/"
+ .date April 2023
+ .description
+ Valve adopts portals for the popular Steam application
+ .date May 2023
+ .description
+ Flathub offers more than 2000 apps and celebrates 1B total downloads
+ .date October 2023
+ .description
+ Discord adopts Flatpak to publish on Linux
diff --git a/source/blog-posts.html.haml.markdown b/source/blog-posts.html.haml.markdown
new file mode 100644
index 00000000..3d8b5fcd
--- /dev/null
+++ b/source/blog-posts.html.haml.markdown
@@ -0,0 +1,216 @@
+---
+title: Blog Posts
+description: Blog posts about Flatpak
+---
+
+:markdown
+
+ # Blog Posts
+
+
+
+ If you know of a blog post that isn't listed, please [file an issue](https://github.com/flatpak/flatpak.github.io/issues/new) so we can add it!
+
+ ## 2024
+
+ [**Cassidy James Blaede: 2 Billion Downloads & Other Milestones from 2024 So Far**](https://docs.flathub.org/blog/2-billion-downloads-2024/)
+ August 2024
+
+ ## 2022
+
+ [**Hubert Figuière: RTKit, portals, and Pipewire**](https://www.figuiere.net/hub/wlog/rtkit-portal-pipewire/)
+ August 2022
+
+ [**Will Thompson: How many Flathub apps reuse other package formats?**](https://blogs.gnome.org/wjjt/2022/06/14/how-many-flathub-apps-reuse-other-package-formats/)
+ June 2022
+
+ [**Jakub Steiner: Flatpak Brand Refresh**](https://blog.jimmac.eu/2022/flatpak-refresh/)
+ June 2022
+
+ [**Martín Abente Lahaye: Flatseal 1.8.0**](https://blogs.gnome.org/tchx84/2022/05/31/flatseal-1-8-0/)
+ May 2022
+
+ [**Will Thompson: Evince, Flatpak, and GTK print previews**](https://blogs.gnome.org/wjjt/2022/05/30/evince-flatpak-and-gtk-print-previews/)
+ May 2022
+
+ [**TheEvilSkeleton: Response to "Flatpak Is Not the Future"**](https://theevilskeleton.gitlab.io/2022/05/16/response-to-flatpak-is-not-the-future.html)
+ May 2022
+
+ [**Jan Grulich: How to use Libportal/libportal-qt**](https://jgrulich.cz/2022/02/10/how-to-use-libportal-libportal-qt/)
+ February 2022
+
+ ## 2021
+
+ [**Phaedrus Leeds: A Quick PSA on Writing Portal-friendly Application Code**](https://blogs.gnome.org/mwleeds/2021/12/03/a-quick-psa-on-writing-portal-friendly-application-code/)
+ December 2021
+
+ [**Will Thompson: On Flatpak disk usage and deduplication**](https://blogs.gnome.org/wjjt/2021/11/24/on-flatpak-disk-usage-and-deduplication/)
+ November 2021
+
+ [**Martín Abente Lahaye: Flatseal 1.7.5**](https://blogs.gnome.org/tchx84/2021/11/20/flatseal-1-7-5/)
+ November 2021
+
+ [**Peter Hutterer: Flatpak portals - how do they work?**](https://who-t.blogspot.com/2021/08/flatpak-portals-how-do-they-work.html)
+ September 2021
+
+ [**Lionir Deadman: Flathub, runtimes and stats**](https://thelion.website/flathub-runtimes-and-stats/)
+ June 2021
+
+ [**Martín Abente Lahaye: Flatseal 1.7.0**](https://blogs.gnome.org/tchx84/2021/04/23/flatseal-1-7-0/)
+ April 2021
+
+ [**TheEvilSkeleton: Response to flatkill.org**](https://theevilskeleton.gitlab.io/2021/02/11/response-to-flatkill-org.html)
+ February 2021
+
+ [**Phaedrus Leeds: Cleaning Up Unused Flatpak Runtimes**](https://blogs.gnome.org/mwleeds/2021/01/11/cleaning-up-unused-flatpak-runtimes/)
+ January 2021
+
+ ## 2020
+
+ [**Alexander Larsson: Scaling Flathub 100x**](https://blogs.gnome.org/alexl/2020/11/20/scaling-flathub/)
+ November 2020
+
+ [**Alexander Larsson: Compatibility in a sandboxed world**](https://blogs.gnome.org/alexl/2020/08/11/compatibility-in-a-sandboxed-world/)
+ August 2020
+
+ [**Martín Abente Lahaye: Flatseal 1.6.0**](https://blogs.gnome.org/tchx84/2020/06/26/flatseal-1-6-0-and-beyond/)
+ June 2020
+
+ [**Hubert Figuière: Getting a stack trace with debug symbols out of a flatpak**](https://www.figuiere.net/technotes/notes/tn001/)
+ June 2020
+
+ [**Alexander Larsson: Putting container updates on a diet**](https://blogs.gnome.org/alexl/2020/05/13/putting-container-updates-on-a-diet/)
+ May 2020
+
+ ## 2019
+
+ [**Matthias Clasen: More on Flatpak Updates**](https://blogs.gnome.org/mclasen/2019/12/19/9100/)
+ December 2019
+
+ [**TingPing: Hardening Flatpak Permissions Over Time**](https://blog.tingping.se/2019/10/06/hardening-flatpak-permissions.html)
+ October 2019
+
+ [**Matthias Clasen: Some Flatpak Updates**](https://blogs.gnome.org/mclasen/2019/10/03/some-flatpak-updates/)
+ October 2019
+
+ [**Robert McQueen: Flathub, brought to you by...**](https://ramcq.net/2019/08/12/flathub-brought-to-you-by/)
+ August 2019
+
+ [**Matthias Clasen: Settings, in a Sandbox World**](https://blogs.gnome.org/mclasen/2019/07/12/settings-in-a-sandbox-world/)
+ July 2019
+
+ [**Christian Hergert: Flatpaking Terminals**](https://blogs.gnome.org/chergert/2019/04/25/flatpaking-terminals/)
+ April 2019
+
+ [**Alexander Larsson: Introducing flat-manager**](https://blogs.gnome.org/alexl/2019/03/19/introducing-flat-manager/)
+ March 2019
+
+ [**Alexander Larsson: Changes in Flathub land**](https://blogs.gnome.org/alexl/2019/02/19/changes-in-flathub-land/)
+ February 2019
+
+ [**Matthias Clasen: What's New in Flatpak 1.2**](https://blogs.gnome.org/mclasen/2019/01/28/whats-new-in-flatpak-1-2/)
+ January 2019
+
+ ## 2018
+
+ [**Matthias Clasen: Flatpak Commandline Design**](https://blogs.gnome.org/mclasen/2018/12/19/flatpak-commandline-design/)
+ December 2018
+
+ [**Matthias Clasen: An Update on Flatpak Updates**](https://blogs.gnome.org/mclasen/2018/11/26/an-update-on-flatpak-updates/)
+ November 2018
+
+ [**Robert McQueen: Flatpak, sandboxes and security**](https://ramcq.net/2018/10/15/flatpak-sandbox-security/)
+ October 2018
+
+ [**Alexander Larsson: Moving away from the 1.6 freedesktop runtime**](https://blogs.gnome.org/alexl/2018/10/11/moving-away-from-the-1-6-freedesktop-runtime/)
+ October 2018
+
+ [**Matthias Clasen: Flatpak, After 1.0**](https://blogs.gnome.org/mclasen/2018/10/08/flatpak-after-1-0/)
+ October 2018
+
+ [**Alexander Larsson: Flatpak on windows**](https://blogs.gnome.org/alexl/2018/09/17/flatpak-on-windows/)
+ September 2018
+
+ [**Matthias Clasen: On Flatpak Dependencies**](https://blogs.gnome.org/mclasen/2018/09/07/on-flatpak-dependencies/)
+ September 2018
+
+ [**Matthias Clasen: About Flatpak Installations**](https://blogs.gnome.org/mclasen/2018/08/26/about-flatpak-installations/)
+ August 2018
+
+ [**TingPing: Using host Nvidia driver with Flatpak**](https://blog.tingping.se/2018/08/26/flatpak-host-extensions.html)
+ August 2018
+
+ [**Alexander Larsson: Kick-starting the revolution 1.0**](https://blogs.gnome.org/alexl/2018/08/21/kick-starting-the-revolution-1-0/)
+ August 2018
+
+ [**TingPing: Easier Flatpak manifest editing with VSCode**](https://blog.tingping.se/2018/08/19/flatpak-schema.html)
+ August 2018
+
+ [**Alexander Larsson: The birth of a new runtime**](https://blogs.gnome.org/alexl/2018/08/10/the-birth-of-a-new-runtime/)
+ August 2018
+
+ [**Matthias Clasen: Flatpak Portal Experiments**](https://blogs.gnome.org/mclasen/2018/08/03/flatpak-portal-experiments/)
+ August 2018
+
+ [**Matthias Clasen: Flatpak - A Look Behind the Portal**](https://blogs.gnome.org/mclasen/2018/07/19/flatpak-a-look-behind-the-portal/)
+ July 2018
+
+ [**Matthias Clasen: The Flatpak BoF at GUADEC**](https://blogs.gnome.org/mclasen/2018/07/14/the-flatpak-bof-at-guadec/)
+ July 2018
+
+ [**Matthias Clasen: Flatpak, Making Contribution Easy**](https://blogs.gnome.org/mclasen/2018/07/07/flatpak-making-contribution-easy/)
+ July 2018
+
+ [**Matthias Clasen: Flatpak in Detail, Part 3**](https://blogs.gnome.org/mclasen/2018/07/02/flatpak-in-detail-part-3/)
+ July 2018
+
+ [**Alexander Larsson: Flatpak - a history**](https://blogs.gnome.org/alexl/2018/06/20/flatpak-a-history/)
+ June 2018
+
+ [**Matthias Clasen: Flatpak in Detail, Part 2**](https://blogs.gnome.org/mclasen/2018/06/19/flatpak-in-detail-part-2/)
+ June 2018
+
+ [**Matthias Clasen: Flatpak in Detail**](https://blogs.gnome.org/mclasen/2018/06/13/flatpak-in-detail/)
+ June 2018
+
+ [**Alexander Larsson: Flatpak inception**](https://blogs.gnome.org/alexl/2018/04/27/flatpak-inception/)
+ April 2018
+
+ [**TingPing: Flatpaking application plugins**](https://blog.tingping.se/2018/03/18/flatpaking-plugins.html)
+ March 2018
+
+ [**PointestStick: Flatpak support in Discover**](https://pointieststick.com/2018/01/13/flatpak-support-in-discover/)
+ January 2018
+
+ ## 2017
+
+ [**TingPing: Status of emulators Flatpak'd**](https://blog.tingping.se/2017/10/31/flatpaked-emulators.html)
+ October 2017
+
+ [**Alexander Larsson: On application sizes and bloat in flatpak**](https://blogs.gnome.org/alexl/2017/10/02/on-application-sizes-and-bloat-in-flatpak/)
+ October 2017
+
+ [**Simon McVittie: DebConf 17: Flatpak and Debian**](http://smcv.pseudorandom.co.uk/2017/flatpak_and_debian/)
+ August 2017
+
+ [**Robert McQueen: Welcome, Flathub!**](https://ramcq.net/2017/07/29/welcome-flathub/)
+ July 2017
+
+ [**TingPing: Flatpak now supports themes**](https://blog.tingping.se/2017/05/11/flatpak-theming.html)
+ May 2017
+
+ [**Simon McVittie: GTK hackfest 2017: D-Bus communication with containers**](http://smcv.pseudorandom.co.uk/2017/dbus_and_containers/)
+ March 2017
+
+ [**Matthias Clasen: Debugging a Flatpak Application**](https://blogs.gnome.org/mclasen/2017/01/20/debugging-a-flatpak-application/)
+ January 2017
+
+ ## 2016
+
+ [**Simon McVittie: Flatpak in Debian**](http://smcv.pseudorandom.co.uk/2016/flatpak/)
+ June 2016
+
+ [**Simon McVittie: GNOME Developer Experience hackfest: xdg-app + Debian**](https://smcv.pseudorandom.co.uk/2016/xdg-app/)
+ January 2016
+
+
diff --git a/source/distro-template.html.haml b/source/distro-template.html.haml
new file mode 100644
index 00000000..a8425d2a
--- /dev/null
+++ b/source/distro-template.html.haml
@@ -0,0 +1,24 @@
+---
+title: Flatpak—the future of application distribution
+description: #{locals[:name]} Quick Setup
+---
+
+%section#setup
+ .container
+ .row
+ .col-lg-10.col-lg-offset-1
+ %h1.centered
+ = locals[:name]
+ Quick Setup
+ %p.centered
+ Follow these simple steps to start using Flatpak
+
+ .row.largegap
+ .col-lg-12
+ %ol.distrotut
+ - if locals[:introduction]
+ = locals[:introduction]
+ - Array(locals[:steps]).each_with_index do |step, i|
+ %li
+ %h2= step[:name]
+ %p= step[:text]
\ No newline at end of file
diff --git a/source/faq.html.haml.markdown b/source/faq.html.haml.markdown
index 819f7600..ab7da3f3 100644
--- a/source/faq.html.haml.markdown
+++ b/source/faq.html.haml.markdown
@@ -42,11 +42,11 @@ description: FAQ about the Flatpak project.
Yes. We are explicitly using many features of the linux kernel (bind mounts, namespaces, seccomp, etc) to create the sandbox that
Flatpak apps are running in. It may be possible to use equivalent technologies on other kernels, but that would be a non-trivial
- amount of work, and we don't consider this one of our priorities.
+ amount of work, and we don’t consider this one of our priorities.
### Is Flatpak tied to systemd?
- No. Versions of flatpak before 0.6.10 relied on systemd for cgroups setup, but this is no longer required.
+ No. Versions of Flatpak before 0.6.10 relied on systemd for cgroups setup, but this is no longer required.
### Is Flatpak the same as xdg-app?
@@ -56,28 +56,28 @@ description: FAQ about the Flatpak project.
### Is Flatpak a container technology?
- It can be, but it doesn't have to be. Since a desktop application would require quite extensive changes in order to
+ It can be, but it doesn’t have to be. Since a desktop application would require quite extensive changes in order to
be usable when run inside a container you will likely see Flatpak mostly deployed as a convenient library bundling technology
early on, with the sandboxing or containerization being phased in over time for most applications. In general though we
try to avoid using the term container when speaking about Flatpak as it tends to cause comparisons with Docker and rkt,
comparisons which quickly stop making technical sense due to the very different problem spaces these technologies
try to address. And thus we prefer using the term sandboxing.
- ### How does Flatpak relate to freedesktop.org technologies such as desktop files and appstream metadata?
+ ### How does Flatpak relate to freedesktop.org technologies such as desktop files and AppStream metadata?
- These standards are incorporated as mandatory parts in the flatpak definition. By relying on these standards
+ These standards are incorporated as mandatory parts in the Flatpak definition. By relying on these standards
we are building on years of investment and support under Linux.
### Can Flatpak be used on servers too?
- Flatpak is designed to run inside a desktop session and relies on certain session services, such as a dbus session bus
- and, optionally, a systemd --user instance. This makes Flatpak not a good match for a server.
+ Flatpak is designed to run inside a desktop session and relies on certain session services, such as a D-Bus session bus
+ and, optionally, a systemd `--user` instance. This makes Flatpak not a good match for a server.
However, the build features of Flatpak run fine outside a session, so you can build things on a server.
### Is Flatpak compatible with other desktop isolation frameworks?
- In general unprivileged container systems can't stack, because anything running inside the sandbox does not have the necessary privileges to set up a sandbox, nor does it have the ability to raise its privileges in any way. For instance, firejail can never work inside flatpak, because it is setuid. That being said, using multiple sandboxing frameworks at once does not really make anything more secure, so there is little point in trying to nest things like that.
+ In general unprivileged container systems can’t stack, because anything running inside the sandbox does not have the necessary privileges to set up a sandbox, nor does it have the ability to raise its privileges in any way. For instance, Firejail can never work inside Flatpak, because it is setuid. That being said, using multiple sandboxing frameworks at once does not really make anything more secure, so there is little point in trying to nest things like that.
It is certainly possible for Flatpak and Flatpak applications to coexist with applications that are packaged in other ways, on the same host system.
@@ -85,13 +85,13 @@ description: FAQ about the Flatpak project.
Yes!
- Version 3.22.4 and newer of [GNOME Builder](https://wiki.gnome.org/Apps/Builder) includes support for `flatpak-builder` manifests. This ensures your project is built using your selected flatpak runtime and any external dependencies. Support for running your application inside flatpak is also supported. By developing your application within the exact same environment as your users you can squash those "Works for me" bugs before they reach your users!
+ Version 3.22.4 and newer of [Builder](https://apps.gnome.org/Builder/) includes support for `flatpak-builder` manifests. This ensures your project is built using your selected Flatpak runtime and any external dependencies. Support for running your application inside Flatpak is also supported. By developing your application within the exact same environment as your users you can squash those “Works for me” bugs before they reach your users!
- ### Can I host my flatpak app on github?
+ ### Can I host my Flatpak app on GitHub?
- Flatpak repositories can't (currently) be put on github in a convenient way.
- As an alternative, you can create a single-file bundle, and put that up on github
- as a 'release'. Note that bundles have some drawbacks, compared to a repository.
+ Flatpak repositories can’t (currently) be put on GitHub in a convenient way.
+ As an alternative, you can create a single-file bundle, and put that up on GitHub
+ as a “release.” Note that bundles have some drawbacks, compared to a repository.
Another option you have is to get your app on [Flathub](https://flathub.org/)
which will allow your users to get updates.
diff --git a/source/favicon.ico b/source/favicon.ico
index 3ac6a102..2136ca91 100644
Binary files a/source/favicon.ico and b/source/favicon.ico differ
diff --git a/source/fonts/Inter.var.woff2 b/source/fonts/Inter.var.woff2
new file mode 100644
index 00000000..365eedc5
Binary files /dev/null and b/source/fonts/Inter.var.woff2 differ
diff --git a/source/fonts/Overpass-Bold-Italic.ttf b/source/fonts/Overpass-Bold-Italic.ttf
deleted file mode 100644
index 6c55085a..00000000
Binary files a/source/fonts/Overpass-Bold-Italic.ttf and /dev/null differ
diff --git a/source/fonts/Overpass-Bold.ttf b/source/fonts/Overpass-Bold.ttf
deleted file mode 100644
index 0518472f..00000000
Binary files a/source/fonts/Overpass-Bold.ttf and /dev/null differ
diff --git a/source/fonts/Overpass-ExtraLight Italic.ttf b/source/fonts/Overpass-ExtraLight Italic.ttf
deleted file mode 100644
index 6336b8c5..00000000
Binary files a/source/fonts/Overpass-ExtraLight Italic.ttf and /dev/null differ
diff --git a/source/fonts/Overpass-ExtraLight.ttf b/source/fonts/Overpass-ExtraLight.ttf
deleted file mode 100644
index 733b4100..00000000
Binary files a/source/fonts/Overpass-ExtraLight.ttf and /dev/null differ
diff --git a/source/fonts/Overpass-Light-Italic.ttf b/source/fonts/Overpass-Light-Italic.ttf
deleted file mode 100644
index 90faedbf..00000000
Binary files a/source/fonts/Overpass-Light-Italic.ttf and /dev/null differ
diff --git a/source/fonts/Overpass-Light.ttf b/source/fonts/Overpass-Light.ttf
deleted file mode 100644
index 426c35e5..00000000
Binary files a/source/fonts/Overpass-Light.ttf and /dev/null differ
diff --git a/source/fonts/Overpass-Regular-Italic.ttf b/source/fonts/Overpass-Regular-Italic.ttf
deleted file mode 100644
index 7bc8ad0f..00000000
Binary files a/source/fonts/Overpass-Regular-Italic.ttf and /dev/null differ
diff --git a/source/fonts/Overpass-Regular.ttf b/source/fonts/Overpass-Regular.ttf
deleted file mode 100644
index 49499e47..00000000
Binary files a/source/fonts/Overpass-Regular.ttf and /dev/null differ
diff --git a/source/fonts/SourceCodePro-ExtraLight.otf b/source/fonts/SourceCodePro-ExtraLight.otf
deleted file mode 100644
index 62aedb62..00000000
Binary files a/source/fonts/SourceCodePro-ExtraLight.otf and /dev/null differ
diff --git a/source/fonts/SourceCodePro-Light.otf b/source/fonts/SourceCodePro-Light.otf
deleted file mode 100644
index d196cabc..00000000
Binary files a/source/fonts/SourceCodePro-Light.otf and /dev/null differ
diff --git a/source/fonts/SourceCodePro-Regular.otf b/source/fonts/SourceCodePro-Regular.otf
deleted file mode 100644
index f88f9c68..00000000
Binary files a/source/fonts/SourceCodePro-Regular.otf and /dev/null differ
diff --git a/source/fonts/SourceCodePro-Semibold.otf b/source/fonts/SourceCodePro-Semibold.otf
deleted file mode 100644
index 764ca4ed..00000000
Binary files a/source/fonts/SourceCodePro-Semibold.otf and /dev/null differ
diff --git a/source/fonts/SourceSansPro-ExtraLight.otf b/source/fonts/SourceSansPro-ExtraLight.otf
deleted file mode 100644
index 43e0c69f..00000000
Binary files a/source/fonts/SourceSansPro-ExtraLight.otf and /dev/null differ
diff --git a/source/fonts/SourceSansPro-Light.otf b/source/fonts/SourceSansPro-Light.otf
deleted file mode 100644
index 9d8fb28c..00000000
Binary files a/source/fonts/SourceSansPro-Light.otf and /dev/null differ
diff --git a/source/fonts/SourceSansPro-Regular.otf b/source/fonts/SourceSansPro-Regular.otf
deleted file mode 100644
index 7b6fa55f..00000000
Binary files a/source/fonts/SourceSansPro-Regular.otf and /dev/null differ
diff --git a/source/fonts/SourceSansPro-Semibold.otf b/source/fonts/SourceSansPro-Semibold.otf
deleted file mode 100644
index 6b39aa45..00000000
Binary files a/source/fonts/SourceSansPro-Semibold.otf and /dev/null differ
diff --git a/source/getting.html.haml.markdown b/source/getting.html.haml.markdown
deleted file mode 100644
index 0f899e64..00000000
--- a/source/getting.html.haml.markdown
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Getting Flatpak
-description: How to download and install Flatpak on your system to get started.
----
-
-:markdown
- # Getting Flatpak
-
- Flatpak is available for the most common Linux distributions. After installing it, it is necessary to log out and in again for Flatpak apps to appear in your desktop.
-
- Once you've installed Flatpak, you can [get some apps](apps.html) or [create your own in 5 minutes](hello-world.html).
-
- ### Alpine
-
- A `flatpak` package is available in the testing repository.
-
-
- $ sudo apk add flatpak
-
-
- ### Arch
-
- A `flatpak` package is available in the official repositories. `flatpak-git` is also available in the AUR for the latest development snapshot.
-
-
- $ sudo pacman -S flatpak
-
-
- For development of Flatpak applications using `flatpak-builder` these dependencies are required:
-
-
-
- ### Debian
-
- A `flatpak` package is available in [Debian Stretch](https://wiki.debian.org/DebianStretch) and newer. To install, run the following as root:
-
-
- # apt install flatpak
-
-
- For Debian Jessie, a `flatpak` package is available in the official [backports repository](https://backports.debian.org/Instructions/).
-
- ### Endless OS
-
- Flatpak support is built into Endless OS 3.0.0 and newer. If you are using an older version, [upgrade to Endless OS 3](https://community.endlessos.com/t/upgrade-from-endless-os-2-x-to-endless-os-3/967).
-
- ### Fedora
-
- A `flatpak` package is available for Fedora 24 and newer and is installed by default on Fedora Workstation. If you do not use Fedora Workstation, you can install Flatpak by running:
-
-
- $ sudo dnf install flatpak
-
-
- ### Gentoo
-
- An unofficial overlay is available [here](https://github.com/fosero/flatpak-overlay).
-
- ### Linux Mint
-
- Flatpak support is built into Linux Mint 18.3 and newer.
-
- ### Mageia
-
- A `flatpak` package is available for Mageia 6 and newer. To install, run the following as root:
-
- If using `DNF`
-
-
- # dnf install flatpak
-
-
- If using `urpmi`
-
-
- # urpmi flatpak
-
-
- ### openSUSE
-
- Flatpak is available as a [1-click install](https://software.opensuse.org/package/flatpak) for Leap 42.1 and 42.2 and Tumbleweed. It can also be installed on Tumbleweed using Zypper:
-
-
- $ sudo zypper install flatpak
-
-
- ### Solus
-
- Flatpak package is available for Solus too. Install it using `eopkg`.
-
-
- $ sudo eopkg install flatpak
-
-
- ### Ubuntu
-
- For Ubuntu 16.04 and newer a PPA is available. To install, run:
-
-
-
- A `flatpak` package is available in [Ubuntu 16.10](https://wiki.ubuntu.com/YakketyYak) and newer via universe, however this is
- an older version, and it's recommended that you use the one from the PPA.
-
-
-
diff --git a/source/img/apple-touch-icon.png b/source/img/apple-touch-icon.png
new file mode 100644
index 00000000..4ce20102
Binary files /dev/null and b/source/img/apple-touch-icon.png differ
diff --git a/source/img/apple-touch-icon.svg b/source/img/apple-touch-icon.svg
new file mode 100644
index 00000000..b3415397
--- /dev/null
+++ b/source/img/apple-touch-icon.svg
@@ -0,0 +1,98 @@
+
+
diff --git a/source/img/bluetowhite.svg b/source/img/bluetowhite.svg
deleted file mode 100644
index 8e4d847f..00000000
--- a/source/img/bluetowhite.svg
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
diff --git a/source/img/container.webp b/source/img/container.webp
new file mode 100644
index 00000000..7bce53ed
Binary files /dev/null and b/source/img/container.webp differ
diff --git a/source/img/delivery_truck.original.png b/source/img/delivery_truck.original.png
new file mode 100644
index 00000000..bf792872
Binary files /dev/null and b/source/img/delivery_truck.original.png differ
diff --git a/source/img/delivery_truck.png b/source/img/delivery_truck.png
new file mode 100644
index 00000000..62c6c6d0
Binary files /dev/null and b/source/img/delivery_truck.png differ
diff --git a/source/img/delivery_truck2.original.png b/source/img/delivery_truck2.original.png
new file mode 100644
index 00000000..ff4a3701
Binary files /dev/null and b/source/img/delivery_truck2.original.png differ
diff --git a/source/img/delivery_truck2.png b/source/img/delivery_truck2.png
new file mode 100644
index 00000000..86770c34
Binary files /dev/null and b/source/img/delivery_truck2.png differ
diff --git a/source/img/distro/almalinux.svg b/source/img/distro/almalinux.svg
new file mode 100644
index 00000000..b2e050ae
--- /dev/null
+++ b/source/img/distro/almalinux.svg
@@ -0,0 +1,16 @@
+
diff --git a/source/img/distro/alpine.svg b/source/img/distro/alpine.svg
new file mode 100644
index 00000000..6b43c64e
--- /dev/null
+++ b/source/img/distro/alpine.svg
@@ -0,0 +1,276 @@
+
+
+
+
diff --git a/source/img/distro/altlinux-dark.svg b/source/img/distro/altlinux-dark.svg
new file mode 100644
index 00000000..affd52c5
--- /dev/null
+++ b/source/img/distro/altlinux-dark.svg
@@ -0,0 +1,17 @@
+
diff --git a/source/img/distro/altlinux.svg b/source/img/distro/altlinux.svg
new file mode 100644
index 00000000..de3d97ab
--- /dev/null
+++ b/source/img/distro/altlinux.svg
@@ -0,0 +1,16 @@
+
diff --git a/source/img/distro/arch.svg b/source/img/distro/arch.svg
new file mode 100644
index 00000000..c4d13f3e
--- /dev/null
+++ b/source/img/distro/arch.svg
@@ -0,0 +1,228 @@
+
+
+
+
diff --git a/source/img/distro/centos.svg b/source/img/distro/centos.svg
new file mode 100644
index 00000000..1a3f9f10
--- /dev/null
+++ b/source/img/distro/centos.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/source/img/distro/chrome-os.svg b/source/img/distro/chrome-os.svg
new file mode 100644
index 00000000..9aad7bba
--- /dev/null
+++ b/source/img/distro/chrome-os.svg
@@ -0,0 +1,838 @@
+
+
diff --git a/source/img/distro/crystallinux.svg b/source/img/distro/crystallinux.svg
new file mode 100644
index 00000000..6f4c9263
--- /dev/null
+++ b/source/img/distro/crystallinux.svg
@@ -0,0 +1,5 @@
+
+
diff --git a/source/img/distro/debian.svg b/source/img/distro/debian.svg
new file mode 100644
index 00000000..30329f47
--- /dev/null
+++ b/source/img/distro/debian.svg
@@ -0,0 +1,154 @@
+
+
+
+
diff --git a/source/img/distro/deepin.svg b/source/img/distro/deepin.svg
new file mode 100644
index 00000000..9738f0e1
--- /dev/null
+++ b/source/img/distro/deepin.svg
@@ -0,0 +1,123 @@
+
+
diff --git a/source/img/distro/elementary-os-dark.svg b/source/img/distro/elementary-os-dark.svg
new file mode 100644
index 00000000..f845c32d
--- /dev/null
+++ b/source/img/distro/elementary-os-dark.svg
@@ -0,0 +1,102 @@
+
+
diff --git a/source/img/distro/elementary-os.svg b/source/img/distro/elementary-os.svg
new file mode 100644
index 00000000..f86f1141
--- /dev/null
+++ b/source/img/distro/elementary-os.svg
@@ -0,0 +1,102 @@
+
+
diff --git a/source/img/distro/endeavouros-dark.svg b/source/img/distro/endeavouros-dark.svg
new file mode 100644
index 00000000..5e6482be
--- /dev/null
+++ b/source/img/distro/endeavouros-dark.svg
@@ -0,0 +1,96 @@
+
+
diff --git a/source/img/distro/endeavouros.svg b/source/img/distro/endeavouros.svg
new file mode 100644
index 00000000..24c7ea25
--- /dev/null
+++ b/source/img/distro/endeavouros.svg
@@ -0,0 +1,96 @@
+
+
diff --git a/source/img/distro/endless.svg b/source/img/distro/endless.svg
new file mode 100644
index 00000000..7ef91b0a
--- /dev/null
+++ b/source/img/distro/endless.svg
@@ -0,0 +1,82 @@
+
+
+
+
diff --git a/source/img/distro/fedora.svg b/source/img/distro/fedora.svg
new file mode 100644
index 00000000..d789e9eb
--- /dev/null
+++ b/source/img/distro/fedora.svg
@@ -0,0 +1,53 @@
+
+
diff --git a/source/img/distro/gentoo.svg b/source/img/distro/gentoo.svg
new file mode 100644
index 00000000..7c382cf1
--- /dev/null
+++ b/source/img/distro/gentoo.svg
@@ -0,0 +1,231 @@
+
+
+
+
diff --git a/source/img/distro/guix-dark.svg b/source/img/distro/guix-dark.svg
new file mode 100644
index 00000000..bf36ebcc
--- /dev/null
+++ b/source/img/distro/guix-dark.svg
@@ -0,0 +1,177 @@
+
+
+
+
diff --git a/source/img/distro/guix.svg b/source/img/distro/guix.svg
new file mode 100644
index 00000000..9b9e8f6f
--- /dev/null
+++ b/source/img/distro/guix.svg
@@ -0,0 +1,177 @@
+
+
+
+
diff --git a/source/img/distro/kdeneon.svg b/source/img/distro/kdeneon.svg
new file mode 100644
index 00000000..5068c338
--- /dev/null
+++ b/source/img/distro/kdeneon.svg
@@ -0,0 +1,176 @@
+
+
diff --git a/source/img/distro/kubuntu.svg b/source/img/distro/kubuntu.svg
new file mode 100644
index 00000000..6aa4feaf
--- /dev/null
+++ b/source/img/distro/kubuntu.svg
@@ -0,0 +1,101 @@
+
+
+
+
diff --git a/source/img/distro/mageia.svg b/source/img/distro/mageia.svg
new file mode 100644
index 00000000..060b1c4d
--- /dev/null
+++ b/source/img/distro/mageia.svg
@@ -0,0 +1,316 @@
+
+
+
+
diff --git a/source/img/distro/manjaro.svg b/source/img/distro/manjaro.svg
new file mode 100644
index 00000000..e7774b7e
--- /dev/null
+++ b/source/img/distro/manjaro.svg
@@ -0,0 +1,93 @@
+
+
diff --git a/source/img/distro/mint.svg b/source/img/distro/mint.svg
new file mode 100644
index 00000000..ed8950e5
--- /dev/null
+++ b/source/img/distro/mint.svg
@@ -0,0 +1,87 @@
+
+
+
+
diff --git a/source/img/distro/mxlinux.svg b/source/img/distro/mxlinux.svg
new file mode 100644
index 00000000..e15d9046
--- /dev/null
+++ b/source/img/distro/mxlinux.svg
@@ -0,0 +1,81 @@
+
+
diff --git a/source/img/distro/nixos.svg b/source/img/distro/nixos.svg
new file mode 100644
index 00000000..19e3a619
--- /dev/null
+++ b/source/img/distro/nixos.svg
@@ -0,0 +1,518 @@
+
+
diff --git a/source/img/distro/openmandriva.svg b/source/img/distro/openmandriva.svg
new file mode 100644
index 00000000..5992d10c
--- /dev/null
+++ b/source/img/distro/openmandriva.svg
@@ -0,0 +1,90 @@
+
+
+
+
diff --git a/source/img/distro/opensuse.svg b/source/img/distro/opensuse.svg
new file mode 100644
index 00000000..d93730a0
--- /dev/null
+++ b/source/img/distro/opensuse.svg
@@ -0,0 +1,131 @@
+
+
+
+
diff --git a/source/img/distro/pardus.svg b/source/img/distro/pardus.svg
new file mode 100644
index 00000000..5fece936
--- /dev/null
+++ b/source/img/distro/pardus.svg
@@ -0,0 +1,170 @@
+
+
+
+
diff --git a/source/img/distro/pisi-dark.svg b/source/img/distro/pisi-dark.svg
new file mode 100644
index 00000000..7555bc0d
--- /dev/null
+++ b/source/img/distro/pisi-dark.svg
@@ -0,0 +1,306 @@
+
+
+
+
diff --git a/source/img/distro/pisi.svg b/source/img/distro/pisi.svg
new file mode 100644
index 00000000..05dc0259
--- /dev/null
+++ b/source/img/distro/pisi.svg
@@ -0,0 +1,306 @@
+
+
+
+
diff --git a/source/img/distro/pop-os.svg b/source/img/distro/pop-os.svg
new file mode 100644
index 00000000..0d06a7dd
--- /dev/null
+++ b/source/img/distro/pop-os.svg
@@ -0,0 +1,98 @@
+
+
diff --git a/source/img/distro/pureos-dark.svg b/source/img/distro/pureos-dark.svg
new file mode 100644
index 00000000..9c3a67cf
--- /dev/null
+++ b/source/img/distro/pureos-dark.svg
@@ -0,0 +1,52 @@
+
+
diff --git a/source/img/distro/pureos.svg b/source/img/distro/pureos.svg
new file mode 100644
index 00000000..70cd1caf
--- /dev/null
+++ b/source/img/distro/pureos.svg
@@ -0,0 +1,52 @@
+
+
diff --git a/source/img/distro/raspberry-pi-os.svg b/source/img/distro/raspberry-pi-os.svg
new file mode 100644
index 00000000..ac958e5c
--- /dev/null
+++ b/source/img/distro/raspberry-pi-os.svg
@@ -0,0 +1,89 @@
+
+
+
+
diff --git a/source/img/distro/redhat.svg b/source/img/distro/redhat.svg
new file mode 100644
index 00000000..7e6715e6
--- /dev/null
+++ b/source/img/distro/redhat.svg
@@ -0,0 +1,97 @@
+
+
+
+
diff --git a/source/img/distro/rockylinux.svg b/source/img/distro/rockylinux.svg
new file mode 100644
index 00000000..58f22104
--- /dev/null
+++ b/source/img/distro/rockylinux.svg
@@ -0,0 +1,3 @@
+
diff --git a/source/img/distro/salix.svg b/source/img/distro/salix.svg
new file mode 100644
index 00000000..9de77679
--- /dev/null
+++ b/source/img/distro/salix.svg
@@ -0,0 +1,65 @@
+
+
+
+
diff --git a/source/img/distro/slackware.svg b/source/img/distro/slackware.svg
new file mode 100644
index 00000000..ccea5803
--- /dev/null
+++ b/source/img/distro/slackware.svg
@@ -0,0 +1,157 @@
+
+
+
\ No newline at end of file
diff --git a/source/img/distro/solus.svg b/source/img/distro/solus.svg
new file mode 100644
index 00000000..059974fe
--- /dev/null
+++ b/source/img/distro/solus.svg
@@ -0,0 +1,331 @@
+
+
+
+
diff --git a/source/img/distro/sulinos.svg b/source/img/distro/sulinos.svg
new file mode 100644
index 00000000..bcf430bd
--- /dev/null
+++ b/source/img/distro/sulinos.svg
@@ -0,0 +1,251 @@
+
+
+
+
diff --git a/source/img/distro/ubuntu.svg b/source/img/distro/ubuntu.svg
new file mode 100644
index 00000000..f5e18550
--- /dev/null
+++ b/source/img/distro/ubuntu.svg
@@ -0,0 +1,9 @@
+
diff --git a/source/img/distro/vanillaos.svg b/source/img/distro/vanillaos.svg
new file mode 100644
index 00000000..b56a6dca
--- /dev/null
+++ b/source/img/distro/vanillaos.svg
@@ -0,0 +1,321 @@
+
+
diff --git a/source/img/distro/void-dark.svg b/source/img/distro/void-dark.svg
new file mode 100644
index 00000000..e59fbc84
--- /dev/null
+++ b/source/img/distro/void-dark.svg
@@ -0,0 +1,137 @@
+
+
diff --git a/source/img/distro/void.svg b/source/img/distro/void.svg
new file mode 100644
index 00000000..734cdfec
--- /dev/null
+++ b/source/img/distro/void.svg
@@ -0,0 +1,87 @@
+
+
diff --git a/source/img/distro/zorin-os.svg b/source/img/distro/zorin-os.svg
new file mode 100644
index 00000000..4445744f
--- /dev/null
+++ b/source/img/distro/zorin-os.svg
@@ -0,0 +1,71 @@
+
+
diff --git a/source/img/download.original.svg b/source/img/download.original.svg
new file mode 100644
index 00000000..6f9de522
--- /dev/null
+++ b/source/img/download.original.svg
@@ -0,0 +1,57 @@
+
+
diff --git a/source/img/download.svg b/source/img/download.svg
index 6f9de522..7b03bc26 100644
--- a/source/img/download.svg
+++ b/source/img/download.svg
@@ -1,57 +1 @@
-
-
+
\ No newline at end of file
diff --git a/source/img/endless-apps.original.png b/source/img/endless-apps.original.png
new file mode 100644
index 00000000..6b87d055
Binary files /dev/null and b/source/img/endless-apps.original.png differ
diff --git a/source/img/endless-apps.png b/source/img/endless-apps.png
index cfa27604..48f957be 100644
Binary files a/source/img/endless-apps.png and b/source/img/endless-apps.png differ
diff --git a/source/img/favicon.png b/source/img/favicon.png
deleted file mode 100644
index 6ed880a2..00000000
Binary files a/source/img/favicon.png and /dev/null differ
diff --git a/source/img/favicon.svg b/source/img/favicon.svg
new file mode 100644
index 00000000..8e8c3679
--- /dev/null
+++ b/source/img/favicon.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/source/img/favicon.xcf.bz2 b/source/img/favicon.xcf.bz2
deleted file mode 100644
index 6e77603d..00000000
Binary files a/source/img/favicon.xcf.bz2 and /dev/null differ
diff --git a/source/img/favicon152.png b/source/img/favicon152.png
deleted file mode 100644
index 14f52c54..00000000
Binary files a/source/img/favicon152.png and /dev/null differ
diff --git a/source/img/favicon57.png b/source/img/favicon57.png
deleted file mode 100644
index 0fc73213..00000000
Binary files a/source/img/favicon57.png and /dev/null differ
diff --git a/source/img/flatpak-logos.zip b/source/img/flatpak-logos.zip
new file mode 100644
index 00000000..31a75b7f
Binary files /dev/null and b/source/img/flatpak-logos.zip differ
diff --git a/source/img/header.png b/source/img/header.png
deleted file mode 100644
index e862ea55..00000000
Binary files a/source/img/header.png and /dev/null differ
diff --git a/source/img/header.svgz b/source/img/header.svgz
deleted file mode 100644
index 88e95bc4..00000000
Binary files a/source/img/header.svgz and /dev/null differ
diff --git a/source/img/header_bottom.png b/source/img/header_bottom.png
deleted file mode 100644
index 87aa0d84..00000000
Binary files a/source/img/header_bottom.png and /dev/null differ
diff --git a/source/img/header_bottom.svg b/source/img/header_bottom.svg
deleted file mode 100644
index f89eaea1..00000000
--- a/source/img/header_bottom.svg
+++ /dev/null
@@ -1,387 +0,0 @@
-
-
-
-
diff --git a/source/img/logo.svg b/source/img/logo.svg
deleted file mode 100644
index bccb6964..00000000
--- a/source/img/logo.svg
+++ /dev/null
@@ -1,271 +0,0 @@
-
-
diff --git a/source/img/logo.svgz b/source/img/logo.svgz
new file mode 100644
index 00000000..55a22751
Binary files /dev/null and b/source/img/logo.svgz differ
diff --git a/source/img/logo2.svg b/source/img/logo2.svg
deleted file mode 100644
index 1d45dd5f..00000000
--- a/source/img/logo2.svg
+++ /dev/null
@@ -1,239 +0,0 @@
-
-
diff --git a/source/img/whitetoblue.svg b/source/img/whitetoblue.svg
deleted file mode 100644
index 299a7c52..00000000
--- a/source/img/whitetoblue.svg
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
diff --git a/source/index.html.haml b/source/index.html.haml
index 938dd79d..e80210b9 100644
--- a/source/index.html.haml
+++ b/source/index.html.haml
@@ -1,70 +1,99 @@
---
-title: Flatpak - the future of application distribution
+title: Flatpak—the future of application distribution
description: The days of chasing multiple Linux distributions are over. Standalone apps for Linux are here!
---
-%section.bg-primary-neutral.centered
+%section.imagebanner
.container
.row.largegap
- .col-lg-12
- %h1.section-heading the best way to get apps on Linux
- %p Choose from a growing collection of apps.
- .row
- .appgrid
- - data.apps.each do |i|
- - if i.icons["128"]
- .icon.featured{:style => "background-image: url(#{i.icons['128']})"}
- - elsif i.icons["64"]
- .icon{:style => "background-image: url(#{i.icons['64']})"}
- .row
- .col-lg-12
- %a#flathubbtn.btn.btn-default.btn-xl.page-scroll{:href => "http://flathub.org/"} Install apps on Flathub
-
+ .col-lg-10.col-lg-offset-1
+ %h1.section-heading
+ The future of apps on Linux
-%section#devsplash.bg-secondary
+%section#appsplash.bg-secondary
.container
- .row.largegap.centered
- .col-sm-6.col-sm-offset-3
- %h2 Publish apps on every linux distribution
- %p Flatpak is distro agnostic. Developers can distribute on every Linux distribution simultaneously and with ease.
.row
- .col-lg-8.col-lg-offset-2
- %p
- =partial "distro-grid.svg"
- .row
- .col-sm-8.col-sm-offset-2.centered
- %a.btn.btn-default.btn-xl.page-scroll{:href => "/hello-world.html"} 5 minute tutorial
- %a.btn.btn-primary.btn-xl.page-scroll{:href => "http://docs.flatpak.org/en/latest/"} Developer guide
+ .col-sm-6.col-sm-offset-1
+ %h3
+ Start using Flatpak and install from a growing collection of apps
+ .appgrid
+ - 0.upto(6) do |i|
+ - if data.apps[i].icons["128"]
+ .icon.featured{:style => "background-image: url(#{data.apps[i].icons['128']})"}
+ - elsif data.apps[i].icons["64"]
+ .icon{:style => "background-image: url(#{data.apps[i].icons['64']})"}
+ .col-sm-4.col-sm-offset-1.centered
+ %a#quicksetupbtn.btn-default.btn.btn-xl.page-scroll{:href => "/setup"} Get set up
+
+ %p.small.mediumgap
+ Already set up? Head over to
+ = link_to "Flathub", "https://flathub.org"
+ to install apps.
+
%section.bg-primary-neutral
.container
+ .row.centered
+ .col-sm-10.col-sm-offset-1
+ %iframe.full{'width'=>'100%', 'src'=>'https://www.youtube.com/embed/jDVCITRWGgs', 'frameborder'=>'0', 'allowfullscreen'=>'true'}
+ =link_to 'Flatpak 1.0', 'https://youtu.be/jDVCITRWGgs'
.row.centered
.col-sm-6.col-sm-offset-3
%h2 A new world for application developers
+ %p Flatpak changes app distribution for the better. Advantages include:
.row.largegap
.col-sm-5.col-sm-offset-1
- %h4 Cross-distro
- %p Create one app bundle and distribute it to the entire Linux desktop market.
+ %h4 Build for every distro
+ %p Create one app and distribute it to the entire Linux desktop market.
.col-sm-5
%h4 Stable platforms
- %p Runtimes provide stable sets of dependencies that can be used by applications.
+ %p Runtimes provide platforms of common libraries that you can depend on.
.row
.col-sm-5.col-sm-offset-1
%h4 Consistent environments
- %p Develop and test your application in an environment that's identical to the one users have.
+ %p Develop and test your application in an environment that’s identical to the one users have.
.col-sm-5
- %h4 Control over dependencies
- %p Dependencies that aren't in a runtime can be bundled as part of an application. Versions of the dependencies that are used can be fixed and patched.
+ %h4 Full control over dependencies
+ %p Flatpak makes it easy to bundle your own libraries as part of your app.
.row
.col-sm-5.col-sm-offset-1
%h4 Easy build tools
- %p
- Flatpak's build tools are simple and easy to use, and come with a
- =link_to 'full set of documentation.', 'http://docs.flatpak.org/'
+ %p
+ Flatpak’s build tools are simple and easy to use, and come with a
+ =link_to 'full set of documentation.', 'https://docs.flatpak.org/'
.col-sm-5
%h4 Future-proof builds
- %p Runtimes are forward compatible, irrespective of distribution changes. Flatpak applications run on new Linux distribution versions as they are released.
+ %p Flatpak apps continue to be compatible with new versions of Linux distributions.
+ .row
+ .col-sm-5.col-sm-offset-1
+ %h4 Distribution made easy
+ %p
+ Make your app available to a rapidly growing audience of Flatpak users, with
+ =link_to 'Flathub.', 'https://flathub.org/'
+ .col-sm-5
+ %h4 An independent project
+ %p Flatpak is developed by an independent community, with no lock-in to a single vendor.
+ .row.largegap
+ .col-sm-6.col-sm-offset-4
+ %a.btn.btn-default.btn-xl.page-scroll{:href => "https://docs.flatpak.org/en/latest/getting-started.html"} 5 minute tutorial
+ %a.btn.btn-primary.btn-xl.page-scroll{:href => "https://docs.flatpak.org/en/latest/"} Developer guide
+
+%section#devsplash.bg-secondary
+ .container
+ .row.largegap
+ .col-sm-5.col-sm-offset-1
+ %h3
+ Flatpak can be used with a total of
+ = data.distro.count
+ distros
+ %p
+ See the
+ = link_to "complete list.", "/setup"
+ .col-sm-6
+ .distrogrid
+ - 0.upto(4) do |i|
+ .icon{:style => "background-image: url(/img/distro/#{data.distro[i].logo})"}
%section.bg-primary
.container
@@ -77,14 +106,14 @@ description: The days of chasing multiple Linux distributions are over. Standalo
%p
Bringing Flatpak technology into Debian enables us to run applications in a predictable environment with their most suitable library stack, without compromising the base OS's stability and flexibility.
.author
- %em Simon McVittie
+ %em Simon McVittie
.title Senior Software Engineer, Collabora
.col-sm-5
%blockquote
%p
At Endless, we’re proud to be a part of this movement and have fully embraced Flatpak by readily converting all of our applications for our upcoming release and continuing to build new Flatpak apps.
.author
- %em Jonathan Blandford
+ %em Jonathan Blandford
.title VP of Software Engineering, Endless
.row
.col-sm-5.col-sm-offset-1
@@ -97,7 +126,7 @@ description: The days of chasing multiple Linux distributions are over. Standalo
.col-sm-5
%blockquote
%p
- Flatpak will enable us (as a Linux ISV) to distribute a better LibreOffice, with up-to-date dependencies and a platform that can run on many systems. I'm excited to see that happen.
+ Flatpak will enable us (as a Linux ISV) to distribute a better LibreOffice, with up-to-date dependencies and a platform that can run on many systems. I’m excited to see that happen.
.author
%em Michael Meeks
.title Director, The Document Foundation
diff --git a/source/javascripts/command.js b/source/javascripts/command.js
new file mode 100644
index 00000000..45ebfce6
--- /dev/null
+++ b/source/javascripts/command.js
@@ -0,0 +1,39 @@
+// A web component to display a terminal command with a copy button.
+
+// Icons are from https://github.com/lucide-icons/lucide
+const copyIcon = ``;
+const checkIcon = ``;
+
+// Define custom element, so we can do apt install flatpak
+class TerminalCommand extends HTMLElement {
+ constructor() {
+ super();
+ }
+ connectedCallback() {
+ const commands = this.textContent
+ .trim()
+ .split(/\n|\\n/)
+ .map((command) => command.trim())
+ .filter(Boolean);
+
+ this.innerHTML = "";
+
+ const code = document.createElement("code");
+ code.innerHTML = commands
+ .map((command) => `$ ${command}`)
+ .join("\n");
+ this.appendChild(code);
+
+ const button = document.createElement("button");
+ button.title = "Copy the command to clipboard";
+ button.innerHTML = copyIcon;
+ button.addEventListener("click", () => {
+ navigator.clipboard.writeText(commands.join("\n"));
+ button.innerHTML = checkIcon;
+ setTimeout(() => (button.innerHTML = copyIcon), 1000);
+ });
+ this.appendChild(button);
+ }
+}
+
+customElements.define("terminal-command", TerminalCommand);
diff --git a/source/layouts/layout.haml b/source/layouts/layout.haml
index 5c0ec3bc..ded26598 100644
--- a/source/layouts/layout.haml
+++ b/source/layouts/layout.haml
@@ -1,16 +1,17 @@
!!!5
%html
%head
- %title
+ %title
=current_page.data.title
%meta{content: "text/html; charset=UTF8", "http-equiv" => "content-type"}/
%meta{content: "#{current_page.data.description}", name: "description"}/
%meta{content: "bundle,application,runtime,flatpak,xdg-app", name: "keywords"}/
- %meta{content: "width=device-width,initial-scale=1", name: "viewport" }/
- %link{rel:"icon", "type" => "image/png", href:"img/favicon.png"}/
+ %meta{content: "width=device-width,initial-scale=1", name: "viewport" }/
+ %meta{content: "Flatpak", property: "og:site_name"}/
+ %meta{content: current_page.data.title, property: "og:title"}/
+ %meta{content: image_path('/img/favicon.svg'), property: "og:image"}/
+ %meta{content: "website", property: "og:type"}/
%link{rel:"shortcut icon", "type" => "image/x-icon", href:"/favicon.ico"}/
- %link{rel:"apple-touch-icon", "sizes" => "57x57", href:"img/favicon57.png"}/
- %link{rel:"apple-touch-icon", "sizes" => "152x152", href:"img/favicon152.png"}/
= stylesheet_link_tag :fonts
= stylesheet_link_tag :site
= stylesheet_link_tag :animate
@@ -21,7 +22,8 @@
= javascript_include_tag "jquery.toc.min"
= javascript_include_tag :bootstrap
= javascript_include_tag :all
- = google_analytics_universal_tag
+ = javascript_include_tag :command, defer: true
+ = matomo
%body#page-top
%nav#mainNav.navbar.navbar-default.navbar-fixed-top
diff --git a/source/presentations.html.haml.markdown b/source/presentations.html.haml.markdown
new file mode 100644
index 00000000..4eba26c9
--- /dev/null
+++ b/source/presentations.html.haml.markdown
@@ -0,0 +1,142 @@
+---
+title: Presentations & Articles
+description: Presentations and articles about Flatpak
+---
+
+:markdown
+
+ # Presentations & Articles
+
+
+
+ If you know of a presentation or article that isn't listed, please [file an issue](https://github.com/flatpak/flatpak.github.io/issues/new) so we can add it!
+
+ ## 2021
+
+ [**Will Thompson: Automate your Flatpak manifest updates today**](https://www.youtube.com/watch?v=c_dG_ngnJk4)
+ Linux App Summit, May 2021
+
+ [**Jan Beran: Making flatpaks from Fedora RPMs**](https://www.youtube.com/watch?v=IuxHidCdbPo)
+ Linux App Summit, May 2021
+
+ [**Valentin David: Freedesktop SDK on RISC-V**](https://www.youtube.com/watch?v=INTbqkck258)
+ Linux App Summit, May 2021
+
+ ## 2020
+
+ [**Alexander Larsson: Flatpak, an introduction (Lightning Talk)**](https://www.youtube.com/watch?v=0yeXTounX3E)
+ Linux App Summit, November 2020
+
+ [**Bartłomiej Piotrowski: Flathub: The State of the Union**](https://www.youtube.com/watch?v=IqHEx-Lug8k)
+ Linux App Summit, November 2020
+
+ [**Felipe Borges: Application sandboxing with Flatpak Portals**](https://www.youtube.com/watch?v=3rCIEzfZw1I)
+ DevConf.CZ, Brno, Czechia, January 2020
+
+ ## 2019
+
+ [**Robert McQueen: Building an app store with Flathub**](https://www.youtube.com/watch?v=ZGAfYP3OiAI)
+ Linux App Summit, Barcelone, Spain, November 2019
+
+ [**Alexander Larsson: Maintaining a Flatpak Repository**](https://www.youtube.com/watch?v=q-_fKWby0ds&list=PLkmRdYgttscEuv9v2-H9P5FBj8-td_Nri&index=24)
+ GUADEC, Thessaloniki, Greece, August 2019
+
+ [**Valentin David, Adam Jones: Freedesktop-sdk Status Update and Future Plans**](https://www.youtube.com/watch?v=ky-inEefWpE&list=PLkmRdYgttscEuv9v2-H9P5FBj8-td_Nri&index=20)
+ GUADEC, Thessaloniki, Greece, August 2019
+
+ [**Richard Brown: Help, I'm Falling in Love with Flatpak**](https://www.youtube.com/watch?v=7p4y9Meyy0M&list=PLkmRdYgttscEuv9v2-H9P5FBj8-td_Nri&index=12)
+ GUADEC, Thessaloniki, Greece, August 2019
+
+ [**Matthias Clasen: Portals - Principles and Practice**](https://www.youtube.com/watch?v=bIzJyp8sb70&list=PLkmRdYgttscEuv9v2-H9P5FBj8-td_Nri&index=9)
+ GUADEC, Thessaloniki, Greece, August 2019
+
+ [**Owen Taylor: Flatpaks in Fedora - an update**](https://www.youtube.com/watch?v=mpCXK6PqvDk)
+ DevConf.CZ, Brno, Czechia, January 2019
+
+ [**Jiří Janoušek: Fight Linux fragmentation with Flatpak**](https://www.youtube.com/watch?v=_ZmgdnhvjvM)
+ DevConf.CZ, Brno, Czechia, January 2019
+
+ [**Felipe Borges: Running virtual machines in the Flatpak sandbox**](https://www.youtube.com/watch?v=EdrSJMKikUM)
+ DevConf.CZ, Brno, Czechia, January 2019
+
+ [**Kukuh Syafaat: LibreOffice Flatpak, Snap and AppImage**](https://wiki.documentfoundation.org/File:AsiaCon2019_Kukuh_Syafaat.pdf)
+ LibreOffice Asia Conference 2019, Tokyo, Japan, May 2019
+
+ ## 2018
+
+ [**Jiří Janoušek: Why and How I Switched to Flatpak**](https://www.youtube.com/watch?v=OuySHov0gdA)
+ LinuxDays, Prague, Czechia, October 2018
+
+ [**Alexander Larsson: Flatpak - a technical walk-through**](https://people.gnome.org/~alexl/presentations/all-systems-go-2018.pdf)
+ All Systems Go! Berlin, Germany, September 2018
+
+ [**Robert McQueen & Jorge García: Flathub, app store and build service for flatpak apps**](https://www.youtube.com/watch?v=Hga20qlyknw)
+ GUADEC, Almeria, Spain, July 2018
+
+ [**Adam Jones & Valentin David: Freedesktop SDK: the future of Linux runtimes**](https://www.youtube.com/watch?v=rhEzTQg_LEk)
+ GUADEC, Almeria, Spain, July 2018
+
+ [**Matthew Leeds: P2P Distribution of Flatpaks and OSTrees**](https://www.youtube.com/watch?v=SIPOfPv1z1s)
+ GUADEC, Almeria, Spain, July 2018
+
+ [**Owen Taylor: A distribution approach to building Flatpaks**](https://www.youtube.com/watch?v=EbvxZa2Blgs)
+ DevConf.CZ, Brno, Czechia, January 2018
+
+ [**Robert McQueen: Desktop OS of the future: ostree + flatpak**](https://www.youtube.com/watch?v=FcykFHJEDUU)
+ DevConf.CZ, Brno, Czechia, January 2018
+
+ [**Alexander Larsson: Flatpaking your app for fame and fortune**](https://www.youtube.com/watch?v=SBWGwwrGR8M)
+ DevConf.CZ, Brno, Czechia, January 2018
+
+ [**Kukuh Syafaat: openSUSE Leap & Flatpak**](https://events.opensuse.org/conferences/summitasia18/program/proposals/2005)
+ openSUSE.Asia Summit 2018, Taipei, Taiwan, August 2018
+
+ ## 2017
+
+ [**Alexander Larsson: Taking back the apps from the distributions**](https://www.youtube.com/watch?v=IUA38lvb_tM)
+ LAS GNOME, October 2016, Portland, USA
+
+ [**Jorge Garcia:Building a Flatpak based app store**](https://www.youtube.com/watch?v=MFue217zmyk)
+ GUADEC, August 2017, Manchester, UK
+
+ [**Jan Grulich & Martin Bříza: Flatpak and KDE & the state of Qt integration in GNOME**](https://www.youtube.com/watch?v=U8zlbXYTN2U)
+ GUADEC, August 2017, Manchester, UK
+
+ [**Richard Brown: Resurrecting Dinosaurs - what could possibly go wrong?**](https://www.youtube.com/watch?v=RPblTKt4Klo)
+ GUADEC, August 2017, Manchester, UK
+
+ [**Simon McVittie: Flatpak and Debian**](https://www.collabora.com/news-and-blog/blog/2017/08/17/debconf-17-flatpak-and-debian/)
+ Debconf, August 2017, Montreal, Canada
+
+ [**Linux Magazine: Flatpak and snap**](http://www.linux-magazine.com/Online/Features/Universal-Package-Formats-and-How-They-Differ)
+ June 2017
+
+ [**Mario Sanchez Prada & Richard Hughes: The future of linux application distribution**](https://speakerdeck.com/mariospr/the-future-of-linux-application-distribution-ostree-flatpak-and-gnome-software)
+ March 2017, Samsung Research, Staines, UK
+
+ [**Alexander Larsson: Flatpak: Apps on the linux desktops**](https://www.youtube.com/watch?v=xIjxNtIwcBA)
+ foss-north 2017, Gothenburg, Sweden
+
+ [**Matthias Clasen: Flatpak – A new way to distribute applications**](https://mclasen.fedorapeople.org/devconf-flatpak.pdf)
+ January 2017, devconf.cz, Brno, Czech Republic
+
+ [**Kukuh Syafaat: Flatpak & AppImage Usage on openSUSE. Which One Suitable for openSUSE Users?**](https://events.opensuse.org/conferences/summitasia17/program/proposals/1502)
+ openSUSE.Asia Summit 2017, October 2017, Chofu, Tokyo, Japan
+
+ ## 2016
+
+ [**Alexander Larsson: Flatpak status update and future plans**](https://www.youtube.com/watch?v=G1OFcNQ5Fw8)
+ GUADEC, August 2016, Karlsruhe, Germany
+
+ [**Fedora Magazine: Explore Flatpak in Fedora 24**](https://fedoramagazine.org/explore-flatpak-fedora-24/)
+ June 2016
+
+ [**Jens Petersen: Generic standalone linux app packages**](https://www.slideshare.net/JensPetersen2/flatpak-introdiction)
+ FUDCon APAC 2016, Phnom Penh, Cambodia
+
+ ## 2015
+
+ [**Christian Hergert: Flatpak, the easiest, fastest, and safest software distribution platform**](https://www.socallinuxexpo.org/scale/15x/presentations/flatpak-easiest-fastest-and-safest-software-distribution-platform)
+ SCALE 2015, Pasadena, USA
+
+
diff --git a/source/press.html.haml b/source/press.html.haml
new file mode 100644
index 00000000..47bcf601
--- /dev/null
+++ b/source/press.html.haml
@@ -0,0 +1,37 @@
+---
+title: Flatpak—the future of application distribution
+description: Press
+---
+
+%section#about
+ .container
+ .row
+ .col-lg-8.col-lg-offset-2
+ %h1.section-heading.text-center Press Information
+ %hr.primary
+ %p
+ We are very happy to answer questions from journalists and tech writers. Interview opportunities can also be arranged.
+ .row
+ .col-lg-8.col-lg-offset-2
+ %h3 Press releases
+ .timeline.mediumgap
+ .date 20 August 2018
+ .description
+ =link_to "Flatpak 1.0 released, Ready for Prime Time", "press/2018-08-20-flatpak-1.0.html"
+ .date 21 June 2016
+ .description
+ =link_to "Announcing Flatpak – Next Generation Linux Applications", "press/2016-06-21-flatpak-released.html"
+ .row.largegap
+ .col-lg-8.col-lg-offset-2
+ %h3 Graphics and Logo
+ %p
+ The Flatpak logo is licensed Creative Commons Attribution 3.0 and can be
+ = succeed "." do
+ =link_to "downloaded here", "/img/flatpak-logos.zip"
+ .row
+ .col-lg-8.col-lg-offset-2
+ %h3 Contact
+ %p
+ Press queries, including requests for comments and interviews can be directed to
+ = succeed "." do
+ =link_to "press@flatpak.org", "mailto:press@flatpak.org"
diff --git a/source/press/2016-06-21-flatpak-released.html.haml.markdown b/source/press/2016-06-21-flatpak-released.html.haml.markdown
index 06b59ca9..e4730d32 100644
--- a/source/press/2016-06-21-flatpak-released.html.haml.markdown
+++ b/source/press/2016-06-21-flatpak-released.html.haml.markdown
@@ -10,7 +10,7 @@ description: Announcing Flatpak – Next Generation Linux Applications
## Build once, run anywhere
-
+
The Linux desktop has long been held back by platform fragmentation. This has been a burden on developers, and creates a high barrier to entry for third party application developers. Flatpak aims to change all that. From the very start its primary goal has been to allow the same application to run across a myriad of Linux distributions and operating systems. In doing so, it greatly increases the number of users that application developers can easily reach.
diff --git a/source/press/2018-08-20-flatpak-1.0.html.haml.markdown b/source/press/2018-08-20-flatpak-1.0.html.haml.markdown
new file mode 100644
index 00000000..9a24cefe
--- /dev/null
+++ b/source/press/2018-08-20-flatpak-1.0.html.haml.markdown
@@ -0,0 +1,34 @@
+---
+title: Flatpak 1.0
+description: Flatpak 1.0 Released, Ready for Prime Time
+---
+
+:markdown
+ # Flatpak 1.0 Released, Ready for Prime Time
+
+
+
+ **Stockholm, Sweden, 20 August 2018**: Flatpak, the Linux desktop app distribution framework, reached an important milestone today, with the release of its 1.0 version.
+
+ For those who don't know, once an app has been built as a Flatpak, it can be installed on virtually any Linux distribution. This model is designed to make Linux a more attractive option for desktop app developers, and provides developers with a more stable platform on which to build and develop.
+
+ Discussing the release, Flatpak’s lead developer, Alexander Larsson, has said: “A lot of work has gone into Flatpak 1.0 and we're confident that it's ready for wider use. Flatpak's goal has always been to revolutionize the Linux ecosystem and this is an important step towards that.” A 1.0 release generally marks the point at which software has become “feature complete”, so the fact that the developers are calling this a 1.0 is significant. But what does it mean in practice?
+
+ Flatpak 1.0 comes with a collection of new features that application developers can take advantage of. Developers can mark versions of their apps as end of life, to indicate when they are no longer supported. There’s a new mechanism for apps to restart themselves. The command line interface has had a raft of improvements, including new commands and options.
+
+ Furthermore, Flatpak has matured since its last major stable release in October 2017. The new version promises to be faster and more reliable. There's also been some internal tidying up and reorganization. (This isn't so interesting to users and app developers, but it makes Flatpak that bit easier to integrate with your favorite Linux distro.)
+
+ However, some of the biggest changes have been in the Flatpak ecosystem. To coincide with the release of Flatpak 1.0, the Flatpak developers are also taking the beta label off their Flathub service. Flathub is the central store for Flatpak apps. It is both a repository that can be used by Linux desktops, and a [website that users can use to browse and install apps](https://flathub.org/). It had a quiet, soft launch back in May 2017 and has seen rapid growth in the number of apps and users since then.
+
+ Flathub has become a major feature for developers, as LibreOffice’s Stephan Bergmann made clear: “Flatpak has come a long way since we first started using it; nowadays we can type a trivial command to get the latest LibreOffice 6.1 built and published on Flathub automatically. What keeps impressing me is the breadth and depth of the bug reports we receive for the LibreOffice Flatpak version. It shows that people are using it in all kinds of scenarios.”
+
+ Another significant development in the Flatpak ecosystem relates to their “runtimes” - the platforms that applications are built and run against. The main “Freedesktop” runtime that is used by most Flatpak apps is having a major release to coincide with the Flatpak 1.0. This 18.08 release has a new lifecycle policy, which includes a regular release schedule and guarantees for support periods and security updates. This gives Flatpak’s app platforms a similar level of support to commercial operating system offerings.
+
+ Flatpak's developers also point to other areas where the framework has matured. Their [developer documentation](https://docs.flatpak.org/en/latest/) has been rewritten and is much more complete. Flatpak’s website also includes [tutorials for setting up Flatpak on a lot more Linux distributions](https://flatpak.org/setup/) .
+
+ The big question is what this means for the Linux landscape. Last November, Linux Mint, one of the larger Linux distributions, started using Flatpak by default, and Fedora is planning to start building its own Flatpaks very soon. It might just be that a tipping point has been reached.
+
+ *This press release, including all content and media, can be freely used and modified without the need for attribution.*
+
+
-
- The Linux desktop has long been held back by platform fragmentation. This has been a burden on developers, and creates a high barrier to entry for third party application developers. Flatpak aims to change all that. From the very start its primary goal has been to allow the same application to run across a myriad of Linux distributions and operating systems. In doing so, it greatly increases the number of users that application developers can easily reach.
-
- Speaking about the goals behind Flatpak, Alexander Larsson, its lead developer, said: “Application developers on Linux have always been prevented from having a direct relationship with their users. With Flatpak we're aiming to change that, so developers know exactly what their users are getting. With this launch we are making that goal a reality.”
-
- Flatpak has been available for a range of Linux distributions for several weeks. It allows application developers to build against a series of stable platforms (known as runtimes), as well as to bundle libraries directly within their applications. Flatpak is also standards compliant, offering support for the [Open Container Initiative](https://www.opencontainers.org/) specification.
-
- A growing range of applications are already available as Flatpaks, including Firefox, LibreOffice, the GIMP, InkScape, MyPaint, Darktable, and a large number of stock GNOME applications. [flatpak.org provides instructions on how to easily try these yourself](/apps.html). Linux desktops are also adopting Flatpak. A fully functional GNOME runtime has been available since March: this allows application developers to build and distribute Flatpaks using the GNOME development stack. Work on a similar runtime for KDE is proceeding.
-
- Not only does Flatpak provide cross-distribution installation, but it also allows forward compatibility. Michael Meeks, Director of [The Document Foundation](https://www.documentfoundation.org/), said: “Until now, building a LibreOffice that works for every Linux user has involved some horrible compromises caused by the need to build our binaries on an ancient Linux version to get good forward compatibility. Flatpak will enable us (as a Linux ISV) to distribute a better LibreOffice, with up-to-date dependencies and a platform that can run on many systems. I'm excited to see that happen.”
-
- ## Security first
-
- Another area where the Linux desktop has been weak is security: it has never had a viable model for isolating applications, or for gatekeeping access to user data. This is another area where Flatpak aims to upset the status quo. To this end, it has been built from the ground up with security in mind.
-
- Flatpak apps are sandboxed. From within the sandbox, the only things the app can “see” are itself and a limited set of libraries and operating system interfaces. This effectively isolates apps from each other as well as from the host system and makes it much harder for applications to steal user data or exploit one another.
-
- Initial Flatpak releases have concentrated on application building, distribution and installation, and while the foundations of sandboxing are in place, there are still missing pieces. “The next major Flatpak release will be all about sandboxing”, says Larsson. “Application authors will see a much more complete set of interfaces for interacting with the operating system from within a sandbox.”
-
- Another major part of this work is the widescale move towards the Wayland display server on Linux. X11 is inherently insecure, which makes it impossible to sandbox applications that are using it. In that sense, the growing maturity of Wayland complements Flatpak's emergence, and paves the way for much more complete security model for Linux distributions.
-
- ## Background to Flatpak
-
- [](/img/CC-BY-SA-4.0-Garrett-LeSage.jpg)
-
- Flatpak is the brainchild of Alexander Larsoon, Principal Software Engineer at Red Hat. Larson has been working in the Linux desktop space for 18 years. He was the principal author of GVfs (GNOME's Virtual Filesystem) and has done critical work on Docker, the SPICE protocol, the Gecko rendering engine, GLib and GTK+. He has considerable experience in the area of application bundling.
-
- Flatpak builds on several cutting edge technologies. Under the hood, it makes significant use of [OSTree](https://ostree.readthedocs.org), which can be described as “Git for large binaries”. This provides much of the functionality for hosting software repositories. It also makes Flatpak extremely efficient: applications and libraries that are installed with Flatpak are de-duplicated, saving disk space; “static deltas” reduce the size of downloads for software updates.
-
- For sandboxing, Flatpak makes use of the [Bubblewrap](https://github.com/projectatomic/bubblewrap) utilty, as well as several Linux kernel features (such as cgroups and namespaces), which helps to make it portable across distributions.
-
- ## Rapid community growth and adoption
-
- It is well known that Fedora is making plans around Flatpak. Commenting on Flatpak, Christian F.K. Schaller (Senior Manager at Red Hat and member of the Fedora Workstation Working Group) stated: “The Fedora Workstation team are very excited about Flatpak and the prospects it brings for making the Linux desktop easier to develop for. We plan to continue supporting this effort going forward and help advocate it to a wider audience."
-
- There is also interest from other parties. One early adopter of Flatpak is [Endless Computers](https://endlessm.com/). Speaking about the launch of Flatpak, Jonathan Blandford (VP of Software Engineering at Endless) said: “The Flatpak launch represents a major milestone in providing a unified context for Linux developers. At Endless, we’re proud to be a part of this movement and have fully embraced Flatpak by readily converting all of our applications for our upcoming release and continuing to build new Flatpak apps. We encourage others to do so as well in what we hope to be a revolution among Linux app creation and adoption.”
-
- 
-
- Other distributions are showing interest, as well as other Free Software companies. Simon McVittie is Senior Software Engineer at Collabora and a Debian developer, and is himself looking to Flatpak: “Bringing Flatpak technology into Debian enables us to run applications in a predictable environment with their most suitable library stack, without compromising the base OS's stability and flexibility. Flatpak also retains the ability to deploy security updates, making it a significant enhancement for the many Debian-based desktop and embedded distributions, both in the community and in commercial products.”
-
- One reason for the increasing interest in Flatpak is due to its adaptability and the fact that it is a genuinely upstream project. It can be used and adapted as part of downstream and bespoke solutions, is hosted on Freedesktop.org and Github, and is licensed with the LGPL, with no copyright assignment or contributor license agreement required.
-
- Larsson is obviously pleased by the momentum behind Flatpak. “It's exciting to see the growing interest in what we are doing, as developers realise the possibilities of the technology,” he said.
-
- More information about Flatpak can be found on [flatpak.org](http://flatpak.org/).
-
-
The Linux desktop has long been held back by platform fragmentation. This has been a burden on developers, and creates a high barrier to entry for third party application developers. Flatpak aims to change all that. From the very start its primary goal has been to allow the same application to run across a myriad of Linux distributions and operating systems. In doing so, it greatly increases the number of users that application developers can easily reach.
diff --git a/source/press/2018-08-20-flatpak-1.0.html.haml.markdown b/source/press/2018-08-20-flatpak-1.0.html.haml.markdown
new file mode 100644
index 00000000..9a24cefe
--- /dev/null
+++ b/source/press/2018-08-20-flatpak-1.0.html.haml.markdown
@@ -0,0 +1,34 @@
+---
+title: Flatpak 1.0
+description: Flatpak 1.0 Released, Ready for Prime Time
+---
+
+
+ **Stockholm, Sweden, 20 August 2018**: Flatpak, the Linux desktop app distribution framework, reached an important milestone today, with the release of its 1.0 version.
+
+ For those who don't know, once an app has been built as a Flatpak, it can be installed on virtually any Linux distribution. This model is designed to make Linux a more attractive option for desktop app developers, and provides developers with a more stable platform on which to build and develop.
+
+ Discussing the release, Flatpak’s lead developer, Alexander Larsson, has said: “A lot of work has gone into Flatpak 1.0 and we're confident that it's ready for wider use. Flatpak's goal has always been to revolutionize the Linux ecosystem and this is an important step towards that.” A 1.0 release generally marks the point at which software has become “feature complete”, so the fact that the developers are calling this a 1.0 is significant. But what does it mean in practice?
+
+ Flatpak 1.0 comes with a collection of new features that application developers can take advantage of. Developers can mark versions of their apps as end of life, to indicate when they are no longer supported. There’s a new mechanism for apps to restart themselves. The command line interface has had a raft of improvements, including new commands and options.
+
+ Furthermore, Flatpak has matured since its last major stable release in October 2017. The new version promises to be faster and more reliable. There's also been some internal tidying up and reorganization. (This isn't so interesting to users and app developers, but it makes Flatpak that bit easier to integrate with your favorite Linux distro.)
+
+ However, some of the biggest changes have been in the Flatpak ecosystem. To coincide with the release of Flatpak 1.0, the Flatpak developers are also taking the beta label off their Flathub service. Flathub is the central store for Flatpak apps. It is both a repository that can be used by Linux desktops, and a [website that users can use to browse and install apps](https://flathub.org/). It had a quiet, soft launch back in May 2017 and has seen rapid growth in the number of apps and users since then.
+
+ Flathub has become a major feature for developers, as LibreOffice’s Stephan Bergmann made clear: “Flatpak has come a long way since we first started using it; nowadays we can type a trivial command to get the latest LibreOffice 6.1 built and published on Flathub automatically. What keeps impressing me is the breadth and depth of the bug reports we receive for the LibreOffice Flatpak version. It shows that people are using it in all kinds of scenarios.”
+
+ Another significant development in the Flatpak ecosystem relates to their “runtimes” - the platforms that applications are built and run against. The main “Freedesktop” runtime that is used by most Flatpak apps is having a major release to coincide with the Flatpak 1.0. This 18.08 release has a new lifecycle policy, which includes a regular release schedule and guarantees for support periods and security updates. This gives Flatpak’s app platforms a similar level of support to commercial operating system offerings.
+
+ Flatpak's developers also point to other areas where the framework has matured. Their [developer documentation](https://docs.flatpak.org/en/latest/) has been rewritten and is much more complete. Flatpak’s website also includes [tutorials for setting up Flatpak on a lot more Linux distributions](https://flatpak.org/setup/) .
+
+ The big question is what this means for the Linux landscape. Last November, Linux Mint, one of the larger Linux distributions, started using Flatpak by default, and Fedora is planning to start building its own Flatpaks very soon. It might just be that a tipping point has been reached.
+
+ *This press release, including all content and media, can be freely used and modified without the need for attribution.*
+
+