Conversation
|
Cool! This was the solution I initially considered, but out of concern that it might introduce breaking changes to the plugin, I switched to a milder and more transparent/controllable API design. Of course, this is already sufficient for my needs. |
|
Just to add, as far as I know, in SEO, some meta tags are allowed or required to be duplicated, such as og:image. Therefore, if it were up to me, I would want to control whether a replacement is needed myself. I initially set the replace parameter as a boolean, but then I thought there might be some edge cases that aren't necessarily controlled by name/property/the first parameter, and there might be more complex replacement rules. So, I ultimately chose the CSS selector approach, which I find more elegant. The above is just for your reference~ |
Know of any situations in which it'd be required? I'm not aware of any, but good shout re:allowed. I really don't love supporting this though, I might just recommend using a post-build script or writing a plugin to rewrite the HTML in user land. Overwriting meta tags isn't really something I want to deal with. |
|
Yes, I have actually dealt with this situation. Since different social media platforms have different optimal dimensions for image previews, it is sometimes necessary to use multiple |
|
However, I can also perfectly understand your desire to keep this plugin simple. This is just a small suggestion from me as a user, and I hope you’ll give it some careful consideration. |
2 participants
No description provided.