Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4606830
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T00:37:09+00:00 2026-05-22T00:37:09+00:00

In Rails, the common idiom for page-specific Javascript is: (layout) <head> <% yield :javascript

  • 0

In Rails, the common idiom for page-specific Javascript is:

(layout)

<head>
  <% yield :javascript %>
</head>

(view)

<% content_for :javascript do %>
  <script type="text/javascript">
    $().whatever;
  </script>
<% end %>

I hate repeating the script tags. Is there any reason why the following is a bad idea?

(layout)

<head>
  <script type="text/javascript">
    <% yield :javascript %>
  </script>
</head>

(view)

<% content_for :javascript do %>
    $().whatever;
<% end %>
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T00:37:10+00:00Added an answer on May 22, 2026 at 12:37 am

    I agree that it’s what is most specific to your use case. Generally, when I use the <% yield :javascript %>, it’s purpose is to add in page specific libraries, which would be a limitation to the approach you proposed. If you want to support both, I have done the following:

    (layout)

    <head>
      <% yield :javascript_libraries %>
      <script type="text/javascript">
        <% yield :javascript %>
      </script>
    </head>
    

    (view)

    <% content_for :javascript do %>
        $().whatever;
    <% end %>
    <% content_for :javascript_library do %>
        <%= javascript_include_tag 'page-specific.js' %>
    <% end %>
    

    Of course most people put javascript libraries at the bottom for optimization of page loading, so then you could just move it in your layout.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

A common idiom that my camp uses in rails is as follows: def right_things(all_things,
I noticed that it is quite common in Rails to render back text for
It seems common in the Rails community, at least, to respond to successful POST
What are most common Ruby on Rails antipatterns and how to avoid them?
I've noticed that a common error check line in rails is: if @user.save! rather
I'm close to releasing a rails app with the common networking features (messaging, wall,
I develop Rails based website, enjoying using partials for some common components Recently, i
I'm new on both this site and ruby on rails! I have a common
I find a common issue in my RESTful Rails apps controllers that respond to
rails 3 rspec-rails 2 In controller: def index @users = User.paginate :page => params[:page],:per_pae

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.