Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Determine how to organize our custom design files (LESS, CSS, etc) #169

Closed
5 tasks
brylie opened this issue Jun 26, 2015 · 0 comments
Closed
5 tasks

Determine how to organize our custom design files (LESS, CSS, etc) #169

brylie opened this issue Jun 26, 2015 · 0 comments
Assignees
@55
Milestone
Sprint 6

Comments

@brylie
Copy link
Contributor

brylie commented Jun 26, 2015

Our custom styles are currently stored in one file. Determine common practices for modular LESS files in Meteor projects. Decide on a convention and organize our files to follow the chosen convention.

Examples include:

  • Global styles
  • Variables
  • Template level styles

Related to #166.

Definition of done

  • Decide where to keep view related styles.
  • Decide where to keep global styles.
  • Decide where to keep overrides.
  • Decide where to keep variables.
  • Make sure there is only one point of definition for any given styling.
@bajiat bajiat added this to the Sprint 6 milestone Jun 29, 2015
@55 55 added in progress and removed ready labels Jul 3, 2015
@55 55 mentioned this issue Jul 10, 2015
Merged
@55 55 closed this as completed Jul 10, 2015
@55 55 removed the in progress label Jul 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@55 55

Labels
None yet
Projects
None yet
Milestone
Sprint 6
Development

No branches or pull requests
3 participants
@brylie @55 @bajiat