Benjamin Hättasch authored 1 year ago and Nadja Geisler committed 1 year ago

This way, the frontend views will be used when AKSubmission is installed and active, or otherwise the link to the built-in AK edit form in backend
This reduces the coupling between AKSubmission and other apps that previously needed that app
Use that new property in all places where previously an URL to the submission view was used (for consistency and to allow changes in one place in AKSubmission, too)
This implements #166

Add compressor and sass compiler dependencies
Introduce corresponding settings
Use compressor in templates
Move only partially used dependencies to higher level for better re-usability
Add custom tags to create css and js for fontawesome separately
This implements the first part of #162

Use official fontawesome django app for static file handling
Switch to fork/new version of django-bootstrap (for icon field and rendering shortcuts)
Add migration to bump icon field of dashboard buttons to new version
Update templates to load new app and use new tags

Bump django-bootstrap to version 5
Exchange bootstrap files (js & css)
Adapt settings
Migrate to new version/resolve breaking changes
Move layout adaptions previously included in bootstrap.css into custom.css

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This implements #180

Introduce framework to simply test correct rendering of views
Create tests for dashboard views
Create tests for plan views
Create tests for default admin views (add and change) of AKModel models

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Only store AK in database once all attributes are correctly set.
Previously, each AK was automatically edited directly after saving to add the link, which created two history entries for that AK.
This resolves #141.
Additionally, only display slots as (re-)scheduled when they are indeed scheduled (i.e., have a starting time stamp).

adds datetimefield for start to Event model
adds datetimefield for start to Event model
adds translations
adds migration

The wizard is used instead of the normal built-in creation workflow
It consists of multiple steps to specify the most fundamental settings (especially the timezone), further settings, copying AKCategories and AKRequirements from existing events and activating the event once the basic configuration is done
The steps after the creation (first two steps) can be skipped

Benjamin Hättasch authored 4 years ago and Nadja Geisler committed 4 years ago

Implements #72
Adapt dashboard layout to show feed
Add logic to get a list of recent changes
Add link to dashboard detail view on start page
Introduce settings to disable and control feed
Add translation

Benjamin Hättasch authored 4 years ago and Nadja Geisler committed 4 years ago

Add boolean flag to events whether they should appear on the overview/start page or just when visiting the correct url

Closes #60
Add boolean flag to event
Hide plan for non-staff users when flag is set
Update translations

Closes #74

Use tabbed-view for ak list, too
Reduce code duplication between submission overview and ak list
Cleanup filtering in view
Display message when (filtered) AK list is empty
Remove submission button from dashboard when event is inactive
Closes #70

Hide wall (hide button in plan, redirect when calling directly)
Show message on normal plan & hide current and next AKs
Link only a single schedule view in Dashboard but not current AKs and wall
Update translations

adjust other buttons
re-generate translations

Adapt dashboard links to new URL structure of plan
Introduce conditional loading of paths to central URL file

fix typo

Introduce model
Introduce admin interface
Show buttons on dashboard start page

Add little space between the buttons

deploy dashboard under /
create template view
provide template with important links for each event
handle case of no events
create template tag to ensure installed apps