@roger and I would love some support from you all as we finalize a code evaluation for our path analysis with FNS. We have about a 10 days to get this in tip top shape. A lot of the content is there as is the vision. We'd like help with flow and readability. Here's the link.
I just spoke with @Coreycaitlin about this - a few things as per our conversation:
we're up for starting by having a conversation with you all to scope this out;
we're happy to pair in the beginning - Corey had mentioned that this can be a helpful way to get a content person clearer about what we need and we're up for it;
sadly we have very limited hours. Let's begin by setting the cap at 5 hours.
note that depending on resources, we'll also see if we can get a pair of eyes on our final recommendations doc.
@roger and I would love some support from you all as we finalize a code evaluation for our path analysis with FNS. We have about a 10 days to get this in tip top shape. A lot of the content is there as is the vision. We'd like help with flow and readability. Here's the link.
I just spoke with @Coreycaitlin about this - a few things as per our conversation:
Thanks!
Tock #782