Getting started

Documentation for LAUTI - Open Source Community Calendar#

This documentation covers all kind of users interacting with LAUTI. We identified 5 groups so far, and structured the documentation accordingly.

Visitors#

For the lack of a better term, we named people who are looking for events and therefore browsing a LAUTI instance visitors. They do not have a registered account with the instance, and therefore cannot log in. Their use case is gathering information about an event, group or place in their community.

To the Visitor’s guide

Users#

Users are people with a user account on a LAUTI instance. They use LAUTI to publish events, groups or places. This would e.g. a local community center, activists or a foodsharing group. Their account type on LAUTI is user which they created by receiving an invitation link. They can only modify or delete their own events.

To the Users’s guide

Moderators#

Moderators are monitoring all activity on the instance from a social perspective. E.g. if the posted events are conform to the instances rules, or if users made an obvious mistake with something. They also might create events on their own, but they have the possibility to modify or delete all other content. Their account type is moderator.

To the Moderator’s guide

Admins#

Admins are the people setting up LAUTI on a server and maintaining it from a technical point of view. They have all rights to do modifications to the instance, from a technical point as well as for content moderation. Their account type is admin.

LAUTI is a self-hostable community calendar. There is no flagship instance where you just put in your events, as we want to promote community driven projects. If your community does not have the technical skills to host your own instance, we would recommend you reach out to your wider community. Maybe there is a collective in your area with the ability to do the hosting for you.

To the Admin’s guide

Contributors#

Contributors are people wanting to support LAUTI by putting in all kinds of work. This can start with filing bug reports, feature requests, adding translations, writing documentation or contribution source code for bugs or new features. We welcome all forms of contributions and are grateful for them. To make it easier for people to contribute and the work product can be used, we provide some guidelines.

To the Contributors’s guide