Updates to Building Character Sheets Wiki & GitHub README

1540578143
Roll20 Dev Team
Roll20 Team
Greetings sheet authors! In an effort to improve the character sheet creation and updating process, we have rolled out changes to the  Building Character Sheet  wiki.  With a growing Github community of 550+ contributors, 590+ folders, and over 20,000 commits, it has become ever more important to try to set easy to follow guidelines in order to abate the challenges that come with a collaboration project on this scale.  The most notable updates include: Minimum Requirements  for submitting to the Roll20 repository on Github, Beyond the minimum , a collection of helpful advanced features Best Practices  contributed by veteran sheet authors The minimum requirements posted in the  Building Character Sheet  wiki are a replacement for the old guidelines formerly found in the  GitHub README . The README has received its own updates as well. The important one to note is:   Pull requests are processed weekly and should be  submitted no later than 6am PST Mondays , roughly 13:00-14:00 UTC. Earlier submissions are encouraged to allow for peer review from other contributors. Getting pull requests in before this set time will help the repository curator to review changes, merge requests, and test submissions prior to the official code push. Submitting these requests early offers a chance for our awesome veteran sheet authors over on the Github to take a look at them. We have several helpful collaborators who generously offer their time to look over new pull requests and provide feedback or help. Additional updates include the  kitchensink  which now reflects the minimum requirements. Questions, comments, and feedback is welcome :) Thank you sheet authors for all your past, present, and continued work in order to make this collaboration project possible!
1540783128
Vince
Pro
Sheet Author
Thanks for creating this.  All sheet authors existing as well as future should benefit from this addition to the wiki.
1540808408
Jakob
Pro
Sheet Author
API Scripter
All new sheets are expected to use proper containers elements such as  <⁠div>  and  <⁠span> elements. Hallelujah, no more tables!
1540823480
G G
Pro
Sheet Author
Are you sure they aren't regarding tables as a proper container element? It is still the suggested format for rolltemplates, after all.
1540824583

Edited 1540833161
Cassie
Roll20 Team
I missed the rolltemplates example when doing the wiki updates. I will get that updated today to use <div> & <span>. Tables are perfectly fine for tablular data however an entire sheet and rolltemplates are not generally considered tabular data. :) Feedback on this is welcome as it is a group effort.
1541998544
Andreas J.
Pro
Sheet Author
I might have something interesting under works, when it comes to sheet translations.  Here are some partially translated sheets made by my small program.
1542066337
Vince
Pro
Sheet Author
Andreas J. said: I might have something interesting under works, when it comes to sheet translations.  Here are some partially translated sheets made by my small program. This would be a cool application.  A real time saver for sheet authors. 
1542075044
Chuck
Plus
As a DM and Player I have noticed since the sheet change, lots of the boarder lines are duplicated and layer over text in some areas and text doesn't stay within the lines. 
1542076834
keithcurtis
Roll20 Mod Team
Hi Chuck, Which sheet are you talking about? This thread is about changes to the submission policy for all sheets.
1542132206
Andreas J.
Pro
Sheet Author
Vince said: This would be a cool application.  A real time saver for sheet authors.  Yeah I know, that's why I started on it. Had the luck that I could design a mandatory assignment I had to be both useful for my course, and to create a base for something actually useful(outside the learning experince itself). I was gifted credits thanks to this, so now I could get back being Pro, and can see how the output files behave, and generate translation.json files to see what it's missing. :) Will take my time working on it, but going to be a bit on the backburner(like my work on sheets already been for some time), now that it's not a part of my studies. Likely will have a workable V.05 or something around Christmas time. I'll make a separate post about it, when I have something more than the current v.0.1.(mentioned in the readme).
1542157365
Coal Powered Puppet
Pro
Sheet Author
Jakob said: All new sheets are expected to use proper containers elements such as  <⁠div>  and  <⁠span> elements. Hallelujah, no more tables! For those of us who are self taught- via Roll20 and the forehead-to-keyboard-realignment method- a quick example of how "proper containers elements" would not go unappreciated.  And a line or two on styling the "Attribute-backed spans" would have saved me about two hours of frustration.
1542166956
Andreas J.
Pro
Sheet Author
Coal Powered Puppet said: For those of us who are self taught- via Roll20 and the forehead-to-keyboard-realignment method- a quick example of how "proper containers elements" would not go unappreciated.  And a line or two on styling the "Attribute-backed spans" would have saved me about two hours of frustration. Yeah this exactly. I haven't put energy to try make my sheets better or without tables because when I looked into it, I didn't get really far and just did how I knew would work at least in some form. So yeah my sheets still have horrible code.(on the other hand I didnt make the SWD6 sheet so not my fault) Suggesting real alternative to the row, col and the old classes shoudl also be made if they after all are bad practice(from times since before I got started).
1542174550
G G
Pro
Sheet Author
Coal Powered Puppet said: Jakob said: All new sheets are expected to use proper containers elements such as  <⁠div>  and  <⁠span> elements. Hallelujah, no more tables! For those of us who are self taught- via Roll20 and the forehead-to-keyboard-realignment method- a quick example of how "proper containers elements" would not go unappreciated.  And a line or two on styling the "Attribute-backed spans" would have saved me about two hours of frustration. I had missed that bit about attribute-backed spans. That looks like a useful approach except it says in the best practices section:  Spans over disabled inputs .  Attribute-backed spans  are more efficient than disabled inputs. But in the linked section it says: When using attribute backed spans in a repeating section, you should always make a hidden input version of the attribute as attribute backed spans in repeating sections cannot be called without the full repeating section syntax (e.g. @{repeating_SECTIONNAME_$X_attribute_name}). Is it really more efficient to use a span when you have to add an input as well, as opposed to just using an input? That doesn't seem to make sense to me. I realise this is for repeating sections specifically and not general use, but the efficiency recommendation doesn't distinguish between the two.
1542174745
G G
Pro
Sheet Author
Andreas J. said: I might have something interesting under works, when it comes to sheet translations.  Here are some partially translated sheets made by my small program. I cant tell what your sheets have done. What is the application you are working on going to do?
1542174867
Cassie
Roll20 Team
Way ahead of you good people. The Kitchen Sink example was updated to include <div> tags. For a more elaborate example I would look at the Dungeon World Official sheet. I too am self taught and my primary guides learning tools were W3Schools and Code Academy .
1542176911
Andreas J.
Pro
Sheet Author
G G said: I cant tell what your sheets have done. What is the application you are working on going to do? Hmm i though the readme mentioned it. Anyway, I've started to work on a program the automate the creation/insertions of i18n tags for character sheets that dont have them(the giles with the i18n- prefix are translated files, those without are original). It's a bit faulty still but could potentially speed up the process. I did make a example of your trollbabe sheet but hadn't placed it in that fodder yet.