Board Thread:Support Requests - Getting Technical/@comment-27704998-20160607002600/@comment-27704998-20160608010230

1. Got it!

2. I don't think the CSS should be too complicated to implement; the code is also very simple so the other admins on the wiki should understand how it works.

Hmn, the note about the infoicon is good to know. It's things like that that I wouldn't know about without asking you folks, so thank you for the tip!

3. I feel like I should do some more research on the difference between classes and styles. For now, I'll try out the mobile viewer.

4. I wish I could figure out the rhyme and reason behind the way paragraphs/ breaks/ newlines work in this editor. Sometimes it seems like the WYSIWYG breaks in the source editor make a difference, and sometimes they don't. Thank you again for the tip; I wasn't aware of comments behaving like that.

5. Ah. In some instances (autofill links in the visual editor, and the hyperlink button on the toolbar), typing in the link name with incorrect capitalisation makes a red link. The wiki search bar does the same, so I wanted to make triply sure that the links would be correct (I didn't go so far as to make sure that every word had the first letter capped, since I couldn't figure out how to cut up strings or search for a space/ character like you would do in C. Maybe one day I'll see if I can figure out a way to do that in wikitext/ CSS).

I do actually want most of the links to be properly capitalised so that they're consistent with the pagenames, so the current behavior is perfect. I'll definitely apply this knowledge in future templates, though.

I might keep the category link capitalisation, both for consistency and in case wikia decides to change how those are displayed in the future. If it's not harming anything, it seems fine?

Thank you very much for the reply! This was exactly what I was looking for, so now I feel confident I can make templates for the rest of the pages, and make this one live.