Need Help with Coding

I've gotten a lot accomplished with my character sheet since I last asked for help. I've been trying to learn how to code from looking at different 5e-like sheets in Roll20's Github and I feel like I've learned a lot. However, I've kind of hit a bit of a roadblock. While looking through everything, I've found a lot of tags called data-i18n which confused me for a bit but I think it's some sort of language thing?? I've pretty much been able to work around this for a lot of things but when I came across Tool Prof. or Attacks which had repeating sections, it just became a lot for me. I've also noticed a lot of sheets use JS, PUG, SCSS, and other things that I'm not familiar with. I've been doing all of my coding in HTML and CSS only, nothing else. I haven't had any problems. Just a lack of knowledge when it comes to repeating sections and how to hide some of the information in those repeating sections to clean it up. I would appreciate any little tips and tricks on how they work or how to make them work in HTML and CSS only, if possible. 

Personally, I'm opposed to the increasing use of PUG and SCSS because they made learning sheets much harder, and I'd encourage you to ignore those. A sheet folder should include a html and css file, just look at those and ignore the other files. If the HTMl and CSS are unreadable, just move onto another sheet and ignore that one. The things you need to be aware of: data-i18n: you are correct this is for translations. If you are making sheets for your own personal use you can ignore this. But basically the text here is a string that is used by Roll20's translation software to match text in another language. You can learn more from the wiki. Repeating Sections: I'd suggest these are very important to learn, for the extra features they add to a sheet. They are also very easy to use if you know HTML already: everyting inside a &lt;fieldset class="repeating_NAME"&gt; block makes up a single row of the repeating section, and roll20 handles creating extra rows. There's more here, but that's the gist . Sheet Workers: The JS you see in sheets is a special, limited set of javascript, that allows for fairly powerful automation when modifying a sheet's attributes. This is an optional feature, which you can leave till you are comfortable with HTML and CSS. But it opens up a lot of potential when you are ready. As usual, the wiki has a lot of information . I have a blog where I'm writing articles for sheet authors , but it's still early days. The articles posted so far might be a bit basic, but in time it'll deal with more advanced concepts. But the wiki is always going to be valuable (thanks Andreas for doing such a great job maintaining it): <a href="https://wiki.roll20.net/Character_Sheet_Development" rel="nofollow">https://wiki.roll20.net/Character_Sheet_Development</a>

I’d actually argue that SCSS is easier than CSS, the ability to nest things has made it waaaay easier to think about how styling will affect child elements, etc.&nbsp; It could be debated that PUG could reduce the barrier a little, because you don’t have to use all the fancy parts, and if you don’t, then HTML is a little easier, because you don’t need to worry about closing tags, etc.&nbsp; But, I hear you…the terms can be scary for those who are new to the whole thing. And it could get really complicated. I thought it was until I finally took the plunge.&nbsp;

@GiGs Wanted to say that you are doing an awesome job on covering the essentials of sheet building in your blog.&nbsp; I would highly recommend it to the OP as well as anyone that has designed a sheet for roll20 or is thinking about testing the waters.&nbsp; I'm enjoying reading the topics you've covered so far and I'm personally looking forward to the "more advanced concepts".&nbsp; (lol I see you just posted something new as I'm typing this...) @Finderski I think you nailed my apprehension in your last comment. ;-)

Thank you all for responding! I will definitely check out your blog @GiGs. You've helped me with a lot of my coding and thanks to the forum, I have not given up. I'll give the other things another chance but once I'm more comfortable and confident with HTML and CSS first. Slow and steady gets a character sheet done eventually! :)

Sirius said: Slow and steady gets a character sheet done eventually! :) Indeed - it took me around 8 months to make my first sheet and I still had lots to learn, hehe. Finderski said: It could be debated that PUG could reduce the barrier a little, because you don’t have to use all the fancy parts, and if you don’t, then HTML is a little easier, because you don’t need to worry about closing tags, etc. The problem is, you cant effectively use PUG without already knowing HTML and JS, and I think you have to know both of them pretty well before you even start on using PUG. HTML itself is pretty simple, though very clunky on its own. If you had to learn PUG before posting sheets to the roll20 github, that place would be a lot more barren with a lot fewer sheets than it has now. CSS is a whole other beast, of course :)

Thanks Vince, it's rewarding to hear that :)

Finderski said: I’d actually argue that SCSS is easier than CSS, the ability to nest things has made it waaaay easier to think about how styling will affect child elements, etc. this