Rework "branding" to ease third-part deployment

ecosyste-ms / roadmap

Planning and roadmap for future Ecosyste.ms development

GNU Affero General Public License v3.0

9 stars 1 forks source link

Rework "branding" to ease third-part deployment #10

Open bzg opened 9 months ago

bzg commented 9 months ago

In the scenario where someone or an institution would want to deploy ecosyste.ms, e.g. to track metadata on specific forges, it should be obvious that the new instance is not "ecosyste.ms" but a separate deployment.

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

andrew commented 9 months ago

@bzg would this be a small branding change like, the title, some custom css styles or a whole extra html section?

bzg commented 9 months ago

Yes, just a small branding change. And we would refer and link to the main https://ecosyste.ms instance and encourage potential reusers and contributors to check the flagship instance.

bzg commented 7 months ago

I'm adding @simkim to this issue. Here is a preliminary list of desired changes:

[ ] Allow to adapt the frontpage text
[ ] Allow to use a custom css for the main page (the equivalent of https://ecosyste.ms)
[ ] Allow to adapt the footer (e.g. to remove the links to blog and status)
[ ] Allow to properly credit/link ecosyste.ms as the upstream project