Question: Better way to work when sheet building?

Hey guys, When I am writing up the code for my sheets, I'm using Roll20's own inbuilt HTML and CSS custom area in the Game Settings . I have two tabs open, an active  Game  and the Game Settings  tab so that I can save one and refresh the other to see my changes (for times when I need to check sums are working, when 'preview' can't show this.)  Is there a more effective and efficient way to work? The coding areas Roll20 give are quite small, as they need to fit the websites page layout/spacing. I tried using Atom, but I am not sure you can preview your sheet in the same way, or how I could set that up to do so. Curious to know if anybody else has their own methods or ways about it?

Use the Sheet Sandbox. It mentioned right at the start of the main Build Char Sheets page. I really recommend you read more of the wiki documentation available, and check out the related pages/links for more advice, tips and tricks, as there are plenty of advice that will be useful for you. Is there a more effective and efficient way to work? The coding areas Roll20 give are quite small, as they need to fit the websites page layout/spacing. I tried using Atom, but I am not sure you can preview your sheet in the same way, or how I could set that up to do so. I personally use Sublime Text, but others prefer VSCode. Also heard people use other options, but these are the two popular ones. Edit: I updated the Sheet Author Tips page to include a section mentioning Text Editors, just under the section mentioning the use of the Sheet Sandbox.

I really recommend you read more of the wiki documentation available, and check out the related pages/links for more advice, tips and tricks, as there are plenty of advice that will be useful for you. I've asked a couple of questions recently on the forums that many advanced members perhaps find trivial to get their head around. The examples on the wikis are 50/50 when it comes to clarity, some are well detailed and explained and yet others are just 'put there' without much context. Teaching yourself this stuff is really hit and miss, it's hard work for somebody who is learning as they go ! But I get the message. Nonetheless, thanks for your reply, i'm sorry to have taken up your time.

The custom sheet sandbox is a huge improvement on the inbuilt editor. Everyone should be using that.

Noted. I'm here updating a sheet on request of its game community, something I made 2 years ago. I don't remember Character Sheet Sandbox being available then, I didn't even notice that the old Custom Character Sheet interface was any different than the new Sheet Sandbox until now. Not entirely sure that's a reflection on my sense of awareness, but perhaps it is.

It was just introduced earlier this year - it is new.

GiGs said: It was just introduced earlier this year - it is new. Thanks for your patience, I appreciate the heads up.

Leothedino said: The examples on the wikis are 50/50 when it comes to clarity, some are well detailed and explained and yet others are just 'put there' without much context. Teaching yourself this stuff is really hit and miss, it's hard work for somebody who is learning as they go ! But I get the message. True, but the documentation isn't just about how to wrangle your code, it also mentions and show other useful things, like was the case for the Sheet Sandbox. The Sheet Sandbox page starts off listing three popular text editors, for example. I'm here updating a sheet on request of its game community, something I made 2 years ago. I don't remember Character Sheet Sandbox being available then, I didn't even notice that the old Custom Character Sheet interface was any different than the new Sheet Sandbox until now. Not entirely sure that's a reflection on my sense of awareness, but perhaps it is. A lot have changed in 2 years, such as the Sheet Sandbox being introduced around a year ago, and the documentation on the wiki having improved massively . I cannot understate how much of a difference it make compared to when I started with this stuff 3 years ago. And due to the wiki documentation getting constantly small updates(mostly by me), it's always a good idea to revisit if you haven't checked that in a while. Thanks to you asking this question, I improved a couple of pages so that this information will be harder to miss next time someone looks at it, and we others can just share links to relevant part of the documentation.