Following up on @Scribs idea:
Having the tiddler created so that the text-field is populated this way certainly works, and gives you a good feel for how easy it is to display fields.
If you want to be maximally flexible moving forward, then you might want to make a template that uniformly displays your fields in a particular chosen way.
You would make a template tiddler called ProjectTemplate (or whatever you like) with the contents:
Title: {{!!title}}
Client: {{!!client}}
[...add more here...]
If you modify the <$action-createtiddler>
widget, so that each new tiddler’s text field is set to {{||ProjectTemplate}}
… then the resulting tiddler will “transclude” the information in its fields, according to the template’s instructions, making it look the same, in view mode, as packing all that content into the text field each time.
Why put extra time into setting it up this way? It’s slightly more efficient in the long run. But also:
Suppose you realize you need to edit or add complexity to how these tiddlers look (Let’s show client names with yellow highlighting! Let’s put the title in bold…, and let’s also display the date the project was created, with a horizontal rule underneath all those headers… Oh geez, the yellow highlighting is too tacky, scratch that… but let’s include the company logo floating off to the right…)…
No problem! Then you just change the template once, and any tiddler set up this way (displaying field data according to this template) will instantly reflect your new preferences about how to display the details. Moving forward, you can experiment with different patterns, without having to go back and edit every project tiddler’s content to reflect your new choice.
There’s one more suggestion waiting in the wings, about applying such templates automatically (without even having to put {{||ProjectTemplate}} in the text field)… but I think that’s less important than getting a feel for how transclusion with templates can give HUGE powers to TiddlyWiki.