26 views
Skip to first unread message

Ramiro Morales

unread,
Feb 8, 2014, 8:03:28 PM2/8/14
to nikola-...@googlegroups.com
Hi all,

[Mailing list post instead of a ticket because I have no concrete
proposal, mostly a
copy-paste from a Feb 5 post to the IRC channel]

Do you guys like the "Nikola | Nikola" of the HTML <title> for the
main page and the blog index pages at http://getnikola.com ?

(similarly for "Foo | Foo" titles in many other Nikola-based blogs/sites)

I don't.

The good news is that Nikola has a feature to fix that: The
INDEXES_TITLE setting:

The blog index page(s) then use $INDEXES_TITLE | Nikola
otherwise, BLOG_TITLE is used and that's the reason for e.g. "Nikola | Nikola"

Some ideas on how to 'solve' this:

a) Make INDEXES_TITLE more prominent in the default conf.py, now it's
buried between
the comments about the interaction between INDEXES_PAGES and
INDEXES_PAGES_MAIN.

b) Change the default value of INDEXES_PAGES from "" to another value
to force it's initial
value to be recognizable in the final HTML title rendering.

c) Taking b further, perhaps copying its value from another setting
different from
BLOG_TITLE?

d) Some combination of a, b and c.

Opinions welcome.

--
Ramiro Morales
@ramiromorales

Chris “Kwpolska” Warrick

unread,
Feb 9, 2014, 6:26:16 AM2/9/14
to Nikola—Discuss
Maybe something like this (pseudocode):

if not INDEXES_TITLE:
title = BLOG_TITLE
else:
title = ' | '.join(INDEXES_TITLE, BLOG_TITLE)

--
Chris “Kwpolska” Warrick <http://kwpolska.tk>
PGP: 5EAAEA16
stop html mail | always bottom-post | only UTF-8 makes sense

Kay Hayen

unread,
Feb 9, 2014, 8:43:16 AM2/9/14
to nikola-...@googlegroups.com

Hello,

> Do you guys like the "Nikola | Nikola" of the HTML <title> for the
> main page and the blog index pages at http://getnikola.com ?

No, it makes me look stupid as website operator :)
 
>
> (similarly for "Foo | Foo" titles in many other Nikola-based blogs/sites)
>
> I don't.
>
> The good news is that Nikola has a feature to fix that: The
> INDEXES_TITLE setting:

Never knew that, although that is probably more my fault then anything else.

Maybe something like this (pseudocode):

if not INDEXES_TITLE:
    title = BLOG_TITLE
else:
    title = ' | '.join(INDEXES_TITLE, BLOG_TITLE)

Rather not. I would suggest to have standard titles for index, archive, and what not pages, and use them like this.

if isIndexPage():
       title = ' | '.join(BLOG_TITLE, i18n("index page %d"))
elif isArchivePage():
       title = ' | '.join(BLOG_TITLE, i18n("%y archive "))
else:
       title = ' | '.join(BLOG_TITLE, page.title())

Making up a good value for INDEX_TITLE would not be as easy to get right. On the over hand, if documented, and prominent, I wouldn't vote for anything that causes too much effort. I am going to deploy INDEXES_TITLE and be fine. Archive pages don't matter much, do they. I don't even link to them anymore it seems.

I recall that Google complained about my index pages all having the same name, that at least is no longer true. But "$BLOG_TITLE old posts page 8" also feels wrong BTW.

Yours,
Kay

Daniel Aleksandersen

unread,
Feb 9, 2014, 9:12:28 AM2/9/14
to Nikola Discussions
How about:

e) set the default value of INDEXES_TITLE to something that makes the
user realize it can be changed OR set it to a a good default like ‘Front
page’ or ‘Blog’.
--
Daniel Aleksandersen
https://www.aeyoun.com aka “Aeyoun | Aeyoun”

Daniel Aleksandersen

unread,
Feb 9, 2014, 9:20:02 AM2/9/14
to Nikola Discussions
On 09. feb. 2014 15:12, Daniel Aleksandersen wrote:
> On 09. feb. 2014 02:03, Ramiro Morales wrote:
>> b) Change the default value of INDEXES_PAGES from "" to another value
>> to force it's initial
>> value to be recognizable in the final HTML title rendering.
>
> e) set the default value of INDEXES_TITLE to something that makes the
> user realize it can be changed OR set it to a a good default like 'Front
> page' or 'Blog'.

I was so focused on setting a subject on this thread that I must have
glossed over your proposal b). e) is a duplicate of b), it would seem.

What should the default value be? I think “Blog” is friendly enough as
an untranslated international string. Though it kind of implies that
Nikola can only be used for blogging. Other suggestions?
--
Daniel Aleksandersen
https://www.aeyoun.com now as “Blog | Aeyoun”

Chris “Kwpolska” Warrick

unread,
Feb 9, 2014, 10:44:42 AM2/9/14
to Nikola—Discuss
On Sun, Feb 9, 2014 at 3:20 PM, Daniel Aleksandersen
<dan...@daniel.priv.no> wrote:
> On 09. feb. 2014 15:12, Daniel Aleksandersen wrote:
>> On 09. feb. 2014 02:03, Ramiro Morales wrote:
>>> b) Change the default value of INDEXES_PAGES from "" to another value
>>> to force it's initial
>>> value to be recognizable in the final HTML title rendering.
>>
>> e) set the default value of INDEXES_TITLE to something that makes the
>> user realize it can be changed OR set it to a a good default like 'Front
>> page' or 'Blog'.
>
> I was so focused on setting a subject on this thread that I must have
> glossed over your proposal b). e) is a duplicate of b), it would seem.
>
> What should the default value be? I think "Blog" is friendly enough as
> an untranslated international string.

…except the Russians would want to see Блог instead, and not everyone
likes the word “blog“ for their blogs, and look at that:
http://www.wikidata.org/wiki/Q30849#sitelinks-wikipedia

>Though it kind of implies that Nikola can only be used for blogging.

> Other suggestions?

We may have it around the “mandatory settings” thing. It also needs
to be translatable, in the way presented by issue #851.

Chris “Kwpolska” Warrick

unread,
Feb 9, 2014, 10:56:48 AM2/9/14
to Nikola—Discuss
On Sun, Feb 9, 2014 at 2:43 PM, Kay Hayen <kay....@gmail.com> wrote:
>
> Hello,
>
>> > Do you guys like the "Nikola | Nikola" of the HTML <title> for the
>> > main page and the blog index pages at http://getnikola.com ?
>
>
> No, it makes me look stupid as website operator :)
>
>>
>> >
>> > (similarly for "Foo | Foo" titles in many other Nikola-based
>> > blogs/sites)
>> >
>> > I don't.
>> >
>> > The good news is that Nikola has a feature to fix that: The
>> > INDEXES_TITLE setting:
>
>
> Never knew that, although that is probably more my fault then anything else.
>>
>>
>> Maybe something like this (pseudocode):
>>
>> if not INDEXES_TITLE:
>> title = BLOG_TITLE
>> else:
>> title = ' | '.join(INDEXES_TITLE, BLOG_TITLE)
>
>
> Rather not. I would suggest to have standard titles for index, archive, and
> what not pages, and use them like this.
>
> if isIndexPage():
> title = ' | '.join(BLOG_TITLE, i18n("index page %d"))
> elif isArchivePage():
> title = ' | '.join(BLOG_TITLE, i18n("%y archive "))
> else:
> title = ' | '.join(BLOG_TITLE, page.title())

This is kinda sensible. Though I’d like to add another proposal:
collapse titles that are identical, turning "Nikola | Nikola" into
"Nikola". Though this would be tricky, and would require
backwards-incompatible changes to themes.

Christian Barra

unread,
Apr 19, 2014, 6:39:34 PM4/19/14
to nikola-...@googlegroups.com
Try this (base_helper.tmpl):

<title>{% if title!=blog_title %}{{ title|e }} | {% endif %}{{ blog_title|e }}</title>
Reply all
Reply to author
Forward
0 new messages