When inserting lots of contents by copying from e.g. PDFs or word documents (well, clients…) it would be great to have something like an optional filter method to “sanitize” the copied text to markdown – especially when there are clusters which are repeating the whole time, this could save couple of minutes/hours… (e.g. exchange strange list symbols, tabs etc. with "- ").
I agree. Actually, there have been a few projects in which I would have liked to implement some kind of custom functionality for my customers (e. g. approving comments). Custom views/controllers for the panel and dashboard widgets would be great in order to give everyone the possibility to extend the panel in a simple way.
Further, it would be great to be able customize all page-related labels on a per-template basis. This would make the panel even easier to use for non-tech-savy customers.
Unfortunately it doesn’t seem to be working for me and actual my language codes de-de, de-ch, en. I thought it might be about the hyphen not being valid in identifiers, but changing it to a underscore doesn’t help (apart from the fact that renaming all content files is quite off-putting…)
To conceptualize this further: What would you like to happen with the data? I assume it would stay the same for fields with the same name. What about fields that do not exist anymore in the new template/blueprint? Threw the data away or keep it in the context file for the case that you want to switch back? What about fields with the same name, but different form types (e.g. textarea in the old, select in the new)?
I’d rather keep the data of fields that do not exist in the new template, in case I wanted to switch back. As regards fields with the same name, I don’t know what would work best without breaking anything. That would depend on the content, so maybe keeping the original content but validate upon saving?
But yeah, there is no container div for such “groups”, so the js may be a bit tricky and fragile.
I created a replacement for the headline field that groups all content until the next headline field in an accordion. There’s no special instructions or syntax. Simply create a headline for each content group / section you want and it should work. Let me know if you find any issues.