Open sadlerw opened 7 years ago
This story is intended to be more back end focused. To allow a FS employee to upload or otherwise update their forest specific information.
Should this be a page about Forest specific alerts that can be updated as needed? If so, we may not need #7. Need to follow up w/ @JaneZC and @bryanmcfadden
This should also include the FS administrator's ability to update the Forest's contact information.
Menu Items and sections likely to need to be updated by FS Administrators:
I'm going to summarize an approach that @ASprinkle @MelissaBraxton @lauraGgit and I agreed upon earlier today.
There are quite a few unknowns related to this story—we have a hypothesis about what content FS Admins will want to edit (see the comment directly above), but it's not confirmed, and we don't know how often they'll edit, or other information pertinent to design decisions. There are also some dependencies, including building out user auth management tools.
So, rather than build out CMS-like functionality now, we'd like to pursue a more lightweight approach where we ask FS Admins to submit a form (could be a google form, or something else) when they want to make updates to the site. The actual updates will need to be handled manually, and we'll need to design a communication process to keep the original requester updated.
While this process will create a delay between when the FS Admin wants to make a change and when the change actually happens, this is likely outweighed by the benefits—we'll learn a great deal before investing design and dev time in developing features.
Let's discuss at a backlog grooming meeting, including what tasks will be required to implement this approach.
Notes
location information, delete/update/add species information
Acceptance criteria