Bloom is Exygy’s affordable housing platform. Bloom's goal is to be a single entry point for affordable housing seekers and a hub for application and listing management for developers.
Questions are frequently asked on what fields are required when creating, editing, or publishing listings and applications. And if they are different for different jurisdictions. Can we compile that and document it in an accessible place.
Document should include:
Required fields for creating a draft listing
Required fields for publishing a listing
What conditional fields are required for certain scenarios
Required fields for submitting an application via the public site
Required fields for submitting an application via the partner site
For both Listings and Applications which fields are only required for certain Jurisdictions
Nice to have: all fields that are unique to certain jurisdictions (e.g this field only exists in Doorway)
The same thing goes for permissioning and allowable actions by permission level across jurisdictions. Can we compile that and document it in an accessible place.
Document should include:
For each action on the partner site who is eligible to do it.
For each action is the limitation a frontend or backend restriction (If you hit the backend directly would you be able to do something but we prevent it from happening via the frontend)
What divergences on permissioning are there between jurisdictions
sarahlazarich
commented
2 weeks ago
Questions are frequently asked on what fields are required when creating, editing, or publishing listings and applications. And if they are different for different jurisdictions. Can we compile that and document it in an accessible place.
Document should include:
The same thing goes for permissioning and allowable actions by permission level across jurisdictions. Can we compile that and document it in an accessible place.
Document should include: