One part of the project that we'll have to implment right after the runner management by admins is the runner selfservice.
What runner selfservice?
We need a registration self service (registration form) for company runners (register for a company w/ a special link) an runners from the public (register with email confirmation.
This selfservice should also include a "about me" page, where the runner can view his registration status (and maybe later his distance, donations etc).
One part of the project that we'll have to implment right after the runner management by admins is the runner selfservice.
What runner selfservice?
We need a registration self service (registration form) for company runners (register for a company w/ a special link) an runners from the public (register with email confirmation.
This selfservice should also include a "about me" page, where the runner can view his registration status (and maybe later his distance, donations etc).
My first idea for this would be the following api endpoints:
/runners/register -> Register as a runner
/runners/register/:jwt -> Register as a runner for a company
/runners/me/:jwt -> View information about your registration
The specifics can of course vary - it's just my first idea for this.
My first idea for this would be the following api endpoints:
/runners/register -> Register as a runner
/runners/register/:jwt -> Register as a runner for a company
/runners/me/:jwt -> View information about your registration
The specifics can of course vary - it's just my first idea for this.
The registration is implemented.
I'd reccomend starting planning and development on the selfservice frontend eary febraury after lfk/frontend has a first production-ready release.
The registration is implemented.
I'd reccomend starting planning and development on the selfservice frontend eary febraury after lfk/frontend has a first production-ready release.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
One part of the project that we'll have to implment right after the runner management by admins is the runner selfservice.
What runner selfservice?
We need a registration self service (registration form) for company runners (register for a company w/ a special link) an runners from the public (register with email confirmation.
This selfservice should also include a "about me" page, where the runner can view his registration status (and maybe later his distance, donations etc).
My first idea for this would be the following api endpoints:
/runners/register -> Register as a runner
/runners/register/:jwt -> Register as a runner for a company
/runners/me/:jwt -> View information about your registration
The specifics can of course vary - it's just my first idea for this.
The registration is implemented.
I'd reccomend starting planning and development on the selfservice frontend eary febraury after lfk/frontend has a first production-ready release.
Selfservice-UI is implemented over here: https://git.odit.services/lfk/selfservice