this is a duplicate; it's being addressed in improve interface around content view inclusions. Let's keep it anyway as the title is a better description, and we may find that by 1.0 this part is fixed but the other isn't.
note: the display:inline thing is a hack for what we're making work as default in 1.0
--Ethan McCutchen.....Sat Jan 24 15:45:30 -0800 2009
To copy&paste to nesting+tips, once that's been seen as an example of an emailed bug:
Sometimes you want to include a card of text in a sentence, for example:
Ethan McCutchen's favorite fruit is {{Ethan McCutchen+favorite fruit}}, currently.
...which will render as:
Ethan McCutchen's current favorite fruit is
, currently.
For this to work, the included card's cardtype must be PlainText or Phrase.
--John Abbe.....Sun Mar 01 02:28:41 -0800 2009
Strangely, Ethan McCutchen+favorite fruit is a Fruit (i.e., RichText), but it shows as inline. But but, i can't replicate that at http://sandwagn.wagn.org/wagn/keep_display_inline_on_one_line+example
??
--John Abbe.....Sun Mar 01 04:33:30 -0800 2009
So technically how it works is that all of the cardtypes are included inline, but some of them tend to have block elements inside them. For example, if you create a Basic card and type "howdy", it will actually be stored inside "p" tags. If you manage to edit the HTML block tags out, then it will be inline, otherwise it won't.
--Ethan McCutchen.....Mon Mar 02 09:05:50 -0800 2009
Actually, even with the p tag, it's inline! See nesting+tips.
--John Abbe.....Thu Apr 30 00:06:54 -0700 2009
is this another placeholder for broader doc needs?
--Ethan McCutchen.....Tue Jun 02 14:20:38 -0700 2009