xtech

A nice article, but tell me when do you apply these techniques to your site?
Several quick tests show poor results
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Finvisioncommunity.com%2Fnews%2Fcommunity-management%2Ftop-tips-for-optimizing-your-communitys-seo-r1041%2F&tab=mobile
http://www.webpagetest.org/result/171111_DN_1582ddda68468c1ed4489d2cd194f4a2/1/details/

10 hours and no comments on an SEO blog?

Mass mail send interval (throtling) would be welcome.

The existence of such a variable would open new theming possibilities and would make forums really beautiful and visual. Having a $topic->topic_image and $topic->topic_image_thumb as they exist in Pages records (but automated to extract the first image or youtube video thumb of the topic) would be great and would allow visual forum navigation (similar to what happens in Tapatalk, for example). Tapatalk does that: automatically extracts an image from the first post of the topic whenever it exists, and looks great in mobiles. This would be awesome for user engagement and we would have beautiful visual forums, for sure.
Skin designers could come up with new interfaces in which the front page could be lastest topic images with the title below, for example. In an era where great images matter, would be so awesome.

The existence of such a variable would open new theming possibilities and would make forums really beautiful and visual. Having a $topic->topic_image and $topic->topic_image_thumb as they exist in Pages records (but automated to extract the first image or youtube video thumb of the topic) would be great and would allow visual forum navigation (similar to what happens in Tapatalk, for example). Tapatalk does that: automatically extracts an image from the first post of the topic whenever it exists, and looks great in mobiles. This would be awesome for user engagement and we would have beautiful visual forums, for sure.
Skin designers could come up with new interfaces in which the front page could be lastest topic images with the title below, for example. In an era where great images matter, would be so awesome.

The promote dialog will pull any image attachments from the topic, and you can choose from those, or add a new photo upload. There's no real variable stored as the data is kept in a separate table.

Thank you @Ryan Ashbrook, sorry my sincerity but that method is quite ill-designed and not the same as the 3x. It has several flaws:
- It is a javascript controller "show/hide", not a full page reload that matters to increase pageviews and ad reloads.
- If you edit again the article, you cannot edit the page "cuts" as it "spoils" your article - try to do it and you'll see what i mean. For example if you decide to set the page break on a different point of the article, you need to edit the html of the post, remove all the divs and the mention to the JS crontroller and then place the new page tag where you wanted. This is not a practical method. 
Both features (full page reload, edition of article page cuts) were present in 3x and they are fundamental. Please try to put yourselves in the skin of the final user to understand this. A real CMS needs effectively allow multiple pages per article.
This makes us using Pages in competitive disadvantage with others - less pageviews, worse SEO ranking, less revenue.

What about the multiple pages per article? That is a feature from 3x that is absent and is making us loose lots of pageviews and ad money. That is desperately needed!

Thank you @Ryan Ashbrook, sorry my sincerity but that method is quite ill-designed and not the same as the 3x. It has several flaws:
- It is a javascript controller "show/hide", not a full page reload that matters to increase pageviews and ad reloads.
- If you edit again the article, you cannot edit the page "cuts" as it "spoils" your article - try to do it and you'll see what i mean. For example if you decide to set the page break on a different point of the article, you need to edit the html of the post, remove all the divs and the mention to the JS crontroller and then place the new page tag where you wanted. This is not a practical method. 
Both features (full page reload, edition of article page cuts) were present in 3x and they are fundamental. Please try to put yourselves in the skin of the final user to understand this. A real CMS needs effectively allow multiple pages per article.
This makes us using Pages in competitive disadvantage with others - less pageviews, worse SEO ranking, less revenue.

Thank you @Ryan Ashbrook, sorry my sincerity but that method is quite ill-designed and not the same as the 3x. It has several flaws:
- It is a javascript controller "show/hide", not a full page reload that matters to increase pageviews and ad reloads.
- If you edit again the article, you cannot edit the page "cuts" as it "spoils" your article - try to do it and you'll see what i mean. For example if you decide to set the page break on a different point of the article, you need to edit the html of the post, remove all the divs and the mention to the JS crontroller and then place the new page tag where you wanted. This is not a practical method. 
Both features (full page reload, edition of article page cuts) were present in 3x and they are fundamental. Please try to put yourselves in the skin of the final user to understand this. A real CMS needs effectively allow multiple pages per article.
This makes us using Pages in competitive disadvantage with others - less pageviews, worse SEO ranking, less revenue.

What about the multiple pages per article? That is a feature from 3x that is absent and is making us loose lots of pageviews and ad money. That is desperately needed!

What about the multiple pages per article? That is a feature from 3x that is absent and is making us loose lots of pageviews and ad money. That is desperately needed!

What about the multiple pages per article? That is a feature from 3x that is absent and is making us loose lots of pageviews and ad money. That is desperately needed!