Technical Support

Feel free to add a pull request for this if you haven't already 🙂

I believe you should have as many partials in your main template as efficiently as possible to cut down on redundant code. Here I'll write the standard for a good rule of thumb on how you should organize your templates and all the code within in them.

Any redundant JS scripts should be in their own partial to be reused in other templates if need be.

Take full advantage of the NBB API so that you extend your template even further. For example using <!-- IF loggedIn --> condition can greatly improve UX and conversions rates on your site. Having some type of call to action or banner within these will let the user know that they aren't logged. OR when they are logged in, show something else. You can come up with some pretty crafty ideas. But yeah, do what you can with the existing API.

You can only do so much with the templates but is that good enough? Maybe, maybe not, but it does work when you plan out the logical flow and hopefully not get lost in the div's and such. For example on the Majestic Theme, the topic covers are pretty complex and one can easily get lost in the flow of what's going on. Here's a screenshot of the topics UI.

Screen Shot 2015-03-17 at 8.12.29 AM.png

Now lets take a little peek at whats under the hood;

Screen Shot 2015-03-17 at 8.16.46 AM.png

Screen Shot 2015-03-17 at 8.14.33 AM.png

Now there's way more to this, but this is just a little example of how I control the topic covers. The only reason why I'm posting this is because I'm quite certain it would take a while to replicate without all of the other partials in this one template (not shown for obvious reasons).

You can also do stuff like this to take control over pluralization of your template: post<!-- IF !topics.unreplied -->s<!-- ENDIF !topics.unreplied -->
Which would mean, if you don't have any posts, remove the s in post, otherwise its posts. Neat huh?

Anyone else have any cool things they've done with the template system so far in their existing theme? Share some of your ideas here. 🙂

In the end, here are the only changes (to the original theme) I did to successfully achieve what I wanted without bug:

It works.

@julian, I've created a repo with my code:
https://github.com/sanpatricio/nodebb-theme-capitol

Thanks a lot! 🙂

Thanks for your prompt response pitaj.

OP has decided to stick with NodeBB with some minor modifications to the home page as per screenshot.

@thesimon Thanks for the link to IPB, I'm sure it's a great platform.

Solved:

.subcategories .category-item {
margin-left:8px;
margin-right:8px;
}

.col-md-3 {
width:24.1%;
}

put that in custom CSS/HTML section

If you make a menu.tpl in lavender it will overwrite the one from vanilla so thats one way of doing it. Or you can fork vanilla and do the changes in your fork and make that a new theme.

Awesome! Thanks guys!

Could possibly use:

$.getScript("url_to_file.js");

??

Hey all, I've resolved this issue as of Lavender v0.2.8 - let me know if you still experience it. Make sure your full width categories have the class col-lg-12

I've created Pull Request with support of loggedIn variable in footer.tpl

Ok, this works

Just put it somewhere between <!-- BEGIN categories --> and <!--END categories --> in home.tpl

And take both \ from {relative_path}.. it seems that nodebb parses it... so I had to type...

Opened an issue. Getting rid of Bootstrap is currently close to impossible without modifying NodeBB.

Ok. it was my first pull request ever, hope I did it correctly. =]

Here, application of the ajaxifying class to the #content element

@baris Thanks, but there's no way to just get all the most recent posts in a category, including all subcategories posts? The templating engine doesn't seem to allow anything too complicated (nor anything complicated at all in fact), so I don't think I can like aggregate the different arrays and sort them...

Maybe it's something that you should be able to configure? Subcategories is a quite recent addition so it's normal that no such thing has been implemented / thinked about yet, but maybe it's something you might want to have.

I really want all my posts on my main page (WIP theme http://nodebb-test.ribesg.fr/)

If you've forked the Lavender theme, just add the original source as another remote:

Then every time you want to merge the latest changes in:

Thanks for that. I would expect some way to configure that. Removing that line would also apply that to all widgets areas, on all themes, right?

My workaround is to add a plznohide class to the appropriate widget areas' divs and add this to either my theme CSS or the "Custom CSS":

It seems to work as expected. Being able to configure if each widget area should be hidden in the ACP would still be nice.