Blog index page without except

[x4Cx58x54]

This is a feature request for the minimalist bloggers: adding a none option for blog.post_excerpt for those who want only their post titles show on the index page, which means removing the post excerpt and the "continue reading" link.

[alexvoss]

This should be possible to achieve with customization. You can simply hide the excerpt and the link below it by setting them to display: none in extra.css. Material for MkDocs is highly customizable and it is not possible to add everything people might need as a selectable option.

[x4Cx58x54]

Thank you for answering. Yes I have tried hiding the excerpt using css. However the element of post titles and post contents in the excerpts are in the same html level, thus difficult to apply selectors to the contents in a neat and clean implementation.

[alexvoss]

How about this? It is probably not a full solution as you may want to reduce the whitespace but should get you started:

article.md-post--excerpt p, article.md-post--excerpt nav {
  display: none;
}

[mfridman]

Ye, this would be a nice quality-of-life improvement (although I suspect you could do this with a custom template by category, I need to remember how that works).

To add another data point, I have a blog split into sections (by category): Articles, Fragments, Snippets, etc. And for different categories, I'd like to have different behaviour.

For Articles, I'd like to display the blog excerpt, but for Snippets, I only want a title. Going down the .css route it's an all-or-nothing change.

I could add <!-- more --> but then it'll still have a new line with a "Continue reading".

[squidfunk]

Unfortunately, this might lead to content shift on slow connections, because the content is visible, until the JavaScript runs and it isn't. IMHO this should be done in the template, not in JavaScript 😉

[squidfunk]

@mfridman you can use a combination of custom index pages for your categories and a custom template. For example, say you have the categories foo and bar, then your file layout could look like this:

.
├─ overrides/
│  ├─ blog-category-foo.html
│  └─ blog-category-bar.html
├─ docs/
│  └─ blog/
│     ├─ category/
│     │  ├─ foo.md 
│     │  └─ bar.md 
│     ├─ posts/
│     └─ index.md
└─ mkdocs.yml

In mkdocs.yml:

theme:
  name: material
  custom_dir: overrides

In foo.md:

---
template: blog-category-foo.html
---

# Welcome to Foo!

Custom content

<!-- Blog posts will be appended here -->

Same goes for bar.md. The idea is that you override the blog.html in blog-category-foo.html (and subsequently blog-post.html, as that's the partial that is used for rendering the excerpts). I understand that this is a little more involved, but before adding additional rendering options, we'd like to learn about the common patterns that people use to build their blogs.

[mfridman]

Thanks for the example, that's exactly the route I was going down. I also think it's a fair tradeoff for users who want more customization.

Many suggestions (like this discussion) add complexity, and overhead, and are quite subjective. Seems like the 80/20 principle, where simpler solutions will generally suffice for most users. I like your approach of waiting and getting feedback.

[mfridman]

Fwiw this turned out nicely (screenshot is what I was going for), I might do a write-up in case anyone else runs into this (or my future self, hehe).

[squidfunk]

Love it!