search

crkn-rcdr / Access-Platform

Documentation, specifications, and APIs for the Canadiana Access Platform.
https://www.canadiana.ca/
2 stars 0 forks source link

Admin tool universal layout #120

Closed SaschaAdler closed 3 years ago

SaschaAdler commented 3 years ago

What do we need to make available to users from every route? Sapindale has a title (which acts as a "home" link) and something telling you who's logged in, which I've recreated in slightly broken fashion. What else should we add? Answering this question might require some analysis of how the admin tools get used once they can do things.

jjfriedman commented 3 years ago

@SaschaAdler Would it be helpful to have a brainstorming session with the staff who will be using the tools? Or is this more from a platform perspective?

SaschaAdler commented 3 years ago

@jjfriedman I think a brainstorming session would be useful, but it might be best to wait until there are some tools to experiment with before figuring out what to change about them.

We're making progress on that front, at least!

jjfriedman commented 3 years ago

Great, and that makes sense!

SaschaAdler commented 3 years ago

I'm going to work on generalizing the layout @brittnylapierre put together in #147.

brittnylapierre commented 3 years ago

Hey @SaschaAdler I changed around the CSS a lot based off of the cube CSS articles in the add canvas menu pull request, feel free to check those changes out it too before you start your work and thanks for your help!

SaschaAdler commented 3 years ago

@brittnylapierre My first line of inquiry for sorting out the layout of the side menu, especially if we want to generalize it, is to use a list of objects containing a svelte:component. If a SideMenu component accepts as a property something that looks like

[
  { name: "General Info", component: InfoEditor },
  { name: "Content", component: ManifestContentEditor }
]

this can be used to dynamically switch the active component, akin to the tutorial link. It also means that in the object route we can use our various type checks to determine which components should populate the list.

If you want to give this a shot, go ahead. It might be more important for me to sort out back-end stuff.

brittnylapierre commented 3 years ago

Ooo thank you for the example! That helps me understand what's possible, I'm excited. I'll work on this tomorrow then, have a good night Sascha!

SaschaAdler commented 3 years ago

I think we have this sorted out.