tzinm

I have run into the same issue with several feeds that I currently have in my Miniflux instance. More details on this issue can be found in the article title...

Thanks for your response! I hadn't considered lists before, as I'm still new to LinkAce and haven't explored all its features yet. From what I've read in the documentation, I...

Hi @tprouvot I’ve been using the extension for a long time and hadn’t noticed this option. It’s exactly what I was looking for. Quick access to the documentation. Thanks a...

What I have realised is that it only works with **standard objects**. I am working on a project in which we have implemented _Field Service_ for [inventory management](https://developer.salesforce.com/docs/platform/data-models/guide/field-service-inventory-management.html), where some...

Adding a `description` field to the frontmatter (plain text, without markdown syntax) and using **summary** would allow making a clear distinction: * Use the **summary** for the text displayed under...

No, I haven’t been able to test it directly. Anyway, some applications may display the Markdown summary correctly, while others don't. It depends (I think) on how they parse the...

This is how it works now ( besides the inconsistency between the **home page** and the **feed**). The displayed text, whether it's the `description` or the **summary**, is clean and...

It would be great to extend the functionality, but it seems fair at the moment to only make the change to be consistent with the homepage and feed. I'll take...

> Your main need to prioritise one over the other with a setting was the markdown parsing, or something else? Yes, it's just for visual aspects. As I had pointed...

> For your use-case, would you make the description and summary match, except one would have no markdown? I have considered it. But I don't think I like it. *...