Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rss feed #1343

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from
Open

Rss feed #1343

wants to merge 4 commits into from

Conversation

msamgan
Copy link

@msamgan msamgan commented Sep 20, 2023

PR for issue #1334

@msamgan
Copy link
Author

msamgan commented Sep 20, 2023

Once you get this one merged, if you merge. I will use this as a base for the sitemap.xml issue #1336.

@msamgan
Copy link
Author

msamgan commented Sep 26, 2023

I would like to request you to please close this PR.
Merge or Reject as you see fit.

@austintoddj austintoddj added the enhancement New feature or request label Sep 26, 2023
@foreach($posts as $post)
<item>
<title><![CDATA[{{ $post->title }}]]></title>
<link>{{ url($post->slug) }}</link>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Passing in the post slug is good, but we should be using the absolute path to the post - which can vary. Depending if someone wants their publication at: /blog, or /news, etc.

You could try to use this config value, but there could still be edge cases.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can have two approaches.

  1. we can ask the user to add the static path of the post in the config.
  2. we can make the feed view publishable, so if the user has a custom url he can configure the feed accordingly.

or we can do both.

what do you say about that ?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can ask the user to add the static path of the post in the config

I don't think specifying a static path per post is a good UX.

we can make the feed view publishable...configure the feed accordingly

Still a heavier lift than what I'd expect as a user. Essentially, I'd like to see it where you can provide a config value in your .env file - we'd also need to take into account other taxonomies (tags/topics) - and then a switch where you can either enable or disable the feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants