search

hestiaAI / hestialabs-experiences

HestiaLabs Data Experiences & Digipower Academy
https://digipower.academy
Other
7 stars 1 forks source link

Decide what part of the footer is optional #922

Closed andreaskundig closed 2 years ago

andreaskundig commented 2 years ago

The footer currently has a lot of links to hestia, sitra, migros...

A client might not want any of this. Do we make all of it configurable ? It could be just one field in the translation file that allows html. Do we want to have a mandatory link to hestia.ai or hestialabs.org ?

alexbfree commented 2 years ago

I suspect we may need to keep at least some credit to migros and/or sitra for original dev funding, see what @pdehaye says

alexbfree commented 2 years ago

Need to decide what we suggest to UFC - @pdehaye to decide and ask them (e.g. lose sitra, keep hestia?)

pdehaye commented 2 years ago

We don't name clients on the public repos.

alexbfree commented 2 years ago

Need a clear statement of what should be kept + removed on what deployments.

pdehaye commented 2 years ago

I don't know, this will be driven by client(s), probably very last minute unfortunately as dependent on their schedule and readiness. Tagging @andreaskundig so he can flag it early too.

alexbfree commented 2 years ago

Andreas reports this is waiting on UFC. At which point we might add more options for footer configuration.

fquellec commented 2 years ago

Closing as modularization will not cover footer, if requirements change reopen.