{% extends "site_base.html" %} {% load i18n %} {% block head_title %}{% trans "Welcome" %}{% endblock %} {% block tab_id %}id="home_tab"{% endblock %} {% block body %} {% blocktrans %}

django-schedule

{% endblocktrans %} {% blocktrans %}

This project is a scheduling app. At its core are events that constitute a start and end date implemented via two DateTimeFields together with a some meta datax such as title, description, etc.

To make it more user friendly there is the idea of EventRelation which links generic objects and an Event object. The idea is that you will keep more information about the event in these relations such as who is authorized to view them. It could be the case that User is linked to Event to represent who is authorized to view the event, and also User is linked to event to represent who is attending the event.

The EventRelation has another field called distinction. So in the previous example we could add an EventRelation which links a User to an Event with the distinction "viewer" and another EventRelation which links a User to an Event with the distinction "attendee."

{% endblocktrans %} {% blocktrans %}

Want to see it in action?

{% endblocktrans %} {% blocktrans %}

The sample project come with two management commands that enable you to load some data:

./manage.py load_sample_data

./manage.py load_example_data

{% endblocktrans %}

{% trans "The list of available Calendars." %}


{% blocktrans %}

Core developers

Contributors (in alphabetical order)

{% endblocktrans %} {% endblock %}