Closed scottkellum closed 10 years ago
Thanks Scott. These goals and issues look great.
Modularscale.com is indeed a site, but I think of it as a tool. The calculator is the reason why the site exists, and I use the site like I would use an app. Why don't we rename Goal 1 as, "Improve and clarify the web calculator" and Goal 2 as, "Explain what modular scales are, how to make them, and how to use them".
Users of the web calculator (like me) may be pretty new to Sass, so we should introduce that with care. Calculated results may be a good place to offer a Sass-based takeaway (Step 1: Install modular-scale. Step 2: Copy/paste the SCSS of your scale.). We could also explain modular-scale with the text, UX, and examples we define in Goal 2.
In fact, "Introduce code-based calculation" probably deserves to be its own goal.
In typing this all out, I found it easy to refer to my site as "the web calculator" and your Sass work as "modular-scale". We should think about how we refer to these different parts of the overall concept.
Great points Tim. I updated accordingly
In typing this all out, I found it easy to refer to my site as "the web calculator" and your Sass work as "modular-scale". We should think about how we refer to these different parts of the overall concept.
How about “the web calculator” and “the Sass calculator”? The overall concept of these two is exactly the same but executed in different contexts. Assuming the user has Sass is a huge assumption to make and it would be nice to keep things open for JavaScript, Stylus, and maybe even LESS (no custom function support yet) powered calculators.
Maybe we can switch context of the web calculator for users of the various language based calculators. Have it output some setup code and have the visuals illustrate how to use the calculators instead of just returning values?
:thumbsup: to all of that, Scott.
I’ll start this thread off.
Goals
Constraints