View Topic

I made a new recent topics page, just to try my hand at making something better. Any thoughts on this? Better or worse than what we have now?

http://wintreath.com/index.php?part=recent

I made a new recent topics page, just to try my hand at making something better. Any thoughts on this? Better or worse than what we have now?

http://wintreath.com/index.php?part=recent

By what we have now, do you mean the news feed?

No, the active topics page: http://wintreath.com/forums/index.php?action=recenttopics

Both kinda look weird to me, maybe because I'm not used to it, maybe because the topics aren't bolded. Dunno. The new one is nicer though.

Nice...but weird.

A like the new one better than the old one, but like tau said, I'm not used to it since I've gotten used to just checking the newsfeed every now and then.

The newsfeed is still there, but I think some people use recent topics too just to see what's new.

The newsfeed is still there, but I think some people use recent topics too just to see what's new.

I just check the forums directly and scan for any places that are unread.

I've made some updates to the page, to try to make it look better and more functional on mobile devices. I'd love some opinions and thoughts.

Spoiler

This is from a desktop computer, windows 10, using Chrome.

Try Ctrl+F5. Looks like Chrome is pulling some stuff from your cache.

Cheers, fixed now. =D

What I'm noticing is that, while the recent posts page continues to update if someone posts something new and you haven't refreshed, it:
1) Breaks the order in which information is displayed, which then
2) Breaks the formatting much more egregiously than it used to

In the case of 1, it is usually Topic-Reply #s-Starter-Replier. After someone posts without refreshing, the board in which the topic was posted is added to the list, making it Board-Topics-Reply #s-Starter-Replier, and then causes the table (because it's essentially a table) to extend out an extra column.
I'll note that I use Firefox generally, and this might not be a problem on Chrome, but it also appears on Edge. So there's that.