add topic/sup-topic/resource menus

[timothyfcook]

Per Chelsea's design.

[cameronscott137]

First draft here: saxifrage/cityasacampus@359bd85

All static right now. Will need an eventual assist from @whit537 to make those dynamic.

[timothyfcook]

Nice. On our way!

Note Chelsea's design has the top menu boxes aligned on-center, not top-aligned.

[timothyfcook]

Also:

• There is also a subtle gray line that runs between the centers.
• The third box is incrementally smaller than the others

[cameronscott137]

Added in the subtle grey line.

@chelseaerdner and I just had a conversation your other points:

Hierarchically, shrinking each navigation box makes sense, but the result is that the third box—arguably the most important when its visible—is also the smallest, which is counter-intuitive.

In addition, if any headline breaks to two lines, it will be impossible to maintain that centered alignment. Given that this will ultimately utilize user-submitted content, we won't have control over text length (see screenshot).

Chelsea and I came to the conclusion the subtle grey line and the left-to-right order will be enough to convey progression and hierarchy. Thoughts?

[timothyfcook]

Looks good. We'll leave this issue open until we can make them dynamic.

[chadwhitacre]

As of saxifrage/cityasacampus#181 we now have a pretty nice data structure for the topics, subtopics, and resources. It's at Map.topics, and there's some light documentation on the (Python) function that generates it.

[chadwhitacre]

However, what Map.topics doesn't provide is ordering. We do have ordering info for the resources in Map.topics[topic_id].subtopics[subtopic_id].dag, but a) we also need it for subtopics within each topic, and for the top-level topics, and b) an Array would be an easier API to traverse than a DAG. For #61 I'm planning to add ordering information re: resources at the Python (caac-map) level, so it wouldn't be that much work to also implement topic and subtopic ordering at that level as well, so that resources.json (which, now that I type this, probably wants to be topics.json since it's what ends up at Map.topics) perhaps includes an order key where we keep that info.

[chadwhitacre]

I'll see if I can take the topic ordering from the order of the worksheets in the Google Sheet. How should we manage the ordering of the subtopics? Order mentioned in the sheet? Explicitly defined elsewhere?

[chadwhitacre]

"Alphabetical is rarely the best sort order." —Tufte