Skip to content
This repository has been archived by the owner on Dec 11, 2021. It is now read-only.

Where do we go from here? #176

Open
sfrisk opened this issue Feb 14, 2017 · 5 comments
Open

Where do we go from here? #176

sfrisk opened this issue Feb 14, 2017 · 5 comments

Comments

@sfrisk
Copy link
Contributor

sfrisk commented Feb 14, 2017

This project has been around for about two years now, although due to other life concerns and time availability of team members, progress has been slow for the last year. We've been lacking in focus, and components tend to go in different stylistic directions, both code wise and visually.

We also made decisions 2+ years ago that maybe are not the best ideas now. So the purpose of this issue thread is to analyze decisions we made and see where we need to go from here. Let's come up with a clear list of actionable goals for V1 which could include the following:

  • Analyze tooling, revisit if necessary
    • Currently we are using grunt.
  • Refactor Typography. How do we want to handle it? (responsive typography, units, etc)
  • Are we still happy with SASS? Is it worth it to look at post-css, and embrace CSS modules instead? (It would make it easier for JS libraries to use just the parts of this project they need, since CSS modules are becoming popular)
  • Getting Started / Style Guide files
    • This might help with new contributors, as our current way of doing things isn't well documented unless you look at the code
  • Etc
@geekman-rohit
Copy link
Contributor

Just my 2 cents:

  1. I am happy with grunt. Though we should once revisit the tests we have used and remove the ones that are not relevant right now. There is an accessibility test PR pending which I think should be merged.
  2. This is going to be a big debate over at Typography and Unit Measurement Review and Refactor #172 , But we should certainly remove the em mixin and use rems in some cases rather than ems.

@geekman-rohit
Copy link
Contributor

We are planning to meet on Sunday 26 February 2017 at IRC Freenode #jquery-meeting to discuss and plan things for chassis.

If you wish to participate, please join us and convey a time suitable for you at

http://doodle.com/poll/sp7diqwavx4zagms

We will post the final time here by Saturday.

@sfrisk
Copy link
Contributor Author

sfrisk commented Feb 23, 2017

  1. The only reason why I brought up grunt is that I've seen more js frameworks these days prefer webpack.
  2. definitely.

@sfrisk
Copy link
Contributor Author

sfrisk commented Feb 26, 2017

So how about 11 am ET on Sunday?

@dandv
Copy link

dandv commented May 24, 2020

I've just learned about OpenJS, which lists this as a project.

Is one of the goals of OpenJS to help projects like Chasis remain maintained?

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

No branches or pull requests

3 participants