Someone else should probably come in here and clear/clean this up, because I'm literally coding my first Jcink skin, so my custom forums are probably designed really sloppily. The basic idea, though, is that you have to use the forum_id variable, and use that to change the CSS of everything within it. For example:

<div class="class-<!-- |forum_id| -->">
<div class="class-name">meow</div>
<div class="class-name-2">woof</div>
</div>

<style>
.class-1 .class-name { display:none; }
.class-2 .class-name-2 { display:none; }
</style>

To specify, this would make it so 'meow' only shows up in your first forum, and 'woof' only shows up in your second.

I just inspect element for my forum's ids, because I'm lazy, but that's the basic jist of it? The html loads the same for every individual forum (because Jcink is GROSS and doesn't let you use IF STATEMENTS like PROBOARDS), so it's mostly just a matter of picking and choosing what shows up for what forum, or how different classes display in different forums. o>

leap i'm gonna blow your mind. if statements do work on jcink. i'm mobile so i might not have the exact coding right but i think it's in the format of <script>if('<!-- |forum_id| -->' == '1') { document.write("YOUR CODE HERE") }</script> and then you use the elseif additions to add more. but that way is generally p messy and slow to load since it's loading that script for every single board. i generally prefer to use css and instead use a general class for the board css and then add in an id in the format "board-<!-- |forum_id| -->" since then you can reference that in the css using #board-1 to add in a background color or something (or yknow reference a child element under that id to change something). that way load times are a little faster since i can use scripts to reference smaller bits of code (ie if there's a board description at all) instead of asking it to go through every single board's code for each board on the page and then render one of them twice.

honestly i can pull an example from one of my old skins to show how it works when i'm online, i'm just. about to go to bed oops.

Oct 12, 2019 15:21:12 GMT ninelie said:

Except if the thread title (or anything that shows up that has a double quote, forum descriptions included) happens to have double quotation in it he. It’ll break the coding and the forum won’t even show up. That was the method I employed for one of Mega’s skins, and that’s how I know this error is a thing.

I would rather play it safe by employing forum variables and playing with visibility elements in the css if it means I can allow members to use double quotes in their topic titles, just as a precaution personally.

edit: mobile posting is hard

double edit: you can tell what id number your forum is by its url, denoted but he number at the end.

i mean, you can get around that by switching which quotes you're using where, but then you have the opposite problem.

i still like using if statements for skins - they just work better when it's for small segments of a design (like the list of subboards) over large sections like an entire board, especially since you can't do multiple layers of if statements.

and in the morning uhh. leap the coding is a lil backwards? i'd probably aim more towards something like this

<div class="class-<!-- |forum_id| -->">
<div class="class-name" id="id- 1">meow</div>
<div class="class-name" id="id- 2">woof</div>
</div>

<style>
.class-name { display:none; }
.class-1 #id-1, .class-2 #id-2 { display:block; }
</style>

(obviously i'd pull the style code out and put it into the stylesheets, but that's a bit neater.)

which that's something you can use for doing all individual custom board layouts or just neat little accents or even for different layouts in other templates (i actually use it v heavily for my profiles and mini-profiles). it's less likely to break, like ninelie said, and you can use a similar thing for like. hiding signature codes if they don't exist, for example. but i also just like it because i can come up with entirely different layouts in codepen and convert it over fairly easily with little to no difficulties. (also yep forum number is at the end of the url when you look at it but it's also not a bad idea to use inspect element since membergroup ids are hard to find out any other way).

i'm still mobile so i still don't have actual examples of working code but yeah.