Google likes titles to be distinct for every page and they use that
for page rank. My old layout had the same title for every page. I
looked up
dynamic layout in this group and followed the suggestion for
page specific titles. Now I have a
'@title'
variable in the controllers, I assign it in index and other routines
like this:
'def index
@title = "something"
end'
whatever is the appropriate title for that page and then in the layout
I have
'<title> <%= @title => </title>'
This WORKS in the test environment but when I capistrano upload the
app to the production environment title is ALWAYS blank, an empty
string.
Google likes titles to be distinct for every page and they use that
for page rank. My old layout had the same title for every page. I
looked up
dynamic layout in this group and followed the suggestion for
page specific titles. Now I have a
'@title'
variable in the controllers, I assign it in index and other routines
like this:
'def index
@title = "something"
end'
whatever is the appropriate title for that page and then in the layout
I have
'<title> <%= @title => </title>'
This WORKS in the test environment but when I capistrano upload the
app to the production environment title is ALWAYS blank, an empty
string.
Ah, there is a much more elegant way of doing this!
ActionView has a content_for method, which you can use.
Here is a blog post explaining how it works (with some extra stuff)
Google likes titles to be distinct for every page and they use that
for page rank. My old layout had the same title for every page. I
looked up
dynamic layout in this group and followed the suggestion for
page specific titles. Now I have a
'@title'
variable in the controllers, I assign it in index and other routines
like this:
'def index
@title = "something"
end'
whatever is the appropriate title for that page and then in the layout
I have
'<title> <%= @title => </title>'
This WORKS in the test environment but when I capistrano upload the
app to the production environment title is ALWAYS blank, an empty
string.
Ah, there is a much more elegant way of doing this!
ActionView has a content_for method, which you can use.
Here is a blog post explaining how it works (with some extra stuff)
