Add Project Teasers: Plain text instead of html field and limitation to a few sentences

[jstet]

The field currently called "Summary" should be called "Teaser" instead and not be a html field. It's comparable to the teaser of blog articles. It should be only a few sentences and not contain html.

To change this however, we would need to write some code that copies the text without html tags from the old field to a new field.

@friep do you agree?

[pr130]

I see the problem. However, we do have a few projects that will never get an extensive description (in the sense of "problem", "data", "approach", "impact") but have a summary that is a) longer and b) includes links to outputs etc.

in addition, i like having the summary as an extra field because it's the amount of text that could be used for a longer report etc. so it'd be good to have API access to it (and not include it in the description).

finally, right now, there is no real common approach on how to start the summary so that it makes sense to be used as a "teaser" (i.e. some summaries just start very general and do not "tease" the reader).

My suggestion:

• keep summary field
• add new teaser field that really is a teaser/fits the preview (i.e. one sentence) -> i'll go through the projects and generate those teasers using chatgpt ;)

[jstet]

Sounds good to me. I'll add the teaser field!

[jstet]

@friep so once you have added content to this field for all projects, I will change the logic of project db so that it displays the teaser in the cards and at the top if the sub page. I will also work on #632 ; displaying the summary as the main text of sub pages when there is no description.