facundoolano / jorge

jorge is a personal site generator with org-mode support
https://jorge.olano.dev/
GNU General Public License v3.0
47 stars 1 forks source link

Expose post.content as a template variable in addition to post.excerpt #40

Closed ILoveLinux666 closed 2 days ago

ILoveLinux666 commented 5 days ago

Hello, Thank you for writing this nice org mode ssg. I have a question. Is it possible to embed full post content in the description portion of feed.xml? From what I've read in the docs only post.excerpt is exposed, not post.content for example. It would allow the user to read the post without having to leave their rss reader.

facundoolano commented 4 days ago

post.content is not currently exposed but it should, I'll add it in my next round of updates to this project.

facundoolano commented 2 days ago

@ILoveLinux666 opened a PR with the update, do you mind trying it out and see if it works as you expected?

ILoveLinux666 commented 2 days ago

I believe it works!! I need to tweak the feed.xml to represent the new paragraphs and formatting stuff better, but the post.content works. Thank you! I will also try out #42 because i host my website on an openbsd vps using httpd and had to implement a workaround for a similar issue.

ILoveLinux666 commented 2 days ago

Also I noticed that the xmlns="http://www.w3.org/2005/Atom" property for the feed tag gets removed when the feed is build. According to the atom standard wikipedia it should be present. I hope I'm not to nitpicky 🥺.

facundoolano commented 2 days ago

Also I noticed that the xmlns="http://www.w3.org/2005/Atom" property for the feed tag gets removed when the feed is build. According to the atom standard wikipedia it should be present. I hope I'm not to nitpicky 🥺.

Can you give me some steps to reproduce that? my target/feed.xml looks ok

<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"> ...
facundoolano commented 2 days ago

I will also try out #42 because i host my website on an openbsd vps using httpd and had to implement a workaround for a similar issue.

Let me know how it goes, I'll merge the PR and publish a new version afterwards.