-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCSS Directory structure suggestion #7
Comments
Hey @rgksugan Agreed! I think (master, base, layout) files are less used; let's keep that in common folder. Where in module and pages are used often, so let's put that into a folder as you have suggested. Later if we are have more features in other components we can move it to a folder too. I will work on it and update it here. |
Directory structure suggestion
|
This is pretty close to what i had been using. 👍 |
@MarinaDiamonds I have taken this suggestion from your library only, thanks for the awesome structure. Will give the credits once we finalize. |
I haven't made my structure public yet, the fork you see on my profile is unchanged from @minamarkham's architecture. All credit must go to her. |
Alright; sure will do.. |
Hi @logeshpaul
Thinking about scalability, I would prefer separate directories for each components (base, layout, master etc.), rather than a single file.
Even modules can have different directories, for which we can provide with sub generators.
The text was updated successfully, but these errors were encountered: