This is a fairly straightforward project where I'd say it's not that important.  On many projects though it's not going to be immediately clear exactly how you want the GUI to look and operate, and once you make it someone may ask you to change it.  It's good to make quick mockups of the GUI so you or whoever is in charge can come to a concrete decision on what it should look like and then this will give help you see some of the correletive pieces of data you'll need to track that you might not have noticed had you started with the data design.

More importantly, you do NOT want your data design to drive your user interface.  Relatively speaking, I believe fixing poor GUI implementations is far easier than fixing poor data implementations.  So I definitely vote for starting with the GUI.

And I'm more of a database guy myself, just fyi.

Do you start writing GUI class first or reverse?
I have a problem that occasionally a &lt;p&gt; tag is being added to a table cell, usually when someone pastes something into it. 

Is there a way to remove that &lt;p&gt; and just have the cell be an empty &lt;td&gt; or &lt;th&gt;, ideally without editing the source? 

Is there an option that could be added through the advanced settings?
