fix: images

Signed-off-by: Hélia Barroso <[email protected]>

Author: heliapb

docs/assets/images/blog/community-dashboards/perses-dashboards-am.png

@@ -44,7 +44,7 @@ This approach also lowers the barrier to achieving consistency across dashboards
 
 ## How to build composable dashboards - a practical example
 
-Here we have an example of how to define a panel of Time Series type below. More detailed info about the available option for Time Series Panels can be found [here](https://perses.dev/perses/docs/dac/go/panel/time-series/).
+Here we have an example of how to define a panel of Time Series type below. More detailed info about the available option for Time Series Panels can be found [here](https://pkg.go.dev/github.com/perses/perses/go-sdk/panel/time-series) and [PromQLBuilder](https://pkg.go.dev/github.com/perses/promql-builder).
 
 ```go
 // Define your panel
@@ -130,6 +130,8 @@ func BuildWorkloadOverview(project string, datasource string, clusterLabelName s
 }
 ```
 
+For more on the SDK please check [perses/go-sdk](https://pkg.go.dev/github.com/perses/perses/go-sdk), and [community-dashboards](https://pkg.go.dev/github.com/perses/community-dashboards).
+
 ## Beyond Copy-Pasting - Cleaner and Smarter way to building Dashboards
 
 Going back to the idea of copy-pasting raw YAML or JSON, although it might seem quicker, it leads to painful maintenance over time. The Go SDK offers a better path: