In very simplistic terms:
In order to display something in FGII you need to build a windowclass. Windowclasses are defined within the ruleset. In 4E_JPG the windowclasses are broken into different files by function/subfunction.
For example there are various files in the rulesets\4E_JPG folder which are titled:
reference_npc.xml, reference_powers.xml, etc. These all contain the windows that layout the "stat blocks" for 4E powers/monsters/etc. The charsheet_*.xml files all relate to the character sheet and so on.
Within each xml file you'll find one or more <windowclass>...</windowclass> blocks of code. These define the elements of a window. Each window can contain a number of controls, some visible, some not visible.
The visible section of each control is defined in the <sheetdata>...</sheetdata> block. Under sheetdata there are various controls (numberfields, stringfields, windowrefences, genericcontrols, etc)
The individual controls on a sheet may support a <frame>...</frame> element. This allows you to specify a grapic frame that is rendered behind the control. The boxes you see around the numbers on a character sheet are an example of a frame.
So:
rulesets
4E_JPG
XML File
windowclass
sheetdata
control
frame
Modules contain data. Raw data. They don't include any sort of frames, shading, scripting, etc.
The <table><tr><td>.....</td></tr></table> is an example of data. It would go in a module and not in a ruleset. You can not add shading directly into a table like that.
Instead you would have to store the data in the module in a structure something like this:
<feat>
<feat01>
<name type="string">blahblah</name>
<description type="string">Something useless</description>
<dice type="string">6d6</dice>
</feat01>
<feat02>
<name type="string">gsdgsg</name>
<description type="string">even more useless</description>
<dice type="string">10d12</dice>
</feat02>
</feat>
Your ruleset would then need to contain 2 windowclasses:
The first is for the row the second is for the whole table.
<windowclass name="stupidrow">
<sheetdata>
<stringfield name="name">
<anchored>
<top>
<to>top</top>
</top>
<left>
<to>left</top>
</left>
<right>
<to>left</top>
<offset>50</offset>
</right>
<bottom>
<to>bottom</top>
</bottom>
</anchored>
</stringfield>
<stringfield name="description">
<anchored>
<top>
<to>top</top>
</top>
<left>
<parent>name</parent>
<to>right</top>
<offset>10</offset>
</left>
<right>
<parent>name</parent>
<to>right</top>
<offset>60</offset>
</right>
<bottom>
<to>bottom</top>
</bottom>
</anchored>
</stringfield>
<stringfield name="dice">
<anchored>
<top>
<to>top</top>
</top>
<left>
<parent>description</parent>
<to>right</top>
<offset>10</offset>
</left>
<right>
<parent>description</parent>
<to>right</top>
<offset>60</offset>
</right>
<bottom>
<to>bottom</top>
</bottom>
</anchored>
</stringfield>
</sheetdata>
</windowclass>
<windowclass name="stupidtable">
<sheetdata>
<windowlist name="feats">
<class>stupidrow</class>
<anchored>
<top>
<to>top</top>
</top>
<left>
<to>left</top>
</left>
<right>
<to>right</top>
</right>
<bottom>
<to>bottom</top>
</bottom>
</anchored>
</windowlist>
</sheetdata>
</windowclass>
And that isn't a particularly well built control. It's just an example of what you should be looking for.