<aside> 📌 I'm building a Grant Proposal Language Library web app. This page is one installment of my weekly updates, which I have no doubt you will find to be riveting and insightful. And if you don't know what I'm talking about or what this is, you can read about what I'm building and why over here.

</aside>

Week 3: Data Structure

April 27-May 3

This part of building something is harrrrrrrd.

Even for someone like me who loves organizing things, woof. There are just so many ways to do something. And you have to think about how the thing might grow and account for those possibilities. If you do it wrong, you could really fuck yourself down the road. Stressful.

How I went about it...

Step 1: Visualize

First, I mapped out the grant writing process visually, to make sure I was capturing all the data types I'd need to build out the system. Each color represents a different thing that would need to be created on the back end.

I also needed to think through the different ways someone might navigate through the app. I wrote about these in Week 2, so I won't bore you with the details again. But here's the basics (colors correspond to the stuff above):

Finally, I needed to ****think about different types of users. Right now it's built for freelance grant writers or grant writing agencies who work with multiple nonprofit clients. But I'd also want it to be usable by nonprofits themselves, as an internal tool. In which case, the concept of a "client" in the system would need to be invisible or gone altogether.