search

tobimori / kirby-seo

🔎 All-in-one toolkit that makes implementing SEO & Meta best practices in your Kirby 4+ site a breeze
https://plugins.andkindness.com/seo
MIT License
82 stars 10 forks source link

query language in description fields #64

Closed jaro-io closed 8 months ago

jaro-io commented 8 months ago

hey there tobi ✨ really cool plugin we have here!

it would be amazing if query language would be enabled for the description fields as well. is this something that could be added in a future version? my blog posts anyway have a summary field, so ideally i could just write {{ page.summary }} in the description field in order to use it.

🙏🏻

tobimori commented 8 months ago

I do not plan to make more use of KQL in the plugin. It's hard to understand for content editors, impossible to debug from inside the panel and should be the responsibility of the developer, and in my opinion therefore belongs in a page model with programmatic content (docs will follow but you can look at other issues for more details).

I should probably remove the title template KQL notice in 1.0 as well - the feature will stay as a side product of allowing {{ title }} as replacement.

tobimori commented 8 months ago

I asked on Discord what the community things of this and might reconsider it if I get enough positive feedback.

tobimori commented 8 months ago

Another thing to consider:

Most cases where this would be useful, it's hard to actually use this because of how the cascade works.

In order to set the description to a different field for all article pages, i'd have to set the description with KQL on the parent page and allow inheritation.

This also means that my blog page uses the same description but probably doesn't have the same field available, and I couldn't set a different one just for the parent/blog page (like with the title template, where I can select whether the current page uses the template or not as a workaround)

jaro-io commented 8 months ago

hey again 🌳 thanks for getting back to me so quicky!

i didnt know about the page model solution. just found it in one of the other issues like you explained. so that helps a lot, thanks!

and thinking about it again, i do agree regarding kql. i am currently working on my personal site, and in this case i wouldn’t mind having the additional options that kql enables. but you are totally right, most of the times metadata will be edited by content editors, not the dev. and in this case it can indeed be very confusing.

i am therefore withdrawing my request again haha. anyway, thanks a lot for looking into this! 🌻 ✨