When I first found Amethyst, in mid-2019, I used to regularly check the Roadmap to see if any of the goals there had been accomplished, mainly the "iOS and Android Support" one. I wanted to use the engine, but had not really a reason to, as my goal at that time was to make mobile games.

I started to realize that the website wasn't cared of that much, and now it seems quite obsolete with those old goals there (which I have no idea if they were done or not, because I did not get involved with the project).

Maybe you/we could update that, possibily showing what has already been done, so that new people may see a reason to use Amethyst, instead of a reason to not to, by thinking it has been abandoned or something like that.

1. https://amethyst.rs/doc

https://amethyst.rs/doc contains a dead link at

<h2>Previous Stable Version (0.12)</h2>
<!-- [... ] -->
    <li><a target="_blank" rel="noopener" href="https://docs.amethyst.rs/v0.12.0/amethyst/">Browse the API Reference</a></li>
<!-- [... ] -->
</ul>

Specifically, https://docs.amethyst.rs/v0.12.0/amethyst/returns a 404.

I don't know if they're still hosted under the amethyst.rs domain somewhere, alternatively you might want to link to https://docs.rs/amethyst/0.12.0/amethyst/ instead.

I'm not sure how to open a PR to fix this, when I search for the strings I can't find them in this repo, at least not on the master branch. It's probably in a different part of your build / content pipeline.

2. README.md

README.md links to https://amethyst-engine.org/ in line 3. The link appears to be unreachable.

At the moment we're using the old prismic gatsby plugin, called gatsby-source-prismic. There's a few drawbacks to this:

• The preview function doesn't work
• There's a bug where the build fails if a rich text field starts with an image

A new plugin has been released by prismic, which uses their new graphql api directly and can be found here. There's 2 major changes that need to be done for us to switch to this:

• We need to use the prismic-dom library since field parsing and conversion won't be included in the source plugin anymore.
• Images will need to be checked for manual styling, since the new plugin doesn't support locally resizing the images using the sharp plugin. This should be fine though, as we're not too image-heavy and don't rely on them scaling fluidly too much.

Please ping me if anyone's interested in taking this on, since I probably won't do this myself very soon.

Could we be using crates.io as an API to display certain listings on our own website?

e.g. could we build a amethyst.rs/crates page that re-renders https://crates.io/keywords/amethyst?

Could be a handy way of going "looking for amethyst tooling? here's the current ecosystem".

Prior art:

• https://users.rust-lang.org/t/lib-rs-was-crates-rs-a-new-faster-crate-index-website/17876
• https://github.com/rust-lang/crates.io/wiki/Projects-that-use-crates.io%27s-API

I was a little disoriented at first from the progression, being Stable -> Previous -> Master. As we continue to add more releases, we will continue to have a greater separation between stable and master. We also don't want to put master at the top, since we want to encourage users to use stable. Instead, we can put them in a special row with two columns.

If you agree, I can also implement this.

The page titles are all very plain right now, both for pages and blog articles. It should be possible to have a background for the title (similar to how medium articles have a title image), probably dimmed a little so that the text remains readable.

This should be implemented as an extra field that will be ignored if not present on articles, and as an extra slice type for static pages. If you're interested in working on this, hit me up and I'll add the types to prismic so the frontend can be developed for it.