If your view is event-specific, you have to name one parameter in your URL
event. By convention, all plugin URLs except for backend URLs start with
a /p/ to avoid namespace collisions with event names and reserved URLs.

You can then write a regular view. Our middleware will automatically detect the
/orga/ subpath and will ensure the following points if this is an URL with
the event parameter:

The user has logged in

The request.event attribute contains the current event

The user has permission to view the current event

If you want to require specific permission types, we provide you with a decorator or a mixin for
your views:

Frontend views work pretty much like organiser area views. Take care that your URL starts
with /(P?P<event>[\]+)/, or even better, /(P?P<event>[\]+)/p/.
You can then write a regular view. It will be automatically ensured that:

The requested event exists

The requested event is visible (either by being public, or if an organiser looks at it)