What pages specifically do you refer to?

If you have the numbers just post them.

Guys, could you take a look at pull requests pls?

https://github.com/NodeBB/NodeBB/pull/2926

Btw, I did sign CLA before. Though CLAhub lately just errors out

@frissdiegurke Knowing what I know now, @julian post can be construed to contain all the information :). I would word it differently though as SSO is probably veyr widely used. And if so, then calling port optional is...well, still technically correct.

Finally upgraded to 0.6.1 from 0.5.7. First I added the port (in my case 8080) to the URL string as described in this thread. That screwed up SSO. Both google and facebook. After, I went back and manually added "port" setting into config.json, SSO seems functional. This appears to be a bug or a logical conflict. Basically SSO is not functional unless your URL string is exactly how you access nodeBB from the outside.

That brings up a feature request. I would like to have an unlisted category. A perfectly ordinary category, just not listed on the home page. Something where I want to list some basic reference information, which is not important enough to keep on the Home page. Is there a way to achieve that?

@xtech If you have an example where mobile scrolling is implemented well within a browser, please post a link

@agarcia17 I looked at templates.js library. I do not think it supports that now.

https://github.com/psychobunny/templates.js/blob/master/lib/templates.js

I got it, now that I understand what installs redis.

The way I upgrade is I create a brand new workspace, install a new version of nodebb, copy over the config.json. I think that makes sense in real deployment scenario versus executing "git pull" in place. This way I retain a fully functional prior version installation I can fall back to in a instant should something fail with a new version.

@dwn Maybe that is the problem. I copied config.json from another workspace instead of running ./nodebb setup

After checking out v0.5.x

waterloo:NodeBB vlad$ npm ll

npm ERR! extraneous: [email protected] /Users/vlad/workspace/nodebb/0.5.7/NodeBB/node_modules/redis
npm ERR! extraneous: [email protected] /Users/vlad/workspace/nodebb/0.5.7/NodeBB/node_modules/connect-redis
npm ERR! extraneous: [email protected] /Users/vlad/workspace/nodebb/0.5.7/NodeBB/node_modules/redis
npm ERR! not ok code 0

SHouldn't redis package be an explicit dependency?

@baris I started working on a more SEO friendly theme/plugin. I hoped I could keep all the changes within a lavender derived theme, but I cannot. Some changes will be in the core. FOr example, server side rendered pagination. I am looking for some advice on how to coordinate making changes in a theme and core nodebb?

I think some sections of nodeBB forum are styled independently from the current theme. Like admin area. So getting rid of less completely may be hard.

Not to harp on the topic. Just pointing out because it may have been misunderstood. - I wanted to pay money to someone for fixing all the SEO issues. I guess, if nobody wants my hard cold cash, I am going to have to do that myself. @julian @baris watch out for a new contributor.

@jonathanmh I did not get that. Could you give us an example?

@baris Though elsewhere you guys use cgi params. Like ?page=3

@Xiph Thanks for pointing that out. Indeed looks like google disregards meta:keywords http://www.metatags.org/google_ignores_meta_tags_in_ranking

Here is my problem. My forum has been up for 2+ months now (http://optionsforum.net). But it still gets no search traffic. This is not my first site, so I know what to expect. I looked at google webmaster. It turns out google seems to have trouble understanding what is important. For example, Google thinks that word 'ago' is one of the most important keywords on my forum because every reply has a little date tag under it that reads like 'posted 2 days ago'. So I guess my question is do we have a nodebb based site with high page rank that gets a lot of organic search traffic?

@baris Why not or you are referring to paginating a long topic? If so you could do /topic?page=5#300

@julian Thanks for the pointers. You reminded me about another thing in nodebb which trips up google. Lets say we have a topic mysite.org/topic/5/my-topic-name. Say it has 5 replies. To get a link at an individual reply looks like this:

mysite.org/topic/5/my-topic-name/3 <-- This is bad. Because for google it looks like a duplicate page of mysite.org/topic/5/my-topic-name. A more SEO friendly way and perhaps the correct way from HTML point of view is to use hash tags like mysite.org/topic/5/my-topic-name#3. All this hash tagging is completely transparent for servers.

Folks, we really need a SEO plugin. I would be willing to send a donation to whoever gets to work on that. I am sure there is a dozen webmasters around here who could do the same. This work would benefits the whole community greatly.

plugin Functionality:

• Fine gained control of how Title element is constructed
• Intelligent construction of keywords meta tag
• Adding ALT tag to all images. Markdown does not support alt= at all.
• Google has recently announced they would also use rel="next" and rel="prev" link elements in the head section of your paginated archives.