Based on planning in https://github.com/mozilla/foundation.mozilla.org/issues/4090 and our deck.
Create an IA proposal using the analytics and recommendations in https://github.com/mozilla/foundation.mozilla.org/issues/4113. Please adapt the IA as results of the stakeholder interviews https://github.com/mozilla/foundation.mozilla.org/issues/4156 and the audience interviews https://github.com/mozilla/foundation.mozilla.org/issues/4114.
Here are four _slightly_ different proposed IA drafts: https://redpen.io/p/wd83cac5211b178ff0
The files are also merged into our Foundation Site file on Abstract.
I think we need to change our page titles for sure. This is inline with the insight of using more accessible (simple > complex) language we derived from both analytics and our audience interviews. I've put in basic placeholders for now that get at the function of the page (e.g. Work, About, Mission, etc) but we'll need to finesse these.
Aside from that from looking at benchmarks it seems like Foundation websites all follow a similar structure:
Aside from renaming "Internet Health" to something like "Our Mission", which is more clear, we should consider how to weave that content into "How We Work", currently our Initiatives page. I think this will help further explain our complex work to people.
We should also add our Blog to the global navigation since it contains a lot of our most up to date and popular content. This is in line with the insight to make it easier to navigate to /campaigns and /blog since this content is well received. We could name it "News" or something or other that captures the freshness of the content.
I also think since we have two branches of work (staff run and our Grant programs), it would be a good idea to separate the two to help people understand what we do. This is supported from the insight and data we gathered about how people see Fellowship and Awards as one unit.
Thank you so much for the drafts! It so helpful for me to see this and it really helps ground all the things we've been talking about. Having this will really help guide our conversations.
Also, thank you for providing the rational behind your recommendations. I enjoyed your summary of the patterns you noticed from benchmarking. Could you please add them to the benchmarking ticket https://github.com/mozilla/foundation.mozilla.org/issues/4198 as well?
@taisdesouzalessa @beccaklam let's spend some time talking through this next week and then maybe pause on it while the rest of the stakeholder research comes in.
Great work on that, Becca! Really liked the summary from the benchmarks as well.
Looking forward to talk with you both about those next week!
Follow up work can be done here - IA: revised draft based on data & stakeholder interviews #4244. So this ticket is probably good to close!
@kristinashu @taisdesouzalessa Going to close the ticket then. If you need to reopen for whatever reason, feel free!
Most helpful comment
Thank you so much for the drafts! It so helpful for me to see this and it really helps ground all the things we've been talking about. Having this will really help guide our conversations.
Also, thank you for providing the rational behind your recommendations. I enjoyed your summary of the patterns you noticed from benchmarking. Could you please add them to the benchmarking ticket https://github.com/mozilla/foundation.mozilla.org/issues/4198 as well?
@taisdesouzalessa @beccaklam let's spend some time talking through this next week and then maybe pause on it while the rest of the stakeholder research comes in.