diff --git a/website/docs/sdks/proxy-react.md b/website/docs/sdks/proxy-react.md
index c1876d792a..fd69afe17c 100644
--- a/website/docs/sdks/proxy-react.md
+++ b/website/docs/sdks/proxy-react.md
@@ -14,7 +14,7 @@ For more detailed information, check out [the React Proxy SDK on GitHub](https:/
npm install @unleash/proxy-client-react
```
-## Initialize the client
+## Initialization
The snippet below shows you how to initialize the client. We recommend that you do this in your entry point file (typically index.js/ts) to ensure that you only have _one_ instance of it.
diff --git a/website/docs/sdks/proxy-svelte.md b/website/docs/sdks/proxy-svelte.md
new file mode 100644
index 0000000000..c3e24722b5
--- /dev/null
+++ b/website/docs/sdks/proxy-svelte.md
@@ -0,0 +1,196 @@
+---
+id: proxy-svelte
+title: Svelte proxy SDK
+---
+
+
+ Svelte proxy SDK is currently at version 0.0.2 and is experimental.
+
+
+
+This library is meant to be used with the [unleash-proxy](https://github.com/Unleash/unleash-proxy). The proxy application layer will sit between your unleash instance and your client applications, and provides performance and security benefits. DO NOT TRY to connect this library directly to the unleash instance, as the datasets follow different formats because the proxy only returns evaluated toggle information.
+
+For more detailed information, check out [the svelte Proxy SDK on GitHub](https://github.com/Unleash/proxy-client-svelte).
+
+## Installation
+
+```shell npm2yarn
+npm install @unleash/proxy-client-svelte
+```
+
+## Initialization
+
+Import the provider like this in your entrypoint file (typically index.svelte):
+
+```html
+
+
+
+
+
+```
+
+Alternatively, you can pass your own client in to the FlagProvider:
+
+```html
+
+
+
+
+
+```
+
+## Deferring client start
+
+By default, the Unleash client will start polling the Proxy for toggles immediately when the `FlagProvider` component renders. You can delay the polling by:
+
+- setting the `startClient` prop to `false`
+- passing a client instance to the `FlagProvider`
+
+```html
+
+
+
+```
+
+Deferring the client start gives you more fine-grained control over when to start fetching the feature toggle configuration. This could be handy in cases where you need to get some other context data from the server before fetching toggles, for instance.
+
+To start the client, use the client's `start` method. The below snippet of pseudocode will defer polling until the end of the `asyncProcess` function.
+
+```html
+
+
+
+
+
+```
+
+## Usage
+
+## Check feature toggle status
+
+To check if a feature is enabled:
+
+```html
+
+
+{#if $enabled}
+
+{:else}
+
+{/if}
+```
+
+## Check variants
+
+To check variants:
+
+```html
+
+
+{#if $variant.enabled && $variant.name === 'SomeComponent'}
+
+{:else if $variant.enabled && $variant.name === 'AnotherComponent'}
+
+{:else}
+
+{/if}
+```
+
+## Defer rendering until flags fetched
+
+useFlagsStatus retrieves the ready state and error events.
+Follow the following steps in order to delay rendering until the flags have been fetched.
+
+```html
+
+
+{#if !$flagsReady}
+
+{:else}
+
+{/if}
+```
+
+## Updating context
+
+Follow the following steps in order to update the unleash context:
+
+```html
+
+```
\ No newline at end of file
diff --git a/website/docs/sdks/proxy-vue.md b/website/docs/sdks/proxy-vue.md
new file mode 100644
index 0000000000..4ceb737714
--- /dev/null
+++ b/website/docs/sdks/proxy-vue.md
@@ -0,0 +1,181 @@
+---
+id: proxy-vue
+title: Vue proxy SDK
+---
+
+
+ Vue proxy SDK is currently at version 0.0.1 and is experimental.
+
+
+
+This library is meant to be used with the [unleash-proxy](https://github.com/Unleash/unleash-proxy). The proxy application layer will sit between your unleash instance and your client applications, and provides performance and security benefits. DO NOT TRY to connect this library directly to the unleash instance, as the datasets follow different formats because the proxy only returns evaluated toggle information.
+
+For more detailed information, check out [the vue Proxy SDK on GitHub](https://github.com/Unleash/proxy-client-vue).
+
+## Installation
+
+```shell npm2yarn
+npm install @unleash/proxy-client-vue
+```
+
+## Initialization
+
+Import the provider like this in your entrypoint file (typically App.vue):
+
+```jsx
+import FlagProvider from '@unleash/proxy-client-vue'
+
+const config = {
+ url: 'https://HOSTNAME/proxy',
+ clientKey: 'PROXYKEY',
+ refreshInterval: 15,
+ appName: 'your-app-name',
+ environment: 'dev'
+}
+
+
+
+
+
+
+```
+
+Alternatively, you can pass your own client in to the FlagProvider:
+
+```jsx
+import FlagProvider, { UnleashClient } from '@unleash/proxy-client-vue'
+
+const config = {
+ url: 'https://HOSTNAME/proxy',
+ clientKey: 'PROXYKEY',
+ refreshInterval: 15,
+ appName: 'your-app-name',
+ environment: 'dev'
+}
+
+const client = new UnleashClient(config)
+
+
+
+
+
+
+```
+
+## Deferring client start
+
+By default, the Unleash client will start polling the Proxy for toggles immediately when the `FlagProvider` component renders. You can delay the polling by:
+
+- setting the `startClient` prop to `false`
+- passing a client instance to the `FlagProvider`
+
+```jsx
+
+
+
+
+
+```
+
+Deferring the client start gives you more fine-grained control over when to start fetching the feature toggle configuration. This could be handy in cases where you need to get some other context data from the server before fetching toggles, for instance.
+
+To start the client, use the client's `start` method. The below snippet of pseudocode will defer polling until the end of the `asyncProcess` function.
+
+```jsx
+const client = new UnleashClient({
+ /* ... */
+})
+
+onMounted(() => {
+ const asyncProcess = async () => {
+ // do async work ...
+ client.start()
+ }
+ asyncProcess()
+})
+
+
+
+
+
+
+```
+
+# Usage
+
+## Check feature toggle status
+
+To check if a feature is enabled:
+
+```jsx
+
+
+
+
+
+
+```
+
+## Check variants
+
+To check variants:
+
+```jsx
+
+
+
+
+
+
+
+```
+
+## Defer rendering until flags fetched
+
+useFlagsStatus retrieves the ready state and error events.
+Follow the following steps in order to delay rendering until the flags have been fetched.
+
+```jsx
+import { useFlagsStatus } from '@unleash/proxy-client-vue'
+
+const { flagsReady, flagsError } = useFlagsStatus()
+
+
+
+```
+
+## Updating context
+
+Follow the following steps in order to update the unleash context:
+
+```jsx
+import { useUnleashContext, useFlag } from '@unleash/proxy-client-vue'
+
+const props = defineProps<{
+ userId: string
+}>()
+
+const { userId } = toRefs(props)
+
+const updateContext = useUnleashContext()
+
+onMounted(() => {
+ updateContext({ userId })
+})
+
+watch(userId, () => {
+ async function run() {
+ await updateContext({ userId: userId.value })
+ console.log('new flags loaded for', userId.value)
+ }
+ run()
+})
+```
diff --git a/website/sidebars.js b/website/sidebars.js
index 63b6c4b2d2..ac9ee92f2d 100644
--- a/website/sidebars.js
+++ b/website/sidebars.js
@@ -202,6 +202,8 @@ module.exports = {
'sdks/proxy-ios',
'sdks/proxy-javascript',
'sdks/proxy-react',
+ 'sdks/proxy-vue',
+ 'sdks/proxy-svelte'
],
},
{