I suggest to keep description as a plain text summary and to put html content in content:encoded tag. See this for example:
I put full article in content:encoded for my blog even. Most feed readers can deal with MBs long feeds and my readers can see the full content without doing anything.
I wrote a bit of a rambling post about implementing a breakout clone in Elixir. For what it’s worth, there’s a post about the implementation itself as well.
How to efficiently manage multiple clients within a single application? Or how to keep different users’ data isolated while still leveraging shared resources?
Enter multi-tenancy!
How does AI “speak” and “understand”?
Check our latest blog to learn all about language modeling—the technology behind how AI interprets and generates human language.
Over the weekend I finished an article on how to create Elixir powered WordPress plugin using LiveState:
Have you ever wondered about the word use in use GenServer?
I wrote an article explaining how the use macro works and how to build modular and reusable systems: Understanding use and __using__ in Elixir | Doofinder Tech
I wrote an article on how to cache A/B tested pages with plug_http_cache: A/B testing and HTTP caching with plug_http_cache
And another one about caching Liveviews (part 1): Caching Liveviews - Part 1: The road to HTTP-caching Liveviews - Tangui's blog
I really like the post @njwest. The approach is great and really well explained!
Congrats!
