Rails scss stylesheet per action
How can I render a stylesheet per action in rails?
Since my app is not the standart CRUD app, my controllers end up with a few custom routes which require very different CSS's.
So, I'm wondering, is there any way to load the css on a per action basis but still take advantage of the asset pipeline?
Thanks
css ruby-on-rails asset-pipeline
add a comment |
How can I render a stylesheet per action in rails?
Since my app is not the standart CRUD app, my controllers end up with a few custom routes which require very different CSS's.
So, I'm wondering, is there any way to load the css on a per action basis but still take advantage of the asset pipeline?
Thanks
css ruby-on-rails asset-pipeline
add a comment |
How can I render a stylesheet per action in rails?
Since my app is not the standart CRUD app, my controllers end up with a few custom routes which require very different CSS's.
So, I'm wondering, is there any way to load the css on a per action basis but still take advantage of the asset pipeline?
Thanks
css ruby-on-rails asset-pipeline
How can I render a stylesheet per action in rails?
Since my app is not the standart CRUD app, my controllers end up with a few custom routes which require very different CSS's.
So, I'm wondering, is there any way to load the css on a per action basis but still take advantage of the asset pipeline?
Thanks
css ruby-on-rails asset-pipeline
css ruby-on-rails asset-pipeline
asked Dec 1 '15 at 14:38
Nuno
2421317
2421317
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
create a directory for each of your controllers inside stylesheets directory and create css files corresponding to your action, then put this in you layout file
<%= stylesheet_link_tag "#{params[:controller]}/#{params[:action]}" %>
With this I believe we're not taking advantage of rails asset pipeline. I've found this [link]stackoverflow.com/a/22915786/2517796 here on SO and I believe this is what I'm looking for!
– Nuno
Dec 1 '15 at 14:52
add a comment |
You can use controller specific assets. Just remove the *= require_tree .
from application.css. And include the stylesheet the action specific stylesheet in its view by <%= stylesheet_link_tag "style.css" %>
but you have to tell rails to compile them by Rails.application.config.assets.precompile = ["style.css"]
. You can read more about it here. This way I guess we are using rails assets pipelines just not in default way.
add a comment |
Add a unique id to the body based on the controller path and action:
Helper:
def page_id
"#{controller_path.tr('/', '-')}-#{action_name}".dasherize
end
Layout:
<body id="<%= page_id %>"...
Then scope your styles to it:
/users/index.scss
#users-index {
.. page specific styles here ..
}
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f34022991%2frails-scss-stylesheet-per-action%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
create a directory for each of your controllers inside stylesheets directory and create css files corresponding to your action, then put this in you layout file
<%= stylesheet_link_tag "#{params[:controller]}/#{params[:action]}" %>
With this I believe we're not taking advantage of rails asset pipeline. I've found this [link]stackoverflow.com/a/22915786/2517796 here on SO and I believe this is what I'm looking for!
– Nuno
Dec 1 '15 at 14:52
add a comment |
create a directory for each of your controllers inside stylesheets directory and create css files corresponding to your action, then put this in you layout file
<%= stylesheet_link_tag "#{params[:controller]}/#{params[:action]}" %>
With this I believe we're not taking advantage of rails asset pipeline. I've found this [link]stackoverflow.com/a/22915786/2517796 here on SO and I believe this is what I'm looking for!
– Nuno
Dec 1 '15 at 14:52
add a comment |
create a directory for each of your controllers inside stylesheets directory and create css files corresponding to your action, then put this in you layout file
<%= stylesheet_link_tag "#{params[:controller]}/#{params[:action]}" %>
create a directory for each of your controllers inside stylesheets directory and create css files corresponding to your action, then put this in you layout file
<%= stylesheet_link_tag "#{params[:controller]}/#{params[:action]}" %>
answered Dec 1 '15 at 14:45
Saqib
517214
517214
With this I believe we're not taking advantage of rails asset pipeline. I've found this [link]stackoverflow.com/a/22915786/2517796 here on SO and I believe this is what I'm looking for!
– Nuno
Dec 1 '15 at 14:52
add a comment |
With this I believe we're not taking advantage of rails asset pipeline. I've found this [link]stackoverflow.com/a/22915786/2517796 here on SO and I believe this is what I'm looking for!
– Nuno
Dec 1 '15 at 14:52
With this I believe we're not taking advantage of rails asset pipeline. I've found this [link]stackoverflow.com/a/22915786/2517796 here on SO and I believe this is what I'm looking for!
– Nuno
Dec 1 '15 at 14:52
With this I believe we're not taking advantage of rails asset pipeline. I've found this [link]stackoverflow.com/a/22915786/2517796 here on SO and I believe this is what I'm looking for!
– Nuno
Dec 1 '15 at 14:52
add a comment |
You can use controller specific assets. Just remove the *= require_tree .
from application.css. And include the stylesheet the action specific stylesheet in its view by <%= stylesheet_link_tag "style.css" %>
but you have to tell rails to compile them by Rails.application.config.assets.precompile = ["style.css"]
. You can read more about it here. This way I guess we are using rails assets pipelines just not in default way.
add a comment |
You can use controller specific assets. Just remove the *= require_tree .
from application.css. And include the stylesheet the action specific stylesheet in its view by <%= stylesheet_link_tag "style.css" %>
but you have to tell rails to compile them by Rails.application.config.assets.precompile = ["style.css"]
. You can read more about it here. This way I guess we are using rails assets pipelines just not in default way.
add a comment |
You can use controller specific assets. Just remove the *= require_tree .
from application.css. And include the stylesheet the action specific stylesheet in its view by <%= stylesheet_link_tag "style.css" %>
but you have to tell rails to compile them by Rails.application.config.assets.precompile = ["style.css"]
. You can read more about it here. This way I guess we are using rails assets pipelines just not in default way.
You can use controller specific assets. Just remove the *= require_tree .
from application.css. And include the stylesheet the action specific stylesheet in its view by <%= stylesheet_link_tag "style.css" %>
but you have to tell rails to compile them by Rails.application.config.assets.precompile = ["style.css"]
. You can read more about it here. This way I guess we are using rails assets pipelines just not in default way.
answered Dec 1 '15 at 18:16
krsoni
349110
349110
add a comment |
add a comment |
Add a unique id to the body based on the controller path and action:
Helper:
def page_id
"#{controller_path.tr('/', '-')}-#{action_name}".dasherize
end
Layout:
<body id="<%= page_id %>"...
Then scope your styles to it:
/users/index.scss
#users-index {
.. page specific styles here ..
}
add a comment |
Add a unique id to the body based on the controller path and action:
Helper:
def page_id
"#{controller_path.tr('/', '-')}-#{action_name}".dasherize
end
Layout:
<body id="<%= page_id %>"...
Then scope your styles to it:
/users/index.scss
#users-index {
.. page specific styles here ..
}
add a comment |
Add a unique id to the body based on the controller path and action:
Helper:
def page_id
"#{controller_path.tr('/', '-')}-#{action_name}".dasherize
end
Layout:
<body id="<%= page_id %>"...
Then scope your styles to it:
/users/index.scss
#users-index {
.. page specific styles here ..
}
Add a unique id to the body based on the controller path and action:
Helper:
def page_id
"#{controller_path.tr('/', '-')}-#{action_name}".dasherize
end
Layout:
<body id="<%= page_id %>"...
Then scope your styles to it:
/users/index.scss
#users-index {
.. page specific styles here ..
}
answered Nov 11 at 20:10
riley
1,66511725
1,66511725
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f34022991%2frails-scss-stylesheet-per-action%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown