How should I model large bodies of textual content in a django app?
Storing the body of the post in the database shouldn't be an issue. Most blog engines take this approach. It'll be faster than storing it in a separate model (if it's in a separate model, you'd have to do a JOIN to get the body), and likely faster than storing it as a file on the file system. You're not using the body as a primary key, so the length doesn't really matter.
This is a question about best-practice for modelling a Django app. The project is a blog which will present articles written in something similar to Markdown or RST. 
I've checked out a few tutorials to give me some sort of starting point and so far they all store the body of the article in the model. This seems wrong: my understanding of modern database engines isn't the best but storing textfields of arbitrary lengths can't be good for performance.
Three alternatives present themselves:

Limit the article model to metadata and create a separate model to
store the body of an article. At least only one table is a mess!
Limit the article model to metadata and store the article body as a
static file.
Ask someone with more experience. Maybe storing the body in the model
isn't so bad after all... at least it's easily searchable!

How should I model this app? How would you make your solution searchable?