how would you explain the huge difference related to the views by guests shown in the dashboard (ACP) in comparison to the views shown in Google Analytics?
Which number would you consider as trustworthier?
I love the dashboard but would LOVE to see more information available, specially around site performance.
Stats like:
Post rates, not just view rates and user rates. Thread rates too.
Stats per day, week, month not just by the hour.
Selectable time periods, not just one day but week, month, year, etc.
Stats about IP addresses or ranges, browsers if possible.
Just more info in general.
@arasbm As a recent NodeBB explorer (and NodeJs) I'll suggest you to start with the harder of plugins and themes and it's plugins.
As I understand the thing :
Plugin is a custom behaviour that could work on every NodeBB forum and that is not based on the theme. It should be configurable (if needed) and not conflict. It try to solves a problem that is experience related.
Theme is how you want your NodeBB forum to look like. It's easier to go inside because it's based on a sublime api and it's just css/html and and a bit of JS. If you want you theme to create a custom behaviour that is only applicable to itself then you can because themes are created and treated like plugins.
You can take a look at the api on every NodeBB page with {origin}/api/{path}
Both plugins and themes can make the use of the api and write content to use after. Take a look of the existing ones and you'll have a good point of view to start developing you owns.
@pitaj router and app are both routers, per se. However, router refers to a separate router instantiated specifically for plugins to use.
When NodeBB reloads, the plugin router gets regenerated, while the application router does not.
This allows plugins to be both activated and deactivated without a full restart.
... You also cannot overwrite existing application routes in app, though you weren't allowed to do that for awhile now.
If you are only going to use mongodb definitely have multiple collections with indices that make sense. For example your users collection can have indices on username whereas your posts collection can have indices on content and userid etc.
Well, remember that NodeBB is firstly designed with redis in mind (a simple in-memory key/value store) so that might affect the document design decisions they made for their mongodb collection.
This is why we have one collection in our mongodb implementation. To make db.delete db.rename easy to implement. From the db perspective there is no difference between a post and user object they are both indexed by the _key field so finding them is easy. For sorting and querying we use sorted sets, they are implemented in mongo using indices on value and score.
if embedded documents in my collection persons is more efficient than saving them in the same collection with a different key.
I wouldn't suggest embedding lots of documents, mongodb has a document size limit of 16mb so it won't let you insert more users after some point.
