Skip to content

Add blog post on Weblate sponsorship#517

Open
loucasal wants to merge 9 commits into
AntennaPod:masterfrom
loucasal:blog-weblate
Open

Add blog post on Weblate sponsorship#517
loucasal wants to merge 9 commits into
AntennaPod:masterfrom
loucasal:blog-weblate

Conversation

@loucasal

@loucasal loucasal commented Jun 6, 2026

Copy link
Copy Markdown
Contributor

As requested by @keunes at https://forum.antennapod.org/t/blog-post-about-the-weblate-changes-we-sponsored/8614.

Tentatively dated a week from now, to allow time for review.

Edit: not quite sure why the image is not being displayed.

@keunes

keunes commented Jun 8, 2026

Copy link
Copy Markdown
Member

Edit: not quite sure why the image is not being displayed.

Might have something to do with #497?

@ByteHamster

Copy link
Copy Markdown
Member

The recent website rewrite added a script that generates image thumbnails. I think you need to run it

@loucasal

loucasal commented Jun 8, 2026

Copy link
Copy Markdown
Contributor Author

I'm missing multiple packages and package managers to be able to run it, maybe better if someone can run it and push the missing thumbnail?

@ByteHamster ByteHamster left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks! Ready to merge @keunes @loucasal?

@loucasal

Copy link
Copy Markdown
Contributor Author

Thank you! Good to go for me.

@keunes keunes left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for preparing the draft!

I like the start and end but I must say that, while I suggested to go with a bullet-point list - I find that part hard to follow and not too informative.

Maybe we should replace the bullet points with headings and short explanations:

Image

Sections could be:

  • Flexible and inherited settings (key point: moving away from mdpo plugin, simpler flow, fewer settings)
  • Smarter permissions (here I wouldn't mind a note on how they implemented this in the UX - it's really quite convenient.)
  • Other (comment API & how we decided not to use it in the end; Translate button on category landing pages)

Would you be up for making such tweaks @loucasal? If not, I can spend some time.

Either way, thanks again for your help! :-)

---

{: .lead}
As an open-source project, AntennaPod doesn't exist in a vacuum. We rely on a wider ecosystem of open-source tools to keep our project running smoothly. And as many of you know, an important piece of our infrastructure is Weblate, the platform where our global community [translates](https://antennapod.org/contribute/translate) AntennaPod into over 40 languages.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure many of our blog readers know we use Weblate for translations (?)

Comment thread _blog/2026-06-13-weblate.md Outdated
Comment thread _blog/2026-06-13-weblate.md Outdated
Comment thread _blog/2026-06-13-weblate.md Outdated
Comment thread _blog/2026-06-13-weblate.md Outdated
- *[Some component settings should be settable on the project and inherited](https://github.com/WeblateOrg/weblate/issues/10897#issuecomment-3831241112)*, which also addressed our need for a *[Contributor agreement at project level](https://github.com/WeblateOrg/weblate/issues/14231)*
- *[Allow setting language permission at user level](https://github.com/weblateOrg/weblate/issues/14233)*
- *[Enable add-ons at category level](https://github.com/weblateOrg/weblate/issues/17858)*
- *[‘Translate’ button at category landing page](https://github.com/weblateOrg/weblate/issues/11198)*, which also addressed our need to *[Add multiple Markdown files (or folder) as single component](https://github.com/WeblateOrg/weblate/issues/14237)*. This was not implemented as such, but instead the languages page now opens by default when opening a category, i.e. a group of components.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should inverse this: start with what we sponsored and then how this fixed the problem for our initial proposal.

Comment thread _blog/2026-06-13-weblate.md Outdated
Comment thread _blog/2026-06-13-weblate.md Outdated
loucasal and others added 6 commits June 14, 2026 08:30
Co-authored-by: Keunes <11229646+keunes@users.noreply.github.com>
Co-authored-by: Keunes <11229646+keunes@users.noreply.github.com>
Co-authored-by: Keunes <11229646+keunes@users.noreply.github.com>
Co-authored-by: Keunes <11229646+keunes@users.noreply.github.com>
Co-authored-by: Keunes <11229646+keunes@users.noreply.github.com>
Co-authored-by: Keunes <11229646+keunes@users.noreply.github.com>
@loucasal

Copy link
Copy Markdown
Contributor Author

Would you be up for making such tweaks @loucasal? If not, I can spend some time.

I've applied your suggestions, but it will be more efficient if you do the remaining tweaks - after all, you are much more familiar with what was done and why than I am. :)

Happy to give it a final proofread when ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants