Sept 4, 2018 6:19:32 GMT Kitten4u said:

I'm super late, but if you're not sure where to start then starting with setup, basic tips, or just things that you wish you knew when you were getting started seem like good places to start! I'd personally love to see some basic admin guides, whether it be admining in general or host specific stuff. \o/

i'm..... probably going to slowly start working on breaking down every single part of the admin panel. what each category does, what each option does, and how useful it is. if only because i generally see the biggest complaint of people switching being that the admin panel is confusing and intimidating so i'm hoping that by breaking it down section by section, i'll make it a ton easier to understand.

and then finish the whole thing off by teaching people how to avoid dealing with it entirely whenever possible since there are shortcuts, people just don't always know how to get to them.

Sept 4, 2018 7:08:37 GMT Kitten4u said:

Sept 4, 2018 6:33:19 GMT nova winchester. said:

The guide I would like to see the most from both a proboards coder and a jcink coder is an indepth guide on specific ID's that are native to the host. I.E the div class/id's that are already part of the structure that you can technically manipulate but never think of. Like categories and forums and profile id's, search page id's, etc. 

Another example: When I was creating my current skin for Victory, I wanted the avatar's to show in the footer for who is online. I easily got that to work, but I couldn't appropriately get it to hotlink to the players profile until Leap helped me by giving me the needed ID.

$[online_user.href]">$[online_user.avatar_small]{if $[online_user.invisible]}

^^^ THIS crap doesn't come with a handbook that is easy to read and written specifically for a proboard and jcink skinner pov.

Jcink actually does a decent job documenting their stuff (or if you were looking for variables). I wish Proboards documented their advanced features better but they are unfortunately pretty bad about it. :< I was thinking about writing up something for this (both the css and variables), but it'll probably take awhile just because Proboards has so much of it. Documenting some of Proboards' features is definitely on my radar though. \o/ I just have a billion other projects to sort through right now.

yeah no joke jcink really is great about that. literally when i say i can code an entire skin more or less in codepen and pull it out no problem, i'm not exactly joking. you can find like. three to six codepen pages dedicated to each skin in my profile actually lmfao which i hate and should probably take down now since private's a premium feature but. laziness. you can actually code the entire skin in codepen or jsfiddle or a custom tumblr page or even a notepad file and then just copy out the original code and paste it in.

i keep these two links in my bookmarks bar and pull them out when i need them but basically my best friend in the headers + footers + topbars and my best friend for p much anything else get me through without issues. the only missing variable i've ever found across three years of skinning jcink is <% SUBACCOUNTS %> which is used for snagging the subaccount dropdown in the overall wrapper. and then since jcink hands over a lot of the code areas to you to basically rip out and replace entirely with your own, there's not a whole lot of global things you really have to mess with - and what you do, 90% of the time it's just popping into the css to set it to display: none or to rip out the default color styling. the big "these are default classes you use" are, i believe, maintitle, topic-title, wrapper, innerwrapper, copyright, button (and small-button), occasionally the navstrip. which those may or may not be exactly right since ahhhhhhhh i'm not looking directly at the stylesheet and do not care enough to dig them all out one by one.

other than that, jcink coding is really a lot of "okay let's get the default thing to work now let's add the script so it'll hide from guests and test it" or "okay let's just inspect element to see what the hell exactly is going on here or snag 1 class or value". which is something a lot of coders figure out how to do just for troubleshooting anyway.

sunmi. has done it. again.