|« [PHOENIX] Specify permissions on a group base||comment-switch for categories »|
Here's how MT handles the thing.
We need compatibility with that as a minimum.
# Entry Body
# Extended Entry
Collectively these two fields make up the body of your entry. You can use the two fields however you like: you could split up your entry over the two fields, or you could completely ignore the Extended Entry text and enter only the Entry Body text. Movable Type allows you to split up your entry for more flexibility in the display of that entry; for example, if you write very long entries, you may not want your entire entry on your index pages. You can use the two fields to control what gets displayed, and where.
You can enter an excerpt from your entry, or use this field to provide a summary of the content therein. If you do not provide an excerpt, it will be automatically generated (when specified in a template using the MTEntryExcerpt tag) by selecting the first twenty (20) words from your entry, followed by an ellipsis.
i like more the way b2evo is doing. it’s more flexible.
if you don’t want to have the full entry at the index page you can use <!–more–>
so there’s no need for two input fields.
the excerpt, well, could be nice sometimes…
but i really the possibilities b2evo have: more, page, …
damn, forgotten something.
for the import script you just need to take entry_body, add the more-tag and add then extended_entry. and voilà, there’s the whole content in only one field. still no need for two :-)
well, i should also be possible with excerpt.
content = excerpt + teaser-tag + entry_body + more-tag + extended_entry.
still only one field, no changes needed for the database.
I think entry_body + more-tag + extended_entry is good.
The excerpt however, I see it a summary/teaser that does not fit into the post flow and would be better in a separate field.
Btw, kiesow, impelmenting this does not remove any of the existing features of b2evo.