Website Redesign

jordan commented

2023-09-06 19:18:34 +00:00

Owner

We need to redesign the website. The new website should:

Market Telodendria as the lightest, easiest to install and configure Matrix homeserver. Our target audience is those of small, maybe even embedded deployments. The website should appeal to these users.
Provide links to the Gitea releases page for the change log and releases. It should also provide links to the documentation hosted in Gitea instead of the man pages.
Provide links to accept donations.
Answer these questions!
- What can Telodendria do?
- When will it be usable?

We need to redesign the website. The new website should: - [x] Market Telodendria as the lightest, easiest to install and configure Matrix homeserver. Our target audience is those of small, maybe even embedded deployments. The website should appeal to these users. - [x] Provide links to the Gitea releases page for the change log and releases. It should also provide links to the documentation hosted in Gitea instead of the `man` pages. - [x] Provide links to accept donations. - [x] Answer these questions! - What can Telodendria *do*? - *When* will it be usable?

jordan added this to the Gitea Migration project 2023-09-06 19:18:38 +00:00

jordan added a new dependency 2023-09-06 19:18:53 +00:00

#18 Documentation

jordan added a new dependency 2023-09-06 19:20:04 +00:00

#10 Website "Note" links have bad contrast

~~jordan referenced this issue 2023-09-06 19:20:46 +00:00~~

Website "Note" links have bad contrast #10

jordan commented

2023-09-07 12:01:30 +00:00

Author

Owner

Additional things we should address on the website:

Why use Telodendria over, say, Conduit, which is also a databaseless, single-binary Matrix homeserver?
- Dependency Chain: We probably use less dependencies (though someone should verify this) and thus have a greater control over the code, because we wrote all of it. It is extremely unlikely that we will suffer supply chain attacks, while Cargo is vulnerable to them as it is a self-published repository.
- Standard Tooling: Rust breaks a lot, and has no formal standard. This makes it less than ideal for long-lived software. Telodendria is written in C, a stable, standardized language that will always compile code the same way, making it more portable and sustainable in the future because we don't ever have to worry about upgrading our toolchain—using standard built-in tools will always suffice.

There are probably more reasons, feel free to share them here.

Additional things we should address on the website: - [ ] *Why* use Telodendria over, say, Conduit, which is *also* a databaseless, single-binary Matrix homeserver? - **Dependency Chain:** We probably use less dependencies (though someone should verify this) and thus have a greater control over the code, because we wrote all of it. It is extremely unlikely that we will suffer supply chain attacks, while Cargo is vulnerable to them as it is a self-published repository. - **Standard Tooling:** Rust breaks a lot, and has no formal standard. This makes it less than ideal for long-lived software. Telodendria is written in C, a stable, standardized language that will always compile code the same way, making it more portable and sustainable in the future because we don't ever have to worry about upgrading our toolchain—using standard built-in tools will always suffice. There are probably more reasons, feel free to share them here.

jordan commented

2023-09-08 02:01:49 +00:00

Author

Owner

One of the goals is to be extremely well documented as well. Perhaps advertising Telodendria as well-documented would be a good selling point too.

lda commented

2023-09-08 05:18:06 +00:00

Contributor

Additional things we should address on the website:

Why use Telodendria over, say, Conduit, which is also a databaseless, single-binary Matrix homeserver?
[...]
There are probably more reasons, feel free to share them here.

Portableness on rather exotic architectures might also be a (small?) issue on the Rust side, as it's (current) main compiler relies on LLVM, which, while fast, might not support some strange architectures, the biggest example I know of being the SuperH series, and it seems like Rust has some incompatibilities with old versions of architectures it supports at times(see this)

> Additional things we should address on the website: > > - [ ] *Why* use Telodendria over, say, Conduit, which is *also* a databaseless, single-binary Matrix homeserver? > [...] > There are probably more reasons, feel free to share them here. Portableness on rather exotic architectures might also be a (small?) issue on the Rust side, as it's (current) main compiler relies on LLVM, which, while fast, might not support some strange architectures, the biggest example I know of being the SuperH series, and it *seems* like Rust has some incompatibilities with old versions of architectures it supports at times(see [this](https://matrix.to/#/!ykbwcwqRyRJhteUiDp:bancino.net/$9TI22y6nbk1oEZtbw__sAuoWBA-_G8ps7vMXqmlTHJY?via=bancino.net&via=matrix.org&via=uxn.one))

👍 1

jordan commented

2023-09-08 13:55:59 +00:00

Author

Owner

Good point. Portability is definitely the motivation behind choosing C. I've got to imagine that every platform you'd want to run Telodendria on would have a C compiler.

jordan closed this issue

2023-11-02 00:35:53 +00:00

Website Redesign #30