https://github.com/jellyfin/jellyfin-blog/blob/d462ce2b206dcab2c888799666e8f22131baaf9b/content/contact/_index.md?plain=1#L28

Describe the bug

Your website does not sell your product.

To find out about the product and why I would want to use it, I had to do a Google search on "Emby" -- the thing it used to be.

To Reproduce

1. Go to https://jellyfin.org/
2. Click on 'Learn More'
3. Note there's no compelling reason to use the product there
4. Click the FAQ
5. Note the lack of "What is Jellyfin?" and "Why would I want to use Jellyfin?"
6. Accept that Jellyfin is defined by what it is not: Emby.
7. Click the "about page" in the "Why fork Emby?" question

What does the About page actually say about your product? Absolutely nothing. Here, I break it down:

Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. (Meaningless marketing blather.) It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. (References Emby, which I know nothing about.) There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it. We welcome anyone who is interested in joining us in our quest! (Standard open source.)

Jellyfin seeks to continue development of the original Emby project with a Free Software ethos. (I still no nothing of Emby.) It is committed to bringing all its users access to the best possible Media System, developed entirely by a community of volunteers who contribute code, documentation, translations, and support to the project. (Open source. What's a "Media System"?)

The Jellyfin project was started in early December 2018 as a result of Emby's decision to take their 3.6 release closed-source, as well as various philosophical differences with the core developers. Jellyfin seeks to be the free software alternative to Emby and Plex to provide media management and streaming from a dedicated server to end-user devices. (Again references Emby, which I know nothing about.)

Expected behavior

I expected something that tried to convince me of why I should use the product.

What is it? What can I do with it? Does it have any compelling features against the competition?

Basically, have you seen any of the following pages:

• https://www.plex.tv/
• https://kodi.tv/about
• https://emby.media/about.html

Logs

n/a

Screenshots

n/a

System:

n/a (only a potential user)

Additional context

Jellyfin Desktop is apparently not maintained anymore, it would be nice to have it either removed from the website or tagged as unmaintained.

Opening an issue to continue discussion instead of staying in a commit

@Andy2244 Just regarding location, I would suggest replying in the pull request, instead of on the commit. Though commenting/replying on a commit is possible, it doesn't show up in the GitHub mobile app, and it's hard to keep track of. Replying on a Pull Request is what I believe to be the generally accepted way to comment, keeping the commit for line specific comments. Since this has grown much bigger, I am creating a separate issue entirely.

I will be clear and say that I had a much nicer and fuller response that I have been drafting since last night, but my motivation for it has quickly evaporated. There's also not much energy left over after work during the week - I do carry a full-time job and many others also have other commitments.

Let's just start from the top and go from there. I am choosing not to address anything else (including communication) at this time, in the hope that we can just move forward. Here's what I would be looking for:

1. Would you be able to choose a new name for the client you are distributing? Ideally this takes the format of "_____ for Jellyfin" or it can also be an entirely unique name.
2. Would you be able to choose a different/unique logo for your client?
3. Please ensure that you are using a unique application ID for the client, that does not include the org.jellyfin namespace.
4. Of course, please remain compliant with the GPL license for the application. This is just a reminder - to my quick review, you have remained compliant thus far.

Thank you.

Clicking on them takes you no where, but I was able to get to the unstable through the all versions page.

While looking at the website-repo[1] I saw that a feed already exists[2]. That's cool! Would be nice if a link would be on the website and/or also for discoverability in the head.

[1] https://github.com/jellyfin/jellyfin.github.io
[2] https://jellyfin.org/index.xml

SSL port cannot be enabled
8920 SSL port cannot be enabled

Can the "Tag" in the movie introduction interface be set as a clickable option, so that more movies with the same "Tag" can be filtered.

On download page (https://jellyfin.org/downloads/) in section for macOS there is said

Both installers (.dmg) and manual ZIP archives (.zip) are provided.

When you click on stable button for download, site redirects to this link

https://repo.jellyfin.org/releases/server/macos/stable.

which is portable binary version but not .dmg or .app which was mention earlier.

Proper link for download is https://github.com/jellyfin/jellyfin-server-macos/releases/tag/v10.5.2a
I think would be good to fix this because some people could stuck at this point.

The links for autodetecting the RSS feed in the website header are broken:

<!-- /clients/ -->
<link rel="alternate" type="application/rss+xml" href="https://jellyfin.org/clients/index.xml" title="Jellyfin: The Free Software Media System" />

<!-- /downloads/ -->
<link rel="alternate" type="application/rss+xml" href="https://jellyfin.org/downloads/index.xml" title="Jellyfin: The Free Software Media System" />
…

should be: https://jellyfin.org/index.xml.

Noticed the website doesn't acknowledge the availability of groovy releases, might want to update that since it appears to be there now.

From the "downloads" link on the homepage -> Stable:
"We support amd64, armhf, and arm64 for architectures, debian and ubuntu for distributions, and stretch, buster, and bullseye for Debian releases and xenial, bionic, and focal for Ubuntu releases."

The donate links to Open Collective should also be available on the website in addition to Github such that it is accessible to non-developers.

Hello,

I've noticed the seek buttons on the remote don't function in Jelly Fin app.

Please let me know if this is the case for others as well or whether this is already on the radar.

Thanks.

your demo is down. when will it be up again?
Surely you could make a serveless version of the demo and host it on gh-pages alongside everything else? That would be my suggestion.

We should rearrange the client section yet again.

It's been suggested that we move mobile clients higher up on the page, as that is what users are most likely looking for when they come to the site.

In addition, I don't think we have to worry so much about the distinction between Official and Unofficial - if we're listing the client, that means we think it's good enough to recommend. Most official clients will be named "Jellyfin for < platform >", "Jellyfin <platform/form factor>", or "Jellyfin". All the unofficial clients have other names.

Related to #111.

The main page has old screenshots taken during the 10.3 days. We should update it to show off the new 10.5 look!

The hugo build in the pipeline fails a lot. We should fix that. AFAIK a fix is to cache the hugo executable, another solution is to switch to GitHub Actions, there's multiple actions for hugo available.