Steffen D. Sommer

Either by - Passing a config - Passing in the values (e.g. perPage etc.)

Make tests for v 2.0 (Vapor 3)

Consider splitting the package into multiple targets similar to https://github.com/vapor-community/vapor-ext/blob/master/Package.swift

We should have a package that gives you all related helpers/mocks/stubs when testing Vapor projects.

auditEvents vs actions

1

It seems like `Action` is a leftover from before we integrated/made the `Audit` package. Go through codebase and see if we can remove `Action` (e.g. check how recent activities works...

Title missing

1

It seems like the title () is missing on some pages.

Look at UX/UI

1

Go through the package and consider if it's good enough from a UX/UI standpoint.

Let's get a project deployed using the package where we can show all the different leaf tags that are currently implemented

See https://github.com/nodes-vapor/paginator/issues/49 for details

Make API documentation throughout the code base.