Can be done in the admin panel of each respective component.
I think priority=100 is the default value.

Short strings, general, documentation, contribute?

https://antennapod.org/contribute/translate

We encourage you to start with the components General and the Short strings, because these will be the first elements a user sees on the website. The component Documentation is a very close second priority, because this section is directly available via the app when people tap on Support. The Contribute component comes last, because a basic understanding of English is needed anyway to interact with the community.

In the build logs I just saw the following:

Run actions/setup-ruby@v1
------------------------
NOTE: This action is deprecated and is no longer maintained.
Please, migrate to https://github.com/ruby/setup-ruby, which is being actively maintained.

Could that be why my recent commits are failing? @ByteHamster

In reference to my comment on AntennaPod issue 2463

Could the FAQ not address this situation directly as it's potentially catastrophic?

I found myself victim of this bug and was unsure how to proceed in recovering the situation. I thought another section in the FAQ could answer this directly. I propose something below and if it's acceptable I'll put in a PR:

Help! I lost my settings/subscriptions/media/everything!

Subscriptions and metadata can be mostly recovered if you have taken any of the steps from 'How do I keep my data when changing phone?', please see the answer there. However if you have not done that your options are more limited:

• Attempt to recover the sqlite database. AntennaPod may have written a file CorruptedDatabaseBackup.db to its app storage directory. There are guides online for how to recover a database. If you succeed in repairing it use the "Import Database" feature under Settings-Storage to reload it.
• You can see the titles of any podcast you recently downloaded in the 'files/media' dir under the app storage dir. From this list you can manually re-add the subscriptions. Any previously downloaded media still present on your device will not be recognised until you re-download an episode. Playback position, history and your queue will remain lost.

What I don't know for sure right now:

• If it is possible to repair the CorruptedDatabaseBackup.db file how can it be used by AntennaPod again? Use the Import Database function? What is stored in the database exactly? What would be recovered?
• If you re-subscribe to podcasts previously lost AntennaPod does not seem to register see the old media it previously downloaded in media dir, episodes have to be re-downloaded. However when you do re-download it adds a small (64kb) file e.g. "ORIGINAL-1.mp3" in the media dir and is then able to play the full episode, presumably from the old 'ORIGINAL.mp3' media file. So it seems the best advice is to leave your old media files in place (if any)? Will those old files be cleaned up eventually even if not re-downloaded?
• Are there any other ways to recover?

Thanks.

From AntennaPod/AntennaPod#1629

<b>Join the AntennaPod community!</b>
AntennaPod is under active development by volunteers. You can contribute too, with code or with comment!

Ask your question or give feedback via Twitter:
https://twitter.com/@AntennaPod

Share your ideas, favorite podcasting moments and gratitude to all the volunteers in our Google group:
https://groups.google.com/forum/#!forum/antennapod

Help translate the app to your mother tongue on Transifex:
https://www.transifex.com/antennapod/antennapod

Check out our Beta Testing programme to get the latest features first:
https://www.github.com/AntennaPod/AntennaPod/wiki/Help-test-AntennaPod

Visit GitHub to submit feature requests, bug reports and code contributions:
https://www.github.com/AntennaPod/AntennaPod

We have a media query for that https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme

I can do it.

When visiting the "about" page, it is highlighted in the menu. When visiting the "blog" site, it isn't. See screenshots below.

According to this.

Short description: pick & add a license for the website's content & code (aside MIT license of 'theme'), and mention it on the website.

Location: License page

Why have this: so (content & code) contributors know what they're committing to

More info:

Short description: The 'Home' item in the documentation breadcrumb links to the current page

URL: e.g. https://antennapod.org/documentation/getting-started

More info:

Short description: Automatically check (in GitHub action) main blog post images for their ratio and size.

Location: Blog

Why have this: We want blog images to have a certain ratio, so that the space in the blog overview is used efficiently, and of high enough quality to display nicely on social media.

More info: We can use ImageMagick's identify through GitHub action. Ratio + minimum size to be determined.

Short description: Mention that in-app cookies are cleared on every app launch.

Location: Privacy

Why have this: It helps people like me understand that cookies not only affect/are used in websites. And informs concerned people what they can do about in-app cookies.

More info: AntennaPod/AntennaPod#5591

The documentation contains a 'Donations' page that says we don't accept donations, while the updated Contribution page now lists our Open Collective.

Short description:
Spice up the most prominent page with the following elements

• #104 Integrate more screenshots in landing page
• #101 Code contributions graph
• #100 'Latest forum posts' list
• #97 Display list of features on homepage

Location:
Homepage

Why have this:
See respective issues

More info:
Mock-up on Penpot

I didn't implement it in the mock-up, but I think we should only display two rows of features by default, and have a 'Show all' button to unhide the other rows.

@ByteHamster What do you think? I indeed opted not to include some of the elements on the homepage I was thinking of first (contributors list, latest version).

Short description:
When I push translations from Weblate, they end up in the translations branch, and an action automatically pushes them to the main branch (recreates affected files there). However, this update on the main branch (pushed by AntennaPod-bot) do not lead to a website rebuild.

URL: n/a

More info:
Here's an example of a commit that I'd expect to lead to website rebuild: 6940c3c

I'm also not sure why we have/there are two actions: Deploy (main.yml) and pages-build-deployment. I guess the former is one we manually specified, the latter one that comes with the GitHub pages settings. I'm wondering if we would still need the former, though.

@ByteHamster, would you have an idea why our bot's pushes are not picked up?

Short description: Display a block with the 5 forum threads most recently updated, with the title, category, and possibly also last activity date (similar to what Discourse displays). Each entry is a link that opens the respective forum thread.

Location: Homepage

Why have this: Show that we have an active community; encourage engagement in that community (so that in the end we have more people helping the project with user support).

More info:

• With a static site, I imagine we want to get this only when a visitor actually might view it, so we should load this block lazily (only when user scrolls down).
• It could be similar to what's visible on Discourse itself (though without the number of posts):
  (forum header below only in the screenshot because Firefox included it and I'm too lazy to crop it off)
  

Short description: Show the top x / a random set of x contributors on the homepage, each with profile picture and username (?)

Location: Homepage

Why have this: Give the project human faces; show that it's volunteer-based, and reward contributors with visibility.

More info:

• I'm not sure whether we should 'sort' contributors based on their number of contributions (which would be tricky, and extra work to come to a fair list), or simply display a random set of contributors. If random, we should probably set some kind of threshold per platform (e.g. 5 PRs or issues on GitHub; trust level 3 on the forum).
• The list should be pulled automatically from GitHub (the two repos; app & website), Transifex (or whatever translations tool we'll have) and the forum. What would be awesome, is if user matching would be done based on username, as to remove duplicates. If we sort based on contributions, people's effort on different platforms are added up (for them to appear higher on the list).
• I wonder if we should also add a 'The core team' page, listing manually selected key people. It'd also give room to list past contributors, such as the original creator and previous maintainers.

Short description: Add a new page dedicated to the 'Translate' task

Location: https://antennapod.org/documentation/

Why have this: Because the direct link to Transifex that we currently have doesn't make much for a soft landing of new/potential contributors.

More info:

• Page contents:
  • That we use Transifex, and links to Transifex support info/tutorial.
  • How the translations process works in general (e.g., how often they get pulled into production).
  • That communication, feedback on source strings and dilemmas are ideally shared discussed on our forum, under the Translations category. (Mention downsides of Transifex, e.g. notifications issue.)
  • What to do if a language coordinator isn't active any-more, or if a suggestion doesn't get accepted (-> chip in on forum).
• As requested on our forum

Short description: A simple graph showing code contributions over time (number of commits per week, over the past 6 months). There should be a call 'Join development' or 'Contribute to AntennaPod' in close proximity.

Location: Homepage, bit further down.

Why have this: Showcase that the project is under active development, and encourage people to contribute, too.

More info:

• Could look similar to the contributor graph on GitHub:
  
• Another layer could be added, indicating the number of contributors during that period (the number of accounts/people that submitted those commits). Though that might make it a bit too complex.
• It would be more interesting (than number of contributors) to have another layer in the graph for the number of strings that were translated (where each language counts as one), to consider & display also forms of contributions other than code.

See kontalk.org and their GitHub repo.

I don't feel super comfortable making changes to the website, as I'm never sure what I'm doing will work or might mess up something. Would it be possible to connect & use Netlify for creating automatic full-site previous of branches and commits? The 'starter' account is free and it seems like it would do the job.
https://www.netlify.com/products/build/

On the botton of the page antennapod.org the link to http://getbootstrap.com/ is missing a "t" and links to http://getboostrap.com/.

Short description:
The direct link to the filtered Issues for the AntennaPod app doesn't match the current label "Type: Confirmed Bug"

URL:
https://antennapod.org/contribute/develop

More info:
Current Link:
https://github.com/AntennaPod/AntennaPod/labels/confirmed%20bug

Proper Link:
https://github.com/AntennaPod/AntennaPod/labels/Type%3A%20Confirmed%20bug

I can try making the changes and link the PR here if I manage to get it working

@mfietz I saw you created a new FAQ page, whilst there already is an FAQ in the wiki. i think your work is a bit better in approach towards content and in presentation, but I don't think it's a good idea to keep two FAQ's (it's more work to keep more versions up to date and confusing for users).
So I'm wondering why you started a new FAQ rather than updating the wiki-one.
Do you think there's a way to put your content in the wiki-page and somehow get it to display in a nicer way? (so that there's only one content-source)

There's no documentation at https://antennapod.org/ which makes it hard to point new users in the right direction. In particular I'm trying to figure out what the expected deletion behaviour is. I often find that if I mark an episode as "Played" it stays in my queue and isnt' downloaded. There are a lot of reasons I might mark something played:

• this particular episode was already broadcast on the radio
• I listened to it in the car on someone else's phone
• it's a re-run
• It's a terrible episode and I don't want to keep thinking maybe I should listen to it
• I listened to the end but the closing credits are so long that Antennapod thinks I didn't finish it.

I don't know what is supposed to happen and I can't find documentation to figure out what should happen so I don't know if it's my settings or a bug or a combination. But I would expect that all completed episodes would be treated the same, whether they're completed because they played to the end or because they played halfway and I marked them played. More clear documentation of the default flow and places where changing settings will impact the default flow would help me make the most of Antennapod.

A friend started using Antennapod at my suggestion and they're also confused/frustrated and I'd like to point them to some documentation instead of walking them through what I do and puzzling it out together.

We currently don't advertise anywhere the RSS feed of the blog/website. Would be good to include it in, e.g., the footer.
Created following this forum question: https://forum.antennapod.org/t/rss-feed-for-the-blog/693

As the title says. When clicking on the menu, nothing happens/appears.

Mozilla set up a very cool system for reporting bugs; a website that asks users to fill in some fields and it'll automatically create a properly-filled bug report on github:
Check live: https://webcompat.com/ -> "report bug"
Github repo: https://github.com/webcompat/web-bugs (MPL v. 2.0 applies)

Short description: A block that showcases one, two or three languages that need translations help. Randomly picked between the languages that have a progression between 50 and 99% (for the App resource).

Location: Homepage

Why have this: Showcase languages that need translations, but aren't in so high need that they're demoralizing, so that the visitor thinks "Ah, let's contribute".

More info: Clicking on the language should open the respective language in a new tab. A 'More info' link should open the new Translate contribute page (#102).

Short description: When hovering the link item (under Share), the purple text bubble 'Link copied!' is shown (even before clicking the icon - and thus without the link actually being copied).

URL: e.g. https://antennapod.org/blog/2020/12/new-website

More info: Issue probably is somewhere here: https://github.com/AntennaPod/antennapod.github.io/blob/master/_includes/share.html

• New features have been introduced which we might include on the website as well.
• Also, the formatting should be redone to look pretty on mobile too.

• Maybe we can make the features clickable to display a small explanation or screen image (HTML5 details element; CSS transitions; Animation.css).

Short description: The action that builds the website has a job using an action that is no longer maintained.

URL: n/a

More info:

Run actions/setup-ruby@v1

NOTE: This action is deprecated and is no longer maintained.
Please, migrate to https://github.com/ruby/setup-ruby, which is being actively maintained.

System info

App version: 2.1.1

App source: Google Play

Android version: 9

Bug description

Steps to reproduce:

1. Go to Settings>Storage>Import/Export.
2. Invoke HTML export.

Expected behaviour:
The exported HTML refers to an image https://antennapod.org/assets/img/antennapod-logo.png
This does not exist (any more).

Current behaviour:

Feature removed from code, but still in many installs. Add a question for now for sth along the lines of 'where did Flattr go?', or leave as is and remove alltogether after some time.
AntennaPod/AntennaPod#3266

Short description: Serve all social media the blog images if available.

Location: Individual blog posts.

Why have this:

More info:

Short description: A page for podcasters where we explain how they can have their funding links show up in AntennaPod (and where it will show up).

Location: Documentation » For podcasters

Why have this: The AntennaPod project stands for an open podcasting system. To ensure its future, podcasters need funding beyond advertising and buy-outs by platforms. With this page we can encourage users to reach out to podcasters, and hopefully increase the uptake of the funding tag and more income for creators.

More info: https://twitter.com/antennapod/status/1476465703481925634

the RSS feed for antennapod.org Blog posts

 https://antennapod.org/rss.xml

has invalid <link> url in <channel> level

<channel>
<title>AntennaPod Blog</title>
<description>AntennaPod Blog posts</description>
<link>https://antennapod.org/blog/</link>

the link contains an invalid closing / after blog

<link>https://antennapod.org/blog/</link>

if you attempt to go to this link you get an error 404 page not found [imgur]

to be valid it would need to be changed to

<link>https://antennapod.org/blog</link>

#2 Removes the previous link to Flattr the app, as the link was broken:

<a href="http://flattr.com/thing/745609"><i class="fa fa-money"></i></a> -

It is possible to create a link to Daniel Oeh's Flattr thing, but I'd propose to register a new organisation to get AntennaPod in the Software section on Flattr and get collective funding.

As noted by @ByteHamster in #21:

Unfortunately, we are currently quite inconsistent about the color. The app needs some updates in that regard, too (different colors in different pages).

Indeed we should, and I can start with correcting the website, but I'd need a hex code. I think we can just go ahead with the shade used in the icon on Google Play. @ByteHamster if you agree, please let me know the hex you used :)

Short description: A page to which we can link to from the contribute page (instead of directly linking to OpenCollective), with three options/suggestions: donate to your favourite creator (deeplink to Stats page if viewing from Android), donate time to AntennaPod (link to contribute page), donate money (link to OpenCollective).

Location: antennapod.org/donate

Why have this: We hardly need money, and already have quite a bit. Podcasters probably need it more than we do. Providing a link to the stats screen is probably the best to make it concrete.

More info: For text inspiration, see this tweet. For code inspiration, probably look at subscribe deeplink.

Short description: Add more screenshots, nicely integrated in the landing page design.

Location: Homepage

Why have this: Make page more lively; show that AntennaPod is available for other form factors as well.

More info: Can be similar to Element:

I just tried out https://antennapod.org/pindakaas, and get the GitHub Pages default 404 page instead of the custom-defined page.

Short description:
Make the website ready for integration in a (semi-automated) translation system.

Location:
Site-wide, except the blog (posts & section-specific interface).

Why have this:
Make the project and use of the app more accessible to audiences not comfortable with English.

More info:
List of components (Weblate) / resources (Pontoon):

• General page texts
• Contribute page texts
• Documentation page texts
• General interface texts

To do list:

• Split pages' MD files into 3 distinct containers w/in _i18n folder: Contribute, Documentation, General
• Transform localised navbar.yml (in _data) to single file with translation refs, include ref'ed items in generic _i18n/en.yml file using {t ...} (however, maybe this isn't possible - see jekyll/jekyll#8783) OR add navbar yml to components list
• Make sure all UI texts in _includes are translatable (added as items to general _i18n/en.yml)
• Make _includes/nav_languages.html use {% for language in data.languages %} (so we don't have to manually add each language there)
• Make Documentation localisable (incl images & breadcrumb links)
• Make date format (on blog landing page) localised
• Make lang-menu use site.languages array instead of site.data.languages array (though take lang name from this other dataset)
• List site code changes to do when adding a language
• Write CI script (GitHub action)

Short description: Critically review & possibly update the instructions in the documentation for users whose database was wiped.

Location: https://antennapod.org/documentation/bugs-first-aid/database-error

Why have this: Instructions were based on tips for older AntennaPod versions. Also discovered via the forum DB Browser for SQLite which we might want to mention on the website.

More info: user complaining their attempts didn't work

For now, it would be nice to get some information on page visits. In future, when we might expand the website to include a basic knowledge base, it would be nice to get info on that as well. Also, as we might be able to check which features get most attention when we make them 'clickable' (see #4).

Open source options: https://opensource.com/business/14/10/top-3-open-source-alternatives-google-analytics

Short description:
The proxy dialog is rather complex. For privacy sensitive users, it would be great to have a simple explanation about how to connect via TOR.

Location:

Documentation

Why have this:

More info:

Proxy screen -> SOCKS, "localhost"/"127.0.0.1", Port 9050

Short description: A feature list that describes what AntennaPod is (project characteristics) and can do (technical functionality). Main features should be visible on the homepage, a full list on a dedicated features page.

Location: Homepage and a dedicated 'Features' page.

Why have this: To showcase to potential new users/contributors that AntennaPod really is a cool product!

More info:

• 'Features' I think should include both technical features (functionality) and characteristics (e.g. respectful of your privacy)
• Each feature should be a title, and optionally a graphic or icon. When clicking on it, it should display a short description (1-2 sentences), with a 'more info' link if there's a relevant entry in our documentation.
• The 'chips' to represent features could be similar to the ones used for blog posts (varying in height).
• It'd be great if we could create a collection, with one md file per feature.
• We should be able to indicate a priority, where only the top 7 (?) appear on the homepage.
• We used to have a feature list on the previous homepage :-)

Short description: Replace page-level permalink definitions with global 'pretty' permalink.

URL: review all MD files

More info:
Add to _config.yml, move existing permalink definition to documentation collection:

permalink: pretty

#112 (comment)

Short description: The breadcrumbs are not translated.

URL: e.g. https://deploy-preview-135--antennapod-test.netlify.app/fr/documentation/getting-started/subscribe

More info: As mentioned on the forum

Short description: Have a small block displaying the "Latest release" version name & release date and a "What's new" block displaying that version's 'What's new' info (as visible on Google Play and F-Droid). They should probably be visually connected (or a whole), and be updated automatically (without extra intervention for each new release).

Location: Homepage

Why have this: Show that AntennaPod is in active development; encourage visitors to download the app.

More info:

• We could either create a dynamic section or maybe (don't know if this is possible) from the app's (GitHub) Actions set something in motion that updates the static website?
• The 'What's new' section could either display the text capped, with a 'read more' button that expands the block (if this whole thing is presented further down on the page, where it can take more space), or just display the version & date with a 'View what's new' button/link (if this whole thing is displayed prominently above the fold, where we want to keep the view clean).
• displaying the latest release version (date + version number) and a 'what's new' block