Flag indicating manual vs auto summary generation

support
10

After a bit more thinking on this:

Current behavior is bad designed, because it’s conflicting with principle of least astonishment. In some cases you get fancy markdown and in other cases you get ugly flattened text as output. Very frustrating.

Use case: post list in blog. I need to show posts in a fancy way, and still being able to cut them when needed.

Use case: archive/sitemap or feed of announcements. I need a flattened text of given length.

Solution as I see it:

  • .Summary or .TruncatedContent or something like that - returns full content or part of it before <!--more-->;

  • Function, similar to Render, that returns flattened text of given length in words or symbols.

Still not solved an issue when people need more control on what part of a post should be cut. After using PmWiki for a while, I get used to idea of marking up ranges of content and accessing them by names. Not sure how it will work on top of markdown. Something like <!--range mysummary start--> … <!--range mysummary end-->.