I’m currently building a site with WeWeb and facing an issue with dynamically generating Open Graph (OG) data. As you know, OG tags are crucial for controlling how content is shared across social platforms, yet I haven’t found an easy or built-in way to manage these dynamically in WeWeb.
Is there any plan or ETA for a better, more native solution to manage dynamic OG tags in WeWeb?
Are there any upcoming features or updates that will help address this issue?
I’ve gone through this: Dynamic page metadata | WeWeb Documentation, but to be honest, using workarounds like this completely misses the point of low-code tools. I might as well build my own site, invest a little more time, save money, and gain more control.
I read there was a closed beta test that concluded with the result that users don’t need dynamic metadata?
Were they testing the same workaround mentioned in the dynamic page metadata doc?
In this case, it seems more likely that users either didn’t like or didn’t know how to use the workaround provided, rather than not needing metadata.
How does it make sense that users would spend resources creating web pages but then not care about whether someone actually finds them?
Are you sure the sample represents the users you address with " Build production-grade web applications…"?
I don’t get the impression that WeWeb positions itself as a simple static page creation tool, so the fact that OG tags can be set on static pages doesn’t really help in this situation.
I’m hoping someone to tell me this rant wasn’t needed and I just missed the solutions, what I found, doesn’t seem to make any sense
I completely agree that having page titles, meta descriptions, and OG images on dynamic pages is crucial. Hopefully, WeWeb will prioritize resolving this or come up with a better solution that doesn’t require creating a custom GitHub fork.
Toddle has managed to figure it out, so I’m hopeful WeWeb can stay ahead of the curve!
We prioritize things that are in our roadmap and we don’t suddenly change it for a particular user unless we think we should. If you want to post something in the community, please try to post something that will actually help users solve issues.
@danlopes I completely understand, my intention was to be helpful by confirming to @Paul27 that the Cloudflare issue he and others are currently experiencing was recently addressed in another post by the WeWeb team and is being worked on.
I don’t expect you to adjust your roadmap because of Paul, myself, or others facing this issue. I just wanted to voice my support for the eventual fix to a feature/documented workaround that has already been released, especially considering the publicly announced reason for de-prioritizing this functionality was due to a lack of interest. We all love WeWeb and only want the best for the platform.
@danlopes it seems that the static Open Graph is not working either? Or could there be a delay in setting it up in WeWeb and before social medias see it?
