Remove outdated references in `README` and `ECOSYSTEM` guide

2 files changed, 5 insertions, 109 deletions

diff --git a/ECOSYSTEM.md b/ECOSYSTEM.md
deleted file mode 100644
index da3066d8..00000000
--- a/ECOSYSTEM.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# Ecosystem
-This document describes the Iced ecosystem and explains how the different crates relate to each other.
-
-## Overview
-Iced is meant to be used by 2 different types of users:
-
-- __End-users__. They should be able to:
-  - get started quickly,
-  - have many widgets available,
-  - keep things simple,
-  - and build applications that are __maintainable__ and __performant__.
-- __GUI toolkit developers / Ecosystem contributors__. They should be able to:
-  - build new kinds of widgets,
-  - implement custom runtimes,
-  - integrate existing runtimes in their own system (like game engines),
-  - and create their own custom renderers.
-
-Iced consists of different crates which offer different layers of abstractions for our users. This modular architecture helps us keep implementation details hidden and decoupled, which should allow us to rewrite or change strategies in the future.
-
-<p align="center">
-  <img alt="The Iced Ecosystem" src="docs/graphs/ecosystem.png" width="60%">
-</p>
-
-## The foundations
-There are a bunch of concepts that permeate the whole ecosystem. These concepts are considered __the foundations__, and they are provided by three different crates:
-
-- [`iced_core`] contains many lightweight, reusable primitives (e.g. `Point`, `Rectangle`, `Color`).
-- [`iced_futures`] implements the concurrent concepts of [The Elm Architecture] on top of the [`futures`] ecosystem.
-- [`iced_style`] defines the default styling capabilities of built-in widgets.
-
-<p align="center">
-  <img alt="The foundations" src="docs/graphs/foundations.png" width="50%">
-</p>
-
-## The native target
-The native side of the ecosystem is split into two different groups: __renderers__ and __shells__.
-
-<p align="center">
-  <img alt="The native target" src="docs/graphs/native.png" width="80%">
-</p>
-
-### Renderers
-The widgets of a _graphical_ user interface produce some primitives that eventually need to be drawn on screen. __Renderers__ take care of this task, potentially leveraging GPU acceleration.
-
-Currently, there are two different official renderers:
-
-- [`iced_wgpu`] is powered by [`wgpu`] and supports Vulkan, DirectX 12, and Metal.
-- [`tiny-skia`] is used as a fallback software renderer when `wgpu` is not supported.
-
-Additionally, the [`iced_graphics`] subcrate contains a bunch of backend-agnostic types that can be leveraged to build renderers. Both of the renderers rely on the graphical foundations provided by this crate.
-
-### Shells
-The widgets of a graphical user _interface_ are interactive. __Shells__ gather and process user interactions in an event loop.
-
-Normally, a shell will be responsible of creating a window and managing the lifecycle of a user interface, implementing a runtime of [The Elm Architecture].
-
-As of now, there is one official shell: [`iced_winit`] implements a shell runtime on top of [`winit`].
-
-## The web target
-The Web platform provides all the abstractions necessary to draw widgets and gather users interactions.
-
-Therefore, unlike the native path, the web side of the ecosystem does not need to split renderers and shells. Instead, [`iced_web`] leverages [`dodrio`] to both render widgets and implement a proper runtime.
-
-## Iced
-Finally, [`iced`] unifies everything into a simple abstraction to create cross-platform applications:
-
-- On native, it uses __[shells](#shells)__ and __[renderers](#renderers)__.
-- On the web, it uses [`iced_web`].
-
-<p align="center">
-  <img alt="Iced" src="docs/graphs/iced.png" width="80%">
-</p>
-
-[`iced_core`]: core
-[`iced_futures`]: futures
-[`iced_style`]: style
-[`iced_native`]: native
-[`iced_web`]: https://github.com/iced-rs/iced_web
-[`iced_graphics`]: graphics
-[`iced_wgpu`]: wgpu
-[`iced_glow`]: glow
-[`iced_winit`]: winit
-[`iced_glutin`]: glutin
-[`iced`]: ..
-[`futures`]: https://github.com/rust-lang/futures-rs
-[`glow`]: https://github.com/grovesNL/glow
-[`wgpu`]: https://github.com/gfx-rs/wgpu
-[`winit`]: https://github.com/rust-windowing/winit
-[`glutin`]: https://github.com/rust-windowing/glutin
-[`dodrio`]: https://github.com/fitzgen/dodrio
-[The Elm Architecture]: https://guide.elm-lang.org/architecture/
diff --git a/README.md b/README.md
index a9c37977..41fa220a 100644
--- a/README.md
+++ b/README.md
@@ -34,13 +34,12 @@ Inspired by [Elm].
 * Custom widget support (create your own!)
 * [Debug overlay with performance metrics]
 * First-class support for async actions (use futures!)
-* [Modular ecosystem] split into reusable parts:
+* Modular ecosystem split into reusable parts:
   * A [renderer-agnostic native runtime] enabling integration with existing systems
-  * Two [built-in renderers] leveraging [`wgpu`] and [`tiny-skia`]
+  * Two built-in renderers leveraging [`wgpu`] and [`tiny-skia`]
     * [`iced_wgpu`] supporting Vulkan, Metal and DX12
     * [`iced_tiny_skia`] offering a software alternative as a fallback
   * A [windowing shell]
-  * A [web runtime] leveraging the DOM
 
 __Iced is currently experimental software.__ [Take a look at the roadmap],
 [check out the issues], and [feel free to contribute!]
@@ -49,16 +48,12 @@ __Iced is currently experimental software.__ [Take a look at the roadmap],
 [text inputs]: https://iced.rs/examples/text_input.mp4
 [scrollables]: https://iced.rs/examples/scrollable.mp4
 [Debug overlay with performance metrics]: https://iced.rs/examples/debug.mp4
-[Modular ecosystem]: ECOSYSTEM.md
 [renderer-agnostic native runtime]: runtime/
 [`wgpu`]: https://github.com/gfx-rs/wgpu
 [`tiny-skia`]: https://github.com/RazrFalcon/tiny-skia
 [`iced_wgpu`]: wgpu/
 [`iced_tiny_skia`]: tiny_skia/
-[built-in renderers]: ECOSYSTEM.md#Renderers
 [windowing shell]: winit/
-[`dodrio`]: https://github.com/fitzgen/dodrio
-[web runtime]: https://github.com/iced-rs/iced_web
 [Take a look at the roadmap]: ROADMAP.md
 [check out the issues]: https://github.com/iced-rs/iced/issues
 [feel free to contribute!]: #contributing--feedback
@@ -164,7 +159,7 @@ Read the [book], the [documentation], and the [examples] to learn more!
 ## Implementation details
 
 Iced was originally born as an attempt at bringing the simplicity of [Elm] and
-[The Elm Architecture] into [Coffee], a 2D game engine I am working on.
+[The Elm Architecture] into [Coffee], a 2D game library I am working on.
 
 The core of the library was implemented during May 2019 in [this pull request].
 [The first alpha version] was eventually released as
@@ -172,25 +167,17 @@ The core of the library was implemented during May 2019 in [this pull request].
 implemented the current [tour example] on top of [`ggez`], a game library.
 
 Since then, the focus has shifted towards providing a batteries-included,
-end-user-oriented GUI library, while keeping [the ecosystem] modular:
-
-<p align="center">
-  <a href="ECOSYSTEM.md">
-    <img alt="The Iced Ecosystem" src="docs/graphs/ecosystem.png" width="80%">
-  </a>
-</p>
+end-user-oriented GUI library, while keeping the ecosystem modular.
 
 [this pull request]: https://github.com/hecrj/coffee/pull/35
 [The first alpha version]: https://github.com/iced-rs/iced/tree/0.1.0-alpha
 [a renderer-agnostic GUI library]: https://www.reddit.com/r/rust/comments/czzjnv/iced_a_rendereragnostic_gui_library_focused_on/
 [tour example]: examples/README.md#tour
 [`ggez`]: https://github.com/ggez/ggez
-[the ecosystem]: ECOSYSTEM.md
 
 ## Contributing / Feedback
 
-Contributions are greatly appreciated! If you want to contribute, please
-read our [contributing guidelines] for more details.
+If you want to contribute, please read our [contributing guidelines] for more details.
 
 Feedback is also welcome! You can create a new topic in [our Discourse forum] or
 come chat to [our Discord server].