diff --git a/pgml-cms/blog/the-1.0-sdk-is-here.md b/pgml-cms/blog/the-1.0-sdk-is-here.md
index 76534f4e0..59f83252f 100644
--- a/pgml-cms/blog/the-1.0-sdk-is-here.md
+++ b/pgml-cms/blog/the-1.0-sdk-is-here.md
@@ -2,10 +2,22 @@
description: >-
Our official pgml SDK has been stabilized and released for Python and
JavaScript.
+featured: false
+tags: [product]
---
# The 1.0 SDK is Here
+
+
+
+
+
+
+Silas Marvin
+
+March 4, 2023
+
## Announcing the Release of our Official PGML 1.0 SDK
We have spent the last few months stabilizing and finalizing the 1.0 version of our SDK in both JavaScript and Python.
@@ -20,7 +32,7 @@ This release comes with a bunch of performance improvements and new features. To
Our SDK has been built specifically with the task of searching in mind. [We use it power the search on our own website](https://github.com/postgresml/postgresml/blob/6ba605d67016a1177d410d1eb91ae8763b4784c4/pgml-dashboard/src/utils/markdown.rs#L1243), [and to perform RAG with our ChatBot demo](https://github.com/postgresml/postgresml/blob/b3b5f03eb6c54bec88120617d5175279273d81d1/pgml-dashboard/src/api/chatbot.rs#L527).
-### Why It's Exciting
+## Why It's Exciting
Our SDK is no different from any other companies. It abstracts away some complexities of managing SQL tables, building complex queries, and other boring and repetitive tasks, but the SDK itself is not groundbreaking.
diff --git a/pgml-dashboard/src/api/cms.rs b/pgml-dashboard/src/api/cms.rs
index 3f49a934f..73fcbfe81 100644
--- a/pgml-dashboard/src/api/cms.rs
+++ b/pgml-dashboard/src/api/cms.rs
@@ -26,6 +26,7 @@ lazy_static! {
"Blog",
true,
HashMap::from([
+ ("the-1.0-sdk-is-here", "the-1.0-sdk-is-here"),
("announcing-hnsw-support-in-our-sdk", "speeding-up-vector-recall-5x-with-hnsw"),
("backwards-compatible-or-bust-python-inside-rust-inside-postgres/", "backwards-compatible-or-bust-python-inside-rust-inside-postgres"),
("data-is-living-and-relational/", "data-is-living-and-relational"),
pFad - Phonifier reborn
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.
