solara 1.29.1__py2.py3-none-any.whl → 1.30.0__py2.py3-none-any.whl

solara/website/pages/{docs/content/04-tutorial → documentation/getting_started/content/04-tutorials}/20-web-app.md

@@ -5,7 +5,7 @@ In this tutorial, you will learn how to use Solara to create a tiny web app usin
 ## You should know
 This tutorial will assume you have successfully installed Solara.
 
-If not, please follow the [Installation guide](/docs/installing).
+If not, please follow the [Installation guide](/documentation/getting_started/installing).
 
 ## Generate a script file
 The simplest way to get started is to run the command
@@ -40,7 +40,7 @@ def Page():
 
 ## Run the script
 
-Using [Solara server](/docs/understanding/solara-server), we can now run our Python script using:
+Using [Solara server](/documentation/advanced/understanding/solara-server), we can now run our Python script using:
 
 ```bash
 $ solara run sol.py
@@ -50,7 +50,7 @@ Solara server is starting at http://localhost:8765
 If you open the URL in your browser ([or click here](http://localhost:8765)), you should see the same example as above.
 
 Solara will run your script once, and will look for the `Page` component. Solara expects this component to exist
-and be a [Reacton](/docs/understanding/reacton) component. (See the [IPywidget tutorial](/docs/tutorial/ipywidgets) to learn how to render a regular ipywidget).
+and be a [Reacton](/documentation/advanced/understanding/reacton) component. (See the [IPywidget tutorial](/documentation/getting_started/tutorials/ipywidgets) to learn how to render a regular ipywidget).
 
 Since your script is only run once, you could put in the main body of your script code that only needs to run once (e.g. loading data from disk)
 
@@ -68,7 +68,7 @@ Lets modify the script a little bit, possibly in this way:
 ```
 
 If we save the script, Solara will automatically reload your script and update
-your browser (we call this feature [hot reloading](/docs/reference/reloading)).
+your browser (we call this feature [hot reloading](/documentation/getting_started/reference/reloading)).
 
 Note that Solara will remember your state (e.g., the number of buttons clicked) when the app reloads.
 

solara/website/pages/{docs/content/04-tutorial → documentation/getting_started/content/04-tutorials}/30-ipywidgets.md

@@ -1,15 +1,15 @@
 # Tutorial: IPywidgets
 
-If you are already using [ipywidgets](/docs/understanding/ipywidgets) in the notebook, possibly using [Voila](/docs/understanding/voila), you might be pleased to know that you
-can also use the [Solara server](/docs/understanding/solara-server) to render your regular ipywidget application.
+If you are already using [ipywidgets](/documentation/advanced/understanding/ipywidgets) in the notebook, possibly using [Voila](/documentation/advanced/understanding/voila), you might be pleased to know that you
+can also use the [Solara server](/documentation/advanced/understanding/solara-server) to render your regular ipywidget application.
 
-We recommend you learn how to write applications using [Reacton](/docs/understanding/reacton). However, if you have already written an application in
-pure [ipywidgets](/docs/understanding/ipywidgets), this approach will let you gradually move from pure ipywidgets to Reacton.
+We recommend you learn how to write applications using [Reacton](/documentation/advanced/understanding/reacton). However, if you have already written an application in
+pure [ipywidgets](/documentation/advanced/understanding/ipywidgets), this approach will let you gradually move from pure ipywidgets to Reacton.
 
 ## You should know
 This tutorial will assume you have successfully installed Solara.
 
-If not, please follow the [Installation guide](/docs/installing).
+If not, please follow the [Installation guide](/documentation/getting_started/installing).
 
 ## Your first ipywidget based Solara app
 
@@ -70,10 +70,10 @@ Try making the following code change (remove the first, add the last), and watch
 
 ## Using Solara components
 
-There are a lot of [valuable components in Solara](/api), but they are written as [Reacton/Solara components](/docs/understanding/reacton-basics), not
+There are a lot of [valuable components in Solara](/documentation/components), but they are written as [Reacton/Solara components](/documentation/advanced/understanding/reacton-basics), not
 classic ipywidgets.
 
-Use the [.widget(...)](/api/widget) method on a component to create a widget that can be used in your existing classic ipywidget application.
+Use the [.widget(...)](/documentation/api/utilities/widget) method on a component to create a widget that can be used in your existing classic ipywidget application.
 
 ```python
 
@@ -111,10 +111,10 @@ Note that we did not include the `:page` here, since solara will automatically l
 
 ## What you have learned
 
-  * [Solara server](/docs/understanding/solara-server) can render [ipywidgets](/docs/understanding/ipywidgets).
+  * [Solara server](/documentation/advanced/understanding/solara-server) can render [ipywidgets](/documentation/advanced/understanding/ipywidgets).
   * Running `$ solara run filename.py:variablename` tells Solara which script to execute and which variable name from the script to render.
   * The script is executed:
     * Once, when the solara server starts.
     * On each page request.
     * For each open browser page/tab, when the script is saved (hot reloading).
-  * Using the [.widget(...)](/api/widget) method we can start using Solara components in classic ipywidget app.
+  * Using the [.widget(...)](/documentation/api/utilities/widget) method we can start using Solara components in classic ipywidget app.

solara/website/pages/{docs/content/04-tutorial → documentation/getting_started/content/04-tutorials}/40-streamlit.md

@@ -18,8 +18,8 @@ st.markdown(f"{x} squared = {x_squared}")
 
 ## Translated to Solara
 
-We now translate this to the equivalent in Solara. The largest difference is we need to explicitly create (application) state using [`solara.reactive`](/api/reactive). By passing the
-reactive variable to the [SliderInt](/api/slider) via `value=x` we set up a two way binding between the component and the reactive variable. The generated text is passed down to the [Markdown](/api/markdown) component.
+We now translate this to the equivalent in Solara. The largest difference is we need to explicitly create (application) state using [`solara.reactive`](/documentation/api/utilities/reactive). By passing the
+reactive variable to the [SliderInt](/documentation/components/input/slider) via `value=x` we set up a two way binding between the component and the reactive variable. The generated text is passed down to the [Markdown](/documentation/components/output/markdown) component.
 
 
 ```solara
@@ -49,7 +49,7 @@ You will see:
 
 Because we do some styling and because the sidebar is already used up, our preview on this page looks slightly different.
 
-[Navigate to /apps/tutorial-streamlit](/apps/tutorial-streamlit) to see this app fullscreen.
+[Navigate to /apps/tutorial-streamlit](/documentation/examples/fullscreen/tutorial_streamlit) to see this app fullscreen.
 
 
 ### Running this example in the notebook
@@ -61,7 +61,7 @@ Again, slightly different for a different environment.
 
 ## Hot reloading
 
-If you are using [Solara server](/docs/understanding/solara-server), try editing `sol.py`, and watch the page reload automatically after you save your file. Notebook users can simply edit and re-run.
+If you are using [Solara server](/documentation/advanced/understanding/solara-server), try editing `sol.py`, and watch the page reload automatically after you save your file. Notebook users can simply edit and re-run.
 
 (*Note: Upgrade to solara 1.14.0 for a fix in hot reloading using `pip install "solara>=1.14.0"`*)
 
@@ -69,13 +69,13 @@ If you are using [Solara server](/docs/understanding/solara-server), try editing
 
 ### Execution model
 As the introduction says, Solara does not re-execute your whole script after user interactions.
-The main script is executed only once. With Solara you can use your main script to read large dataframes, or do some pre-calculations without the need for [caching](/docs/reference/caching).
+The main script is executed only once. With Solara you can use your main script to read large dataframes, or do some pre-calculations without the need for [caching](/documentation/getting_started/reference/caching).
 
-When a user navigates to a Solara server, the `Page` component (basically a function) will get executed. The `Page` component will call (lazily) new components like [solara.Markdown](/api/markdown) to build up the page. If state changes due to user input, Solara will trigger a cascade of re-excecutions of components which inputs or state changed, but never your whole script, nor every component.
+When a user navigates to a Solara server, the `Page` component (basically a function) will get executed. The `Page` component will call (lazily) new components like [solara.Markdown](/documentation/components/output/markdown) to build up the page. If state changes due to user input, Solara will trigger a cascade of re-excecutions of components which inputs or state changed, but never your whole script, nor every component.
 
 ### State
-With Solara (and [Reacton](/docs/understanding/reacton)) state does not live in a UI component (like a slider). Application state created with [`solara.reactive`](/api/reactive) lives on its own. Connecting the state to the UI component (in this case a slider) is a separate step, done via `value=x` in the above example. In general we recommend organising your components
-similarly as in the example: [First use_state and other hooks, then calculations, at last the UI components](/docs/understanding/anatomy).
+With Solara (and [Reacton](/documentation/advanced/understanding/reacton)) state does not live in a UI component (like a slider). Application state created with [`solara.reactive`](/documentation/api/utilities/reactive) lives on its own. Connecting the state to the UI component (in this case a slider) is a separate step, done via `value=x` in the above example. In general we recommend organising your components
+similarly as in the example: [First use_state and other hooks, then calculations, at last the UI components](/documentation/advanced/understanding/anatomy).
 
 For complex situations, it is important to separate the state and the UI. Especially when you need the state of a UI component as input of the UI component itself, you can get stuck with streamlit. In Solara this follows naturally.
 
@@ -83,8 +83,8 @@ For complex situations, it is important to separate the state and the UI. Especi
 ## Creating a reusable component
 
 
-A big advantage of Solara is that you can create reusable components. A single component can be seen as the equivalent of a single streamlit script. However, in that case, we need to modify our component to have its own state, rather than using global application state, for this you can use the [`use_reactive`](/api/use_reactive), or [`use_state`](/api/use_state) hook.
-Read more about state management in the [state management](/docs/fundamentals/state-management) section.
+A big advantage of Solara is that you can create reusable components. A single component can be seen as the equivalent of a single streamlit script. However, in that case, we need to modify our component to have its own state, rather than using global application state, for this you can use the [`use_reactive`](/documentation/api/hooks/use_reactive), or [`use_state`](/documentation/api/hooks/use_state) hook.
+Read more about state management in the [state management](/documentation/getting_started/fundamentals/state-management) section.
 
 ```solara
 import solara
@@ -129,8 +129,8 @@ Changing that "y" to "x" will lead to an error, however. If this is a problem in
 
 ### Long running function
 
-In Streamlit, it is normal for your main script to block execution. In Solara, the functions bodies of your components ([called render functions](/docs/understanding/anatomy)) should not block. Functions that block, or take a long time to execute, should be executed in a thread, such that rendering can continue. Using threads may sound scary, but using the
-[use_thread](/api/use_thread) hook will help a lot.
+In Streamlit, it is normal for your main script to block execution. In Solara, the functions bodies of your components ([called render functions](/documentation/advanced/understanding/anatomy)) should not block. Functions that block, or take a long time to execute, should be executed in a thread, such that rendering can continue. Using threads may sound scary, but using the
+[use_thread](/documentation/api/hooks/use_thread) hook will help a lot.
 
 ## What you have learned
 
@@ -138,4 +138,4 @@ In Streamlit, it is normal for your main script to block execution. In Solara, t
  * Solara will re-execute components instead, only what needs to.
  * State in Solara is separate from the UI components, unlike streamlit, where they are strongly linked.
  * State can be on the application level (global) for simplicity or on the component level (local) for creating reusable components.
- * Solara should not block the render loop. Long-running functions should be executed in a thread using [use_thread](/api/use_thread).
+ * Solara should not block the render loop. Long-running functions should be executed in a thread using [use_thread](/documentation/api/hooks/use_thread).

solara/website/pages/{docs/content/04-tutorial → documentation/getting_started/content/04-tutorials}/50-dash.md

@@ -36,7 +36,7 @@ This small app creates a dropdown (what we call Select in Solara), and some mark
 
 ## Translated to Solara
 
-In Solara, we need to explicitly create application state using [`solara.reactive`](/api/reactive). We wire this up with the [Select][/api/select] via `value=color` and pass the color value down to the [Markdown](/api/markdown) component.
+In Solara, we need to explicitly create application state using [`solara.reactive`](/documentation/api/utilities/reactive). We wire this up with the [Select][/documentation/components/input/select] via `value=color` and pass the color value down to the [Markdown](/documentation/components/output/markdown) component.
 
 ```solara
 import solara
@@ -50,7 +50,7 @@ def Page():
     solara.Markdown("## Hello World", style={"color": color.value})
 ```
 
-Since this component combines two components, we have to put them together in a [container](/docs/understanding/containers) component, here implicitly a [Column](/api/column).
+Since this component combines two components, we have to put them together in a [container](/documentation/advanced/understanding/containers) component, here implicitly a [Column](/documentation/components/layout/column).
 
 ## Making a re-usable component
 
@@ -115,7 +115,7 @@ if __name__ == "__main__":
 
 ### In Solara
 
-A big advantage of Solara is that components are reusable by default. However, we need to modify our component to have its own state, rather than using global application state. Creating local component state with [`use_reactive`](/api/use_reactive), or [`use_state`](/api/use_state) hook. Read more about state management in the [state management](/docs/fundamentals/state-management) section.
+A big advantage of Solara is that components are reusable by default. However, we need to modify our component to have its own state, rather than using global application state. Creating local component state with [`use_reactive`](/documentation/api/hooks/use_reactive), or [`use_state`](/documentation/api/hooks/use_state) hook. Read more about state management in the [state management](/documentation/getting_started/fundamentals/state-management) section.
 
 We will rename (from `Page` to `MarkdownWithColor`) the component, add local state, and put in the markdown text as an argument.
 

solara/website/pages/{docs/content/04-tutorial → documentation/getting_started/content/04-tutorials}/_data_science.ipynb

@@ -16,7 +16,7 @@
     "  * You have successfully installed Solara\n",
     "  * You know how to display a Solara component in a notebook or script\n",
     "\n",
-    "If not, please follow the [Quick start](/docs/quickstart).\n",
+    "If not, please follow the [Quick start](/documentation/getting_started).\n",
     "\n",
     "## Extra packages you need to install\n",
     "\n",
@@ -85,7 +85,7 @@
     "fig = px.scatter(df, \"sepal_length\", \"sepal_width\")\n",
     "```\n",
     "\n",
-    "To display this figure in a Solara component, we should return an element that can render the plotly figure. [FigurePlotly](/api/plotly) will do the job for us.\n",
+    "To display this figure in a Solara component, we should return an element that can render the plotly figure. [FigurePlotly](/documentation/components/viz/plotly) will do the job for us.\n",
     "\n",
     "Putting this together"
    ]
@@ -133,7 +133,7 @@
     "x_axis = solara.reactive(\"sepal_length\")\n",
     "```\n",
     "\n",
-    "This code creates a reactive variable. You can use this reactive variable in your component and pass it to a [`Select`]((/api/select)) component to control the selected column.\n",
+    "This code creates a reactive variable. You can use this reactive variable in your component and pass it to a [`Select`](/documentation/components/input/select) component to control the selected column.\n",
     "\n",
     "\n",
     "```python\n",
@@ -196,7 +196,7 @@
     "\n",
     "#### State\n",
     "\n",
-    "Understanding state management and how Solara re-renders component is crucial for understanding building larger applications. If you don't fully graps it now, that is ok. You should first get used to the pattern, and consider reading [About state management](/docs/fundamentals/state-management) later on to get a deeper understanding.\n",
+    "Understanding state management and how Solara re-renders component is crucial for understanding building larger applications. If you don't fully graps it now, that is ok. You should first get used to the pattern, and consider reading [About state management](/documentation/getting_started/fundamentals/state-management) later on to get a deeper understanding.\n",
     "\n"
    ]
   },
@@ -358,7 +358,7 @@
     "    return df.sort_values('distance')[1:n+1]\n",
     "```\n",
     "\n",
-    "We now only find the nearest neighbours if `click_data.value` is not None, and display the dataframe using the [`DataFrame`](/api/dataframe) component.\n"
+    "We now only find the nearest neighbours if `click_data.value` is not None, and display the dataframe using the [`DataFrame`](/documentation/components/data/dataframe) component.\n"
    ]
   },
   {

solara/website/pages/documentation/getting_started/content/05-fundamentals/00-overview.md

@@ -0,0 +1,7 @@
+# Fundamentals
+
+If you want to dive deeper into Solara, this section is for you. We will cover the following topics:
+
+  * [Components](/documentation/getting_started/fundamentals/components)
+  * Hooks (soon)
+  * [State management](/documentation/getting_started/fundamentals/state-management)

solara/website/pages/{docs/content/07-fundamentals → documentation/getting_started/content/05-fundamentals}/10-components.md

@@ -19,9 +19,9 @@ In Solara, there are two main types of components: Widget Components and Functio
 
 Widget Components correspond to ipywidgets and are responsible for rendering visual elements in the browser, such as buttons, sliders, or performing layout tasks. These components are the foundation of your user interface and provide the essential building blocks for creating interactive applications.
 
-Solara mainly uses the [ipyvuetify library](/docs/understanding/ipyvuetify) for its widget components. It provides a set of high-level components that can be used to create rich, interactive user interfaces.
+Solara mainly uses the [ipyvuetify library](/documentation/advanced/understanding/ipyvuetify) for its widget components. It provides a set of high-level components that can be used to create rich, interactive user interfaces.
 
-See the [API docs](/docs/api) for a complete list of basic UI components.
+See the [components page](/documentation/components) for a complete list of basic UI components.
 
 ## Function Components
 

solara/website/pages/{docs/content/07-fundamentals → documentation/getting_started/content/05-fundamentals}/50-state-management.md

@@ -1,12 +1,12 @@
 # Introduction
 
-State management is a crucial aspect of building data-focused web applications with Solara. By effectively managing state, you can create interactive and responsive applications that react to changes in data and user input. In Solara, there are two primary ways to define state: global application state using [`solara.reactive`](/api/reactive) and local component state using [`solara.use_state`](/api/use_state) or [`solara.use_reactive`](/api/use_reactive). This article will discuss these two approaches and provide examples of how to use them in your Solara applications.
+State management is a crucial aspect of building data-focused web applications with Solara. By effectively managing state, you can create interactive and responsive applications that react to changes in data and user input. In Solara, there are two primary ways to define state: global application state using [`solara.reactive`](/documentation/api/utilities/reactive) and local component state using [`solara.use_state`](/documentation/api/hooks/use_state) or [`solara.use_reactive`](/documentation/api/hooks/use_reactive). This article will discuss these two approaches and provide examples of how to use them in your Solara applications.
 
 ## Two main ways of defining state in Solara
 
 ### Global application state using solara.reactive
 
-Using [`solara.reactive`](/api/reactive) allows you to create global state variables that can be accessed and modified from any component within your application. This approach is useful when you need to manage state that is shared across multiple components or when you want to maintain consistency throughout your application.
+Using [`solara.reactive`](/documentation/api/utilities/reactive) allows you to create global state variables that can be accessed and modified from any component within your application. This approach is useful when you need to manage state that is shared across multiple components or when you want to maintain consistency throughout your application.
 
 Example:
 
@@ -30,7 +30,7 @@ In this case, the `SomeAppSpecificComponent` is not reusable in the sense that a
 
 ## Local component state using solara.use_state
 
-[`solara.use_state`](/api/use_state) is a hook that allows you to manage local state within a specific component. This approach is beneficial when you want to encapsulate state within a component, making it self-contained and modular. Local state management is suitable for situations where state changes only affect the component and do not need to be shared across the application.
+[`solara.use_state`](/documentation/api/hooks/use_state) is a hook that allows you to manage local state within a specific component. This approach is beneficial when you want to encapsulate state within a component, making it self-contained and modular. Local state management is suitable for situations where state changes only affect the component and do not need to be shared across the application.
 
 Example:
 ```solara

solara/website/pages/documentation/getting_started/content/06-reference/00-overview.md

@@ -0,0 +1,3 @@
+# Reference documentation
+
+Our reference documentation informs you about how certain parts in Solara work.

solara/website/pages/{docs/content/15-reference → documentation/getting_started/content/06-reference}/41-asset-files.md

@@ -29,4 +29,4 @@ All assets files are served under `/static/assets/<filename>`, but how the asset
 Putting the `assets` directory 1 level higher than the `pages` directory avoids name collision with pages.
 
 
-Although the `assets` directory can be used for serving arbitrary files, we recommend using the [static files](/docs/reference/static-files) directory instead, to avoid name collisions.
+Although the `assets` directory can be used for serving arbitrary files, we recommend using the [static files](/documentation/getting_started/reference/static-files) directory instead, to avoid name collisions.

solara/website/pages/{docs/content/15-reference → documentation/getting_started/content/06-reference}/60-static-site-generation.md

@@ -29,7 +29,7 @@ Using the command
 $ solara ssg your.awesome.app
 ```
 
-Will run the solara server and use playwright to fetch all known pages and save them to the `../build` directory. Solara knows about your pages because of its [routing support](/docs/understanding/routing).
+Will run the solara server and use playwright to fetch all known pages and save them to the `../build` directory. Solara knows about your pages because of its [routing support](/documentation/advanced/understanding/routing).
 
 All HTML files in the `../build` will be used to pre-populate the HTML served to the user.
 

solara/website/pages/{docs/content/15-reference → documentation/getting_started/content/06-reference}/70-search.md

@@ -1,6 +1,6 @@
 # Search
 
-Solara can provide search, if [SSG](/docs/reference/static-site-generation) is enabled. This allows you to add a search box to you website, which performs a full-text search to provide quick access to pages. The solara website itself uses the
+Solara can provide search, if [SSG](/documentation/getting_started/reference/static-site-generation) is enabled. This allows you to add a search box to you website, which performs a full-text search to provide quick access to pages. The solara website itself uses the
 search feature as well in the toolbar.
 
 ## Using Solara's Search feature.

solara/website/pages/{docs/content/15-reference → documentation/getting_started/content/06-reference}/80-reloading.md

@@ -13,18 +13,18 @@ When a `.vue` file is saved, the widgets get updated automatically, without need
 
 ## Reloading of .vue files
 
-The [Style component](/api/style) accepts a Path as argument, when that is used and the server is in development mode (the default), also
+The [Style component](/documentation/components/advanced/style) accepts a Path as argument, when that is used and the server is in development mode (the default), also
 CSS files will be hot reloaded.
 
 
 ## Restarting the server after changes to the solara packages
 
 
-You don't need to care about this feature if you only use solara, this is only relevant for development on solara itself, [see also development instructions](/docs/development).
+You don't need to care about this feature if you only use solara, this is only relevant for development on solara itself, [see also development instructions](/documentation/advanced/development/setup).
 
 If the `--auto-restart/-a` flag is passed to solara-server and any changes occur in the `solara` package (excluding `solara.webpage`), solara-server will restart. This speeds up development on `solara-server` for developers since you do not
 need to manually restart the server in the terminal.
 
 ## Disabling reloading
 
-In production mode (pass the `--production` argument to `solara run`) watching of files is disabled, and no reloading of files or vue templates will occur. If you run solara integrated in flask or uvicorn as laid out in [deployment documentation](https://solara.dev/docs/deploying/self-hosted)
+In production mode (pass the `--production` argument to `solara run`) watching of files is disabled, and no reloading of files or vue templates will occur. If you run solara integrated in flask or uvicorn as laid out in [deployment documentation](https://solara.dev/documentation/getting_started/deploying/self-hosted)

solara/website/pages/{docs/content/15-reference → documentation/getting_started/content/06-reference}/95-caching.md

@@ -11,7 +11,7 @@ assert "my-key" in solara.cache.storage
 
 Note that at any time later on, the key may be removed from this object, as a cache always has a limited capacity.
 
-The `solara.cache.storage` cache object is used by [memoize](/api/memoize), if no storage argument is passed to this decorator.
+The `solara.cache.storage` cache object is used by [memoize](/documentation/api/utilities/memoize), if no storage argument is passed to this decorator.
 
 ## Types of cache
 

solara/website/pages/documentation/getting_started/content/07-deploying/00-overview.md

@@ -0,0 +1,3 @@
+# Deploying a solara app
+
+A Solara app can be [self hosted](/documentation/getting_started/deploying/self-hosted) or [cloud hosted](/documentation/getting_started/deploying/cloud-hosted).

solara/website/pages/{docs/content/30-deploying → documentation/getting_started/content/07-deploying}/10-self-hosted.md

@@ -48,7 +48,7 @@ Instead, start your chosen web framework as directed by their documentation and
     $ export SOLARA_APP=sol.py
     # run flask or starlette
 
-or look at the examples below for more detailed instructions per web framework. Note that when solara is used this way it [by default runs in production mode](https://solara.dev/docs/understanding/solara-server).
+or look at the examples below for more detailed instructions per web framework. Note that when solara is used this way it [by default runs in production mode](https://solara.dev/documentation/advanced/understanding/solara-server).
 
 ## Flask
 
@@ -180,7 +180,7 @@ display(element)
 
 Or consider using [Voila-vuetify](https://github.com/voila-dashboards/voila-vuetify).
 
-Solara apps in Voila do not have support for [routing](/docs/understanding/routing)/[multipage](/docs/howto/multipage).
+Solara apps in Voila do not have support for [routing](/documentation/advanced/understanding/routing)/[multipage](/documentation/advanced/howto/multipage).
 
 
 ## Panel
@@ -211,7 +211,7 @@ For development/testing purposes, run this script as:
 
     $ panel serve solara_in_panel.py
 
-Solara apps in Panel do not have support for [routing](/docs/understanding/routing)/[multipage](/docs/howto/multipage).
+Solara apps in Panel do not have support for [routing](/documentation/advanced/understanding/routing)/[multipage](/documentation/advanced/howto/multipage).
 
 ## Nginx
 

solara/website/pages/{docs/content/30-deploying → documentation/getting_started/content/07-deploying}/20-cloud-hosted.md

@@ -73,4 +73,4 @@ Sign up for our waiting list to get early access.
 
 You can use [Ploomber Cloud](https://www.platform.ploomber.io) to deploy Solara apps for free (no credit card required).
 
-To learn more, check out their [documentation.](https://docs.cloud.ploomber.io/en/latest/apps/solara.html)
+To learn more, check out their [documentation.](https://docs.cloud.ploomber.io/en/latest/apps/solara.html)

solara/website/pages/showcase/__init__.py

@@ -9,7 +9,7 @@ def Page():
         with solara.Card("Wanderlust", style={"height": "100%"}):
             solara.Markdown(
                 """
-            [Wanderlust](./wanderlust) is a reproduction of the travel assistant demo shown at the
+            [Wanderlust](/showcase/wanderlust) is a reproduction of the travel assistant demo shown at the
             [OpenAI DevDay](https://devday.openai.com/) 2023, built using Solara and the OpenAI Assistants API.
             """
             )

solara/website/pages/showcase/domino_code_assist.py

@@ -50,7 +50,7 @@ def Page():
 
             # App deploying
 
-            To deploy apps we use [solara server](/docs/understanding/solara-server) which can
+            To deploy apps we use [solara server](/documentation/advanced/understanding/solara-server) which can
             render the same UI as in the notebook, but now sharable with non-technical users.
 
             Many users have deployed apps at Domino using Solara with

solara/website/pages/showcase/solara_dev.py

@@ -22,7 +22,7 @@ def Page():
 
         Solara.dev is designed to be responsive, working seamlessly on both desktop and mobile devices.
         On smaller screens, the top navigation bar is replaced with a drawer for easy navigation.
-        The [`ColumnsResponsive`](/api/columns_responsive) component can be used to create responsive content layouts.
+        The [`ColumnsResponsive`](/documentation/components/layout/columns_responsive) component can be used to create responsive content layouts.
 
         """
         )

solara/website/public/social/discord.svg

@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 127.14 96.36"><path fill="#fff" d="M107.7,8.07A105.15,105.15,0,0,0,81.47,0a72.06,72.06,0,0,0-3.36,6.83A97.68,97.68,0,0,0,49,6.83,72.37,72.37,0,0,0,45.64,0,105.89,105.89,0,0,0,19.39,8.09C2.79,32.65-1.71,56.6.54,80.21h0A105.73,105.73,0,0,0,32.71,96.36,77.7,77.7,0,0,0,39.6,85.25a68.42,68.42,0,0,1-10.85-5.18c.91-.66,1.8-1.34,2.66-2a75.57,75.57,0,0,0,64.32,0c.87.71,1.76,1.39,2.66,2a68.68,68.68,0,0,1-10.87,5.19,77,77,0,0,0,6.89,11.1A105.25,105.25,0,0,0,126.6,80.22h0C129.24,52.84,122.09,29.11,107.7,8.07ZM42.45,65.69C36.18,65.69,31,60,31,53s5-12.74,11.43-12.74S54,46,53.89,53,48.84,65.69,42.45,65.69Zm42.24,0C78.41,65.69,73.25,60,73.25,53s5-12.74,11.44-12.74S96.23,46,96.12,53,91.08,65.69,84.69,65.69Z"/></svg>

solara/website/public/social/github.svg

@@ -0,0 +1 @@
+<svg width="98" height="96" xmlns="http://www.w3.org/2000/svg"><path fill-rule="evenodd" clip-rule="evenodd" d="M48.854 0C21.839 0 0 22 0 49.217c0 21.756 13.993 40.172 33.405 46.69 2.427.49 3.316-1.059 3.316-2.362 0-1.141-.08-5.052-.08-9.127-13.59 2.934-16.42-5.867-16.42-5.867-2.184-5.704-5.42-7.17-5.42-7.17-4.448-3.015.324-3.015.324-3.015 4.934.326 7.523 5.052 7.523 5.052 4.367 7.496 11.404 5.378 14.235 4.074.404-3.178 1.699-5.378 3.074-6.6-10.839-1.141-22.243-5.378-22.243-24.283 0-5.378 1.94-9.778 5.014-13.2-.485-1.222-2.184-6.275.486-13.038 0 0 4.125-1.304 13.426 5.052a46.97 46.97 0 0 1 12.214-1.63c4.125 0 8.33.571 12.213 1.63 9.302-6.356 13.427-5.052 13.427-5.052 2.67 6.763.97 11.816.485 13.038 3.155 3.422 5.015 7.822 5.015 13.2 0 18.905-11.404 23.06-22.324 24.283 1.78 1.548 3.316 4.481 3.316 9.126 0 6.6-.08 11.897-.08 13.526 0 1.304.89 2.853 3.316 2.364 19.412-6.52 33.405-24.935 33.405-46.691C97.707 22 75.788 0 48.854 0z" fill="#fff"/></svg>

solara/website/public/social/twitter.svg

@@ -0,0 +1,3 @@
+<svg width="1200" height="1227" viewBox="0 0 1200 1227" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M714.163 519.284L1160.89 0H1055.03L667.137 450.887L357.328 0H0L468.492 681.821L0 1226.37H105.866L515.491 750.218L842.672 1226.37H1200L714.137 519.284H714.163ZM569.165 687.828L521.697 619.934L144.011 79.6944H306.615L611.412 515.685L658.88 583.579L1055.08 1150.3H892.476L569.165 687.854V687.828Z" fill="white"/>
+</svg>

{solara-1.29.1.dist-info → solara-1.30.0.dist-info}/METADATA

@@ -1,6 +1,7 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.3
 Name: solara
-Version: 1.29.1
+Version: 1.30.0
+Dynamic: Summary
 Project-URL: Home, https://www.github.com/widgetti/solara
 Author-email: "Maarten A. Breddels" <maartenbreddels@gmail.com>
 License: The MIT License (MIT)
@@ -49,7 +50,7 @@ Requires-Dist: watchdog
 Requires-Dist: watchfiles; python_version > '3.6'
 Requires-Dist: websockets
 Provides-Extra: assets
-Requires-Dist: solara-assets==1.29.1; extra == 'assets'
+Requires-Dist: solara-assets==1.30.0; extra == 'assets'
 Provides-Extra: dev
 Requires-Dist: black; extra == 'dev'
 Requires-Dist: bqplot; extra == 'dev'
@@ -138,7 +139,7 @@ Run:
 pip install solara
 ```
 
-Or follow the [Installation instructions](https://solara.dev/docs/installing) for more detailed instructions.
+Or follow the [Installation instructions](https://solara.dev/documentation/getting_started/installing) for more detailed instructions.
 
 ## First script
 
@@ -184,7 +185,7 @@ Solara server is starting at http://localhost:8765
 Or copy-paste this to a Jupyter notebook cell and execute it (the `Page()` expression at the end
 will cause it to automatically render the component in the notebook).
 
-See this snippet run live at https://solara.dev/docs/quickstart
+See this snippet run live at https://solara.dev/documentation/getting_started
 
 ## Demo
 
@@ -211,7 +212,7 @@ By building on top of ipywidgets, we automatically leverage an existing ecosyste
 
 Visit our main website or jump directly to the introduction
 
-[![Introduction](https://dabuttonfactory.com/button.png?t=Introduction&f=Open+Sans-Bold&ts=20&tc=fff&hp=45&vp=12&c=8&bgt=unicolored&bgc=f19f41)](https://solara.dev/docs)
-[![Quickstart](https://dabuttonfactory.com/button.png?t=Quickstart&f=Open+Sans-Bold&ts=20&tc=fff&hp=45&vp=12&c=8&bgt=unicolored&bgc=f19f41)](https://solara.dev/docs/quickstart)
+[![Introduction](https://dabuttonfactory.com/button.png?t=Introduction&f=Open+Sans-Bold&ts=20&tc=fff&hp=45&vp=12&c=8&bgt=unicolored&bgc=f19f41)](https://solara.dev/documentation)
+[![Quickstart](https://dabuttonfactory.com/button.png?t=Quickstart&f=Open+Sans-Bold&ts=20&tc=fff&hp=45&vp=12&c=8&bgt=unicolored&bgc=f19f41)](https://solara.dev/documentation/getting_started)
 
 *Note that the solara.dev website is created using Solara*