-
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
Refactor styles.scss #32
Comments
@patdavid I wanted to get rid of the individual index.css files in each article (articles for now, since apparently So in the index.md for the article, you'd have:
Then in a SASS file, you'd have:
That way we could have one SASS file for all the extra article CSS. I think that'd help us consolidate and it'd cut back the number of calls to the web server. What do you think of that? I had originally thought we had a page slug in there that was a unique string that represented the article, but apparently we're doing that with the folder name. |
I like it! Lets us deal with oddball style cases as needed which is nice. I'd say go for it. Though - we should check that it's really even needed still for most pages. I thought I had started cleaning out posts that used specific stylesheets in order to support this. It might be that most articles don't even have unique stylesheet needs anymore... |
There are a handful or two of articles that still have an index.CSS file. Some of them look like they can be generalized and moved into the main style.scss file, and the others I'll add the class to.
Then I'll move onto the other pages.
…On December 28, 2016 8:16:01 AM PST, Pat David ***@***.***> wrote:
I like it! Let's us deal with oddball style cases as needed which is
nice. I'd say go for it.
Though - we should check that it's really even needed still for most
pages. I thought I had started cleaning out posts that used specific
stylesheets in order to support this. It might be that most articles
don't even have unique stylesheet needs anymore...
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#32 (comment)
|
@patdavid can you check out the sass-class-slug branch? I think I've gotten rid of all the index.css files without breaking the site. Unfortunately, I don't have backstop.js setup anymore :( I need to redo that. |
I'll pull it down later today and test it against a backstop image. |
@patdavid let me know what happened with the sass-class-slug branch when you have a moment! |
I had backstop tests running last week, then got sidetracked into editing a
GIMP news article/interview.
I'll make sure it's the first thing I try as soon as I get home.
On Mon, Feb 27, 2017 at 1:25 AM Mica ***@***.***> wrote:
@patdavid <https://github.com/patdavid> let me know what happened with
the sass-class-slug branch when you have a moment!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#32 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACpnMHfk1zQ5OFhu1qU7UKGEivw5reKsks5rgmxdgaJpZM4Km5KK>
.
--
Pat David
https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC
|
Now that we have that sweet, sweet sass, we should make sure all the classes are nice and clean and get maximum reuse out of our sass!
The text was updated successfully, but these errors were encountered: