Skip to main content
added 94 characters in body
Source Link
Clive Portman
  • 2.9k
  • 19
  • 36

I'm using Matrix to give loads of flexibility with blog posts, but it means things aren't as simple when it comes to RSS than if just using a single field called Body.

How is everyone else dealing with this?

EDIT: As Christian points out, I'm party asking what is best practice for RSS feeds. But I'm also exploring the extra flexibility or complexibility offered by using Matrix for blog post content. Best practice is constantly evolving, and I think it quite possible best practice for creating an RSS feed using Craft may turn out to be different best practice to feeds generated by something else, simply because the flexibility is there (just as long-form content is becoming more commonplace as CMSs start to deal with it better). For example, using Matrix we can pick and choose which types of content are included within the feed to a much greater degree. Or do we just say, no, a feed should contain this, this and this and you shouldn't mess with that, no matter what the tool?

I'm using Matrix to give loads of flexibility with blog posts, but it means things aren't as simple when it comes to RSS than if just using a single field called Body.

How is everyone else dealing with this?

EDIT: As Christian points out, I'm party asking what is best practice for RSS feeds. But I'm also exploring the extra flexibility or complexibility offered by using Matrix for blog post content. Best practice is constantly evolving, and I think it quite possible best practice for creating an RSS feed using Craft may turn out to be different best practice to feeds generated by something else, simply because the flexibility is there. For example, using Matrix we can pick and choose which types of content are included within the feed to a much greater degree. Or do we just say, no, a feed should contain this, this and this and you shouldn't mess with that, no matter what the tool?

I'm using Matrix to give loads of flexibility with blog posts, but it means things aren't as simple when it comes to RSS than if just using a single field called Body.

How is everyone else dealing with this?

EDIT: As Christian points out, I'm party asking what is best practice for RSS feeds. But I'm also exploring the extra flexibility or complexibility offered by using Matrix for blog post content. Best practice is constantly evolving, and I think it quite possible best practice for creating an RSS feed using Craft may turn out to be different best practice to feeds generated by something else, simply because the flexibility is there (just as long-form content is becoming more commonplace as CMSs start to deal with it better). For example, using Matrix we can pick and choose which types of content are included within the feed to a much greater degree. Or do we just say, no, a feed should contain this, this and this and you shouldn't mess with that, no matter what the tool?

added 665 characters in body
Source Link
Clive Portman
  • 2.9k
  • 19
  • 36

I'm using Matrix to give loads of flexibility with blog posts, but it means things aren't as simple when it comes to RSS than if just using a single field called Body.

How is everyone else dealing with this?

EDIT: As Christian points out, I'm providing a summaryparty asking what is best practice for each post withinRSS feeds. But I'm also exploring the extra flexibility or complexibility offered by using Matrix for blog post content. Best practice is constantly evolving, and I think it quite possible best practice for creating an RSS feed using Craft may turn out to be different best practice to feeds generated by something else, butsimply because the flexibility is it betterthere. For example, using Matrix we can pick and choose which types of content are included within the feed to delivera much greater degree. Or do we just say, no, a feed should contain this, this and this and you shouldn't mess with that, no matter what the full posttool?

I'm using Matrix to give loads of flexibility with blog posts, but it means things aren't as simple when it comes to RSS than if just using a single field called Body.

How is everyone else dealing with this? I'm providing a summary for each post within the feed, but is it better to deliver the full post?

I'm using Matrix to give loads of flexibility with blog posts, but it means things aren't as simple when it comes to RSS than if just using a single field called Body.

How is everyone else dealing with this?

EDIT: As Christian points out, I'm party asking what is best practice for RSS feeds. But I'm also exploring the extra flexibility or complexibility offered by using Matrix for blog post content. Best practice is constantly evolving, and I think it quite possible best practice for creating an RSS feed using Craft may turn out to be different best practice to feeds generated by something else, simply because the flexibility is there. For example, using Matrix we can pick and choose which types of content are included within the feed to a much greater degree. Or do we just say, no, a feed should contain this, this and this and you shouldn't mess with that, no matter what the tool?

question has nothing to do with matrix directly
Link
carlcs
  • 36.3k
  • 5
  • 63
  • 140

Populating an RSS feed with Matrixfull post content?

Improving the question
Source Link
Clive Portman
  • 2.9k
  • 19
  • 36
Loading
Source Link
Clive Portman
  • 2.9k
  • 19
  • 36
Loading