Add an option to display local timeline on homepage by default #617

New issue

Open

opened 2019-06-16 13:56:51 +00:00 by EliotBerriot · 1 comment

EliotBerriot commented

2019-06-16 13:56:51 +00:00

(Migrated from github.com)

Is your feature request related to a problem? Please describe.

When you use Plume as a regular blog engine, and don't really care about the discovery part, it's annoying to have the federated timeline showed as the default.

Consider https://blog.funkwhale.audio/: it's mainly used for announcements about Funkwhale releases, yet I cannot simply link our audience to https://blog.funkwhale.audio/, because it shows completely unrelevant entries (in multiple languages, absolutely unrelated to Funkwhale, etc.)

My current workaround is to always link to https://blog.funkwhale.audio/local, but this is far from perfect: if users click the home button, they will land on the homepage anyway, and people searching for funkwhale blog on search engines will still arrive here.

Describe the solution you'd like

I'd like an option to promote the local feed of my Plume instance on the landing page, instead of the federated one. The most basic option I can imagine is an environment variable, like HOMEPAGE_CONTENT={all|local}, with all being the default (current behaviour).

Setting HOMEPAGE_CONTENT=local would display only local content in the homepage, which I suspect is only a matter of adding proper if blocks in the homepage template.

This isn't required to solve this ticket, but we could also imagine supportingg more complex customization using that variable. E.g. specifying HOMEPAGE_CONTENT=local,federated would display the local and federated blocks, in that order. I think it would give an easy option to display the federated feeds, without being annoying to instance owners who want to show their own blogs first :)

**Is your feature request related to a problem? Please describe.** When you use Plume as a regular blog engine, and don't really care about the discovery part, it's annoying to have the federated timeline showed as the default. Consider https://blog.funkwhale.audio/: it's mainly used for announcements about Funkwhale releases, yet I cannot simply link our audience to https://blog.funkwhale.audio/, because it shows completely unrelevant entries (in multiple languages, absolutely unrelated to Funkwhale, etc.) My current workaround is to always link to https://blog.funkwhale.audio/local, but this is far from perfect: if users click the home button, they will land on the homepage anyway, and people searching for `funkwhale blog` on search engines will still arrive here. **Describe the solution you'd like** I'd like an option to promote the local feed of my Plume instance on the landing page, instead of the federated one. The most basic option I can imagine is an environment variable, like `HOMEPAGE_CONTENT={all|local}`, with `all` being the default (current behaviour). Setting `HOMEPAGE_CONTENT=local` would display only local content in the homepage, which I suspect is only a matter of adding proper `if` blocks in the homepage template. This isn't required to solve this ticket, but we could also imagine supportingg more complex customization using that variable. E.g. specifying `HOMEPAGE_CONTENT=local,federated` would display the local and federated blocks, *in that order*. I think it would give an easy option to display the federated feeds, without being annoying to instance owners who want to show their own blogs first :)

👍 2

EliotBerriot commented

2019-06-16 14:03:55 +00:00

(Migrated from github.com)

Possibly linked to https://github.com/Plume-org/Plume/issues/450, and closable when Generic Timelines are implemented :)