The v1 of the Dungeon Master API will expand on the front-end POC that was created with Rage Shipper. The implementation will require migrating data from Airtable to a standalone (Postgres) database that will be accessible via API endpoints within Sentry bot (prev Guild Keeper). These will be protected with (web3) signature-based auth.
The frontend will incorporate the design outcomes from the Season 1 design/UX sprint and any feedback from the updated RG style guide for this initial version. If, based on the design, scope expands beyond the initial API outlined then we'll submit an additional proposal or keep scope to the current set of endpoints for this iteration. The frontend will also leverage signature-based authentication to ensure only members (& apprentices, probably) have access to the underlying data. Signatures could be cached and stored locally to prevent the user from having to sign for every request/update.
Why should we build this?
Based on the feedback from Rage Shipper and the initial workings on the Season 1 Job Board project there will be a lot of value by continuing this implementation and migration. The cost will be well worth it in efficiencies gained at multiple levels of the organization.
Clerics will have a better view into Raiders available. Raiders will have a better view into Raids & RIPs available. New members will be able to quickly learn from the historical context of past raids & RIPs and find potential mentors.
Anything else you'd like to add?
This will serve as a foundational hub for other ancillary (Dungeon Master) projects to be incorporated into or extended with the feeling of being the same application.
This API will also receive new consultation requests from Hire Us & new member applications from Join Us.
Project Submitted by
@Saimano, @bitbeckers, @jonathanprozzi, @DamagedGoods, @scottrepreneur
Summary
The v1 of the Dungeon Master API will expand on the front-end POC that was created with Rage Shipper. The implementation will require migrating data from Airtable to a standalone (Postgres) database that will be accessible via API endpoints within Sentry bot (prev Guild Keeper). These will be protected with (web3) signature-based auth.
The frontend will incorporate the design outcomes from the Season 1 design/UX sprint and any feedback from the updated RG style guide for this initial version. If, based on the design, scope expands beyond the initial API outlined then we'll submit an additional proposal or keep scope to the current set of endpoints for this iteration. The frontend will also leverage signature-based authentication to ensure only members (& apprentices, probably) have access to the underlying data. Signatures could be cached and stored locally to prevent the user from having to sign for every request/update.
Why should we build this?
Based on the feedback from Rage Shipper and the initial workings on the Season 1 Job Board project there will be a lot of value by continuing this implementation and migration. The cost will be well worth it in efficiencies gained at multiple levels of the organization.
Clerics will have a better view into Raiders available. Raiders will have a better view into Raids & RIPs available. New members will be able to quickly learn from the historical context of past raids & RIPs and find potential mentors.
Anything else you'd like to add?
This will serve as a foundational hub for other ancillary (Dungeon Master) projects to be incorporated into or extended with the feeling of being the same application.
This API will also receive new consultation requests from Hire Us & new member applications from Join Us.
Raid Party skills needed
Cost (in Dai)
~ 6000 Dai