It's possible to set the Terms of Service for an Akkoma instance in the AdminFE dashboard, under Settings -> Other -> Terms of Service. It would be really nice if a page on our instance could automatically default to that.
Why
Prior to installing the frontend, we had configured a detailed Terms of Service in the admin section. It showed up perfectly with Pleroma FE, but turned into a blank page when we enabled Mangane.
Due to our current hosting arrangement, we are not able to use the custom page functionality in Mangane, as we are using a managed service.
How
One way to handle this might be to automatically generate a Terms of Service page at a predefined route, if the Terms of Service field is already filled out. Maybe Mangane could check to see if that field has any data, then generate a route at /about/terms?
Another approach may be to add a Terms of Service section into Mangane's Admin interface directly, allowing admins to easily set those details for their communities with little effort.
What
It's possible to set the Terms of Service for an Akkoma instance in the AdminFE dashboard, under Settings -> Other -> Terms of Service. It would be really nice if a page on our instance could automatically default to that.
Why
Prior to installing the frontend, we had configured a detailed Terms of Service in the admin section. It showed up perfectly with Pleroma FE, but turned into a blank page when we enabled Mangane.
Due to our current hosting arrangement, we are not able to use the custom page functionality in Mangane, as we are using a managed service.
How
One way to handle this might be to automatically generate a Terms of Service page at a predefined route, if the Terms of Service field is already filled out. Maybe Mangane could check to see if that field has any data, then generate a route at /about/terms?
Another approach may be to add a Terms of Service section into Mangane's Admin interface directly, allowing admins to easily set those details for their communities with little effort.