Skip to content

Conversation

muildrik
Copy link
Contributor

Here's a first attempt of moving the styling out of the informationPanel component into its own .scss-file. This will definitely be a lot more manageable than having to deal with Stitched and I think, as you said, provides maximum flexibility for overall styling.

There's a few ways to organize this, but I think the best way is probably to define one .scss-file for each component, with its subcomponents in there, and then @use/@forward them in a single global file. That way it should be fairly straightforward to track how a particular part of the application can be styled outside of JSX. We can then come up with a solution to style via JSX if you wanted to do that.

In the docs we do want to clarify what we mean by component, subcomponent, and perhaps even element. Below a little graphic we can use to organize what I would call the elements of the Viewer Component: the header, canvas, informationPanel and navigation. The subcomponents would be the smaller bits within it such as the navigation buttons in the navigation element.

image

Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants