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

solara/website/pages/{docs/content/95-changelog.md → changelog/changelog.md}

@@ -1,9 +1,35 @@
 # Solara Changelog
 
+## Version 1.29.1
+
+### Details
+
+   * Bug Fix: Solara installation failing when using [pixi](https://pixi.sh/latest/). [#553](https://github.com/widgetti/solara/pull/553)
+
+## Version 1.29.0
+
+<video width="80%" controls>
+   <source src="https://solara-assets.s3.us-east-2.amazonaws.com/videos/solara-1.29-drawdata-na.mp4" type="video/mp4" >
+</video>
+
+
+### Highlights
+
+  * Feature: Improved matplotlib support (pylab interface, display support) making it work more similar as in Jupyter. [#540](https://github.com/widgetti/solara/pull/540)
+  * Feature: [use_dark_effective](https://solara.dev/api/use_dark_effective) to get the effective dark mode of the app, making it easier to support dark mode on the Python side [#551](https://github.com/widgetti/solara/pull/551).
+
+
+### Details
+
+   * Feature: [`/resourcez` endpoint](https://solara.dev/docs/understanding/solara-server) to get server resource statistics [#547](https://github.com/widgetti/solara/pull/547).
+   * Bug fix: router.push to external links should not use history, allowing navigation to external links [11c6094](https://github.com/widgetti/solara/commit/11c6094f3c47528d40f8be951c1d322e454f98ea).
+   * Bug fix: After upgrading widgets, solara server would still use the previous version due to browser cache [#523](https://github.com/widgetti/solara/pull/523).
+   * Bug fix: [The example todo app](https://solara.dev/examples/utilities/todo) would not work because Ref(..) did not work in combination with use_reactive [#544](https://github.com/widgetti/solara/pull/544).
+
 ## Version 1.28.0
 
 <video width="80%" controls>
-   <source src=https://dxhl76zpt6fap.cloudfront.net/videos/solara-theme.mp4  type="video/mp4" >
+   <source src="https://dxhl76zpt6fap.cloudfront.net/videos/solara-theme.mp4"  type="video/mp4" >
 </video>
 
 ### Highlight
@@ -123,7 +149,7 @@
 ### Highlights
 
  * Feature: Solara now has a production mode (enabled by passing in `--production`) which will load optimized CSS and JS and disable hot reloading.
-    Our [Solara server](https://solara.dev/docs/understanding/solara-server) page contains more information about it. If you used `--reload` or
+    Our [Solara server](https://solara.dev/documentation/advanced/understanding/solara-server) page contains more information about it. If you used `--reload` or
     `--dev` before you can now use the `-a/--auto-restart` flat. The `--dev` and `--reload` flags are kept for backwards compatibility.
  * Feature: All `Input` components expose the `style` and `classes` arguments for custom styling.
  * Feature: New component: [`InputDate` and `InputDateRange`](https://solara.dev/api/input_date) which use a datepicker in a menu. (#326)

solara/website/pages/contact/__init__.py

@@ -0,0 +1,8 @@
+from pathlib import Path
+
+import solara
+
+title = "Contact"
+HERE = Path(__file__)
+
+Page = solara.Markdown(Path(HERE.parent / "contact.md").read_text())

solara/website/pages/documentation/__init__.py

@@ -0,0 +1,184 @@
+from pathlib import Path
+
+import solara
+
+_title = "Documentation"
+
+HERE = Path(__file__).parent
+
+route_order = ["/", "getting_started", "examples", "components", "api", "advanced", "faq"]
+
+
+@solara.component_vue(str(HERE.parent.parent / "components" / "algolia_api.vue"))
+def Algolia():
+    pass
+
+
+@solara.component
+def Page(children=[]):
+    # show a gallery of all the api pages
+    router = solara.use_router()
+    route_current = router.path_routes[-2]
+
+    with solara.Column(style={"width": "100%"}, gap="75px"):
+        if route_current.path == "documentation":
+            with solara.Column(classes=["api-search-container"], gap="50px", style={"justify-content": "center"}, align="center"):
+                solara.Markdown("# Search the Solara Documentation", style={"text-align": "center"})
+                with solara.Row(style={"width": "100%", "min-width": "20rem", "justify-content": "center", "background-color": "transparent"}):
+                    Algolia()
+            with solara.Row(gap="20px", classes=["docs-card-container"]):
+                for route in route_current.children:
+                    if route.path in ["/", "advanced", "faq"]:
+                        continue
+                    with solara.Link("/documentation/" + route.path):
+                        with solara.Row(
+                            classes=["docs-card"],
+                            style={
+                                "background-color": f"var({'--docs-color-grey' if route.path != 'getting_started' else '--color-primary'})",
+                            },
+                        ):
+                            with solara.Column(style={"height": "100%", "flex-grow": "1", "background-color": "transparent"}):
+                                solara.HTML(tag="h2", unsafe_innerHTML=route.label, style={"color": "white", "padding": "1.5rem"})
+                            with solara.Column(style={"justify-content": "center", "height": "100%", "background-color": "transparent"}):
+                                solara.v.Icon(children=["mdi-arrow-right"], color="var(--color-grey-light)", x_large=True, class_="docs-card-icon")
+            with solara.Row(gap="75px", style={"flex-wrap": "wrap", "row-gap": "75px", "padding-bottom": "75px"}):
+                with solara.Column(style={"padding-left": "10%"}):
+                    solara.HTML(tag="h2", unsafe_innerHTML="How to use our documentation:", style={"padding": "1.5rem"})
+                    solara.Markdown(
+                        """
+* [Getting Started](/documentation/getting_started) - Learn how to install Solara and get started with building your app.
+    Also includes tutorials for you to get a hang of Solara workflow.
+* [Examples](/documentation/examples) - More complex and real world applicable examples of Solara apps.
+    For even more complexity you can see the [Showcase](/showcase) page.
+* [Components](/documentation/components) - All the components that are available in Solara.
+* [API](/documentation/api) - All the API functions that are available in Solara. Importantly, this includes routing and hooks.
+* [Advanced](/documentation/advanced) - Advanced topics like associated and underlying libraries.
+    If a component you would like to use is not available in Solara, you can use the underlying library directly.
+                    """
+                    )
+                with solara.Column(style={"justify-content": "center", "height": "100%"}):
+                    solara.HTML(tag="h2", unsafe_innerHTML="Also Check Out", style={"padding": "1.5rem"})
+                    with solara.Row(gap="20px", style={"flex-wrap": "wrap", "row-gap": "20px", "align-items": "center"}):
+                        with solara.v.Html(tag="a", attributes={"href": "https://discord.solara.dev", "target": "_blank"}):
+                            with solara.Div(classes=["social-logo-container"], style={"background-color": "var(--docs-social-discord)"}):
+                                solara.v.Html(tag="img", attributes={"src": "/static/public/social/discord.svg"}, style_="height: 1.5rem; width: auto;")
+                        solara.Text("We use discord to provide support and answer questions there actively.")
+                    with solara.Row(gap="20px", style={"flex-wrap": "wrap", "row-gap": "20px", "align-items": "center"}):
+                        with solara.v.Html(tag="a", attributes={"href": "https://github.com/widgetti/solara", "target": "_blank"}):
+                            with solara.Div(classes=["social-logo-container"], style={"background-color": "var(--docs-social-github)"}):
+                                solara.v.Html(tag="img", attributes={"src": "/static/public/social/github.svg"}, style_="height: 1.5rem; width: auto;")
+                        solara.Text("Search for solutions on Github issues, or report bugs.")
+                    with solara.Row(gap="20px", style={"flex-wrap": "wrap", "row-gap": "20px", "align-items": "center"}):
+                        with solara.v.Html(tag="a", attributes={"href": "https://twitter.com/solara_dev", "target": "_blank"}):
+                            with solara.Div(classes=["social-logo-container"], style={"background-color": "var(--docs-social-twitter)"}):
+                                solara.v.Html(tag="img", attributes={"src": "/static/public/social/twitter.svg"}, style_="height: 1.5rem; width: auto;")
+                        solara.Text("Get announcements about Solara features, showcases, and events!.")
+
+        else:
+            with solara.Column(align="center", children=children, style={"padding": "0"}):
+                pass
+
+
+@solara.component
+def Sidebar():
+    route_current, all_routes = solara.use_route()
+    router = solara.use_router()
+    if route_current is None:
+        return solara.Error("Page not found")
+
+    with solara.v.NavigationDrawer(
+        clipped=True, width="20rem", height="unset", style_="min-height: calc(100vh - 215.5px);", class_="d-none d-md-block"
+    ) as main:
+        with solara.v.List(expand=True, nav=True, style_="height: calc(100vh - 215.5px); display: flex; flex-direction: column;"):
+            with solara.v.ListItemGroup(v_model=router.path):
+                for route in all_routes:
+                    if len(route.children) == 1 or route.path == "/":
+                        with solara.Link("/documentation/" + route.path if route.path != "/" else "/documentation"):
+                            with solara.v.ListItem(value="/documentation/" + route.path if route.path != "/" else "/documentation"):
+                                if route.path == "/":
+                                    solara.v.ListItemIcon(children=[solara.v.Icon(children=["mdi-home"])])
+                                solara.v.ListItemTitle(style_="padding: 0 20px;", children=[route.label])
+                    else:
+                        with solara.v.ListGroup(
+                            v_slots=[
+                                {
+                                    "name": "activator",
+                                    "children": solara.v.ListItemTitle(
+                                        children=[route.label],
+                                        style_="padding: 0 20px;",
+                                    ),
+                                }
+                            ],
+                            value=router.path.startswith("/documentation/" + route.path),
+                        ):
+                            for item in route.children:
+                                if item.path == "/":
+                                    continue
+                                if item.children != [] and any([c.label is not None and c.path != "/" for c in item.children]):
+                                    with solara.v.ListGroup(
+                                        v_slots=[
+                                            {
+                                                "name": "activator",
+                                                "children": solara.v.ListItemTitle(
+                                                    children=[item.label],
+                                                ),
+                                            }
+                                        ],
+                                        sub_group=True,
+                                        no_action=True,
+                                        value=router.path.startswith("/documentation/" + route.path + "/" + item.path),
+                                    ):
+                                        for subitem in item.children:
+                                            # skip pages that are only used to demonstrate Link or Router usage
+                                            if subitem.path == "/" or subitem.label is None:
+                                                continue
+                                            path = (
+                                                "/documentation/" + route.path + "/" + item.path + "/" + subitem.path
+                                                if item.path != "fullscreen"
+                                                else "/apps/" + subitem.path
+                                            )
+                                            with solara.Link(
+                                                path,
+                                            ):
+                                                with solara.v.ListItem(dense=True, style_="padding: 0 20px;", value=path):
+                                                    solara.v.ListItemContent(
+                                                        children=[subitem.label],
+                                                    )
+                                else:
+                                    with solara.v.ListItemGroup(value="/documentation/" + route.path + "/" + item.path):
+                                        with solara.Link(
+                                            "/documentation/" + route.path + "/" + item.path,
+                                        ):
+                                            with solara.v.ListItem(dense=True, style_="padding: 0 20px;"):
+                                                solara.v.ListItemContent(
+                                                    children=[item.label],
+                                                )
+            solara.v.Spacer(style_="flex-grow: 1;")
+            with solara.v.ListItemGroup():
+                with solara.Link("/contact"):
+                    with solara.v.ListItem():
+                        solara.v.ListItemIcon(children=[solara.v.Icon(children=["mdi-email"])])
+                        solara.v.ListItemTitle(style_="padding: 0 20px;", children=["Contact"])
+                with solara.Link("/changelog"):
+                    with solara.v.ListItem():
+                        solara.v.ListItemIcon(children=[solara.v.Icon(children=["mdi-history"])])
+                        solara.v.ListItemTitle(style_="padding: 0 20px;", children=["Changelog"])
+
+    return main
+
+
+@solara.component
+def Layout(children=[]):
+    route_current, all_routes = solara.use_route()
+    if route_current is None:
+        return solara.Error("Page not found")
+
+    if route_current.path == "/":
+        return Page()
+    else:
+        return Page(children=children)
+
+
+@solara.component
+def Overview():
+    pass

solara/website/pages/documentation/advanced/__init__.py

@@ -0,0 +1,36 @@
+from pathlib import Path
+
+import solara
+from solara.autorouting import generate_routes_directory
+
+title = "Advanced"
+HERE = Path(__file__)
+# if we didn't put the content in the subdirectory, but pointed to the current file
+# we would include the current file recursively, causing an infinite loop
+routes = generate_routes_directory(HERE.parent / "content")
+
+
+@solara.component
+def Page(route_external=None):
+    solara.Markdown(Path(HERE.parent / "content" / "10-howto" / "00-overview.md").read_text())
+
+    with solara.Row(justify="center", style={"flex-wrap": "wrap", "align-items": "start"}):
+        for child in route_external.children:
+            if child.path == "/":
+                continue
+
+            card_title = solara.Link("/documentation/advanced/" + child.path, children=[child.label])
+
+            with solara.Card(title=card_title, style={"min-width": "300px"}):
+                with solara.v.List():
+                    with solara.v.ListItemGroup():
+                        for grandchild in child.children:
+                            if grandchild.path == "/":
+                                continue
+                            with solara.Link(
+                                "/documentation/advanced/" + child.path + "/" + grandchild.path
+                                if child.path != "/"
+                                else "/documentation/advanced/" + grandchild.path
+                            ):
+                                with solara.v.ListItem():
+                                    solara.v.ListItemTitle(children=[grandchild.label])

solara/website/pages/documentation/advanced/content/00-overview.md

@@ -0,0 +1 @@
+The entries are meant as deeper dives into specific topics. Although we try to write each as a standalone document, some parts may build on previous ones.

solara/website/pages/{docs/content/10-howto/20-multipage.md → documentation/advanced/content/10-howto/10-multipage.md}

@@ -1,6 +1,6 @@
 # Multi-page support
 
-In the [Web App tutorial](/docs/tutorial/web-app), we created an application consisting of a single page. Web applications generally have multiple pages, and Solara supports this as well.
+In the [Web App tutorial](/documentation/getting_started/tutorials/web-app), we created an application consisting of a single page. Web applications generally have multiple pages, and Solara supports this as well.
 
 
 ## Multiple scripts
@@ -42,8 +42,7 @@ Solara now:
    * Generate a nice URL by stripping of prefix, splitting the filename taking out `-`, `_` and spaces, and join them together using a `-`  (e.g. "/markdown-editor").
    * Generate a nice default title similar to the link, but now capitalize the first letter and join with a space instead  (e.g. "Mardown Editor").
    * The first page will be the default (and its URL will be empty instead, i.e., the empty string `""`)
-   * Since the first script does not define a `Layout` component, nor did we add a `__init__.py` with a `Layout` component, Solara will add a [default
-     Layout component](/api/default_layout) which includes a navigation sidebar.
+   * Since the first script does not define a `Layout` component, nor did we add a `__init__.py` with a `Layout` component, Solara will add a [Layout component](/documentation/components/layout/app_layout) which includes a navigation sidebar.
    * If a path is a directory, Solara will recursively scan the subdirectory and include it in the navigation. Read more on this in the [Layout section](layout)
 
 Solara will render two pages:
@@ -148,7 +147,7 @@ routes = [
 ]
 ```
 
-See more details in the [Route section](/docs/understanding/routing).
+See more details in the [Route section](/documentation/advanced/understanding/routing).
 
 ## Dynamic pages
 
@@ -189,4 +188,4 @@ By giving the name argument a default value of `"foo"`, Solara will also accept
 
 # What next?
 
-  * Also check out the [Multipage example](/apps/multipage) for more inspiration.
+  * Also check out the [Multipage example](/documentation/examples/fullscreen/multipage) for more inspiration.

solara/website/pages/{docs/content/10-howto/30-layout.md → documentation/advanced/content/10-howto/20-layout.md}

@@ -33,29 +33,29 @@ def Page():
                     solara.Info("two per column on small screens, three per column on large screens")
 ```
 
-[Navigate here to watch this layout in a full browser window](/apps/layout-demo)
+[Navigate here to watch this layout in a full browser window](/documentation/examples/fullscreen/layout_demo)
 
 The key takeaways are:
 
-  * By default, Solara will wrap your component in an [AppLayout](/api/app_layout), which will give you:
-    * Room for a sidebar, that you can populate using the [Sidebar](/api/sidebar) component.
-    * A toolbar showing the [Title](/api/title).
-    * Not visible here: In the case of [multiple pages](/docs/howto/multipage) will include page navigation tabs. See [The multipage demo app](/app/multipage) for an example.
-  * Use [Card](/api/card) to put related components together with a title.
-  * Use [Column](/api/column) to simply layout components under each other.
-  * Use [Columns](/api/columns) if you want to have a few columns with relative sizes next to each other.
-  * Use [ColumnsResponsive](/api/columns_responsive) to have the column widths respond to screen size.
+  * By default, Solara will wrap your component in an [AppLayout](/documentation/components/layout/app_layout), which will give you:
+    * Room for a sidebar, that you can populate using the [Sidebar](/documentation/components/layout/sidebar) component.
+    * A toolbar showing the [Title](/documentation/components/page/title).
+    * Not visible here: In the case of [multiple pages](/documentation/advanced/howto/multipage) will include page navigation tabs. See [The multipage demo app](/documentation/examples/fullscreen/multipage) for an example.
+  * Use [Card](/documentation/components/layout/card) to put related components together with a title.
+  * Use [Column](/documentation/components/layout/column) to simply layout components under each other.
+  * Use [Columns](/documentation/components/layout/columns) if you want to have a few columns with relative sizes next to each other.
+  * Use [ColumnsResponsive](/documentation/components/layout/columns_responsive) to have the column widths respond to screen size.
 
 
 
 ## Changing the default layout
 
-While [AppLayout](/api/app_layout) may be sufficient in 80% of the cases. Solara provides a way to change this default layout in [Solara server](/docs/understanding/solara-server).
+While [AppLayout](/documentation/components/layout/app_layout) may be sufficient in 80% of the cases. Solara provides a way to change this default layout in [Solara server](/documentation/advanced/understanding/solara-server).
 
 You can define your own `Layout` component in the `__init__.py` file in the same directory of your app script.
 
 
-For instance, putting the following `Layout` component in `__init__.py` will give you effectively the same [AppLayout](/api/app_layout):
+For instance, putting the following `Layout` component in `__init__.py` will give you effectively the same [AppLayout](/documentation/components/layout/app_layout):
 ```python
 @solara.component
 def Layout(children=[]):
@@ -80,7 +80,7 @@ This layout leaves every page responsible for creating its own header, footer, a
 ### Layout with navigation
 
 In case you want to set up your own layout system, which sets up navigation as well, this example may get you started. It may help
-to [understand routing](/docs/understanding/routing).
+to [understand routing](/documentation/advanced/understanding/routing).
 ```python
 @solara.component
 def Layout(children=[]):
@@ -108,13 +108,13 @@ This is useful for larger apps where each subdirectory may add a bit of layout/c
 
 ## Components
 
-The following [Container components](/docs/understanding/containers) can be used to define the layout of you app.
+The following [Container components](/documentation/advanced/understanding/containers) can be used to define the layout of you app.
 
- * [Row](/api/row)
- * [Column](/api/column)
- * [ColumnsResponsive](/api/columns_responsive)
- * [GridFixed](/api/gridfixed)
- * [GridDraggable](/api/griddraggable)
- * [VBox](/api/vbox) (kept for ipywidgets compatibility, please use Column)
- * [HBox](/api/hbox) (kept for ipywidgets compatibility, please use Row)
- * [AppLayout](/api/app_layout) Not often used directly, since Solara will already wrap your page in it. Sometimes re-used in a new `Layout` component.
+ * [Row](/documentation/components/layout/row)
+ * [Column](/documentation/components/layout/column)
+ * [ColumnsResponsive](/documentation/components/layout/columns_responsive)
+ * [GridFixed](/documentation/components/layout/gridfixed)
+ * [GridDraggable](/documentation/components/layout/griddraggable)
+ * [VBox](/documentation/components/layout/vbox) (kept for ipywidgets compatibility, please use Column)
+ * [HBox](/documentation/components/layout/hbox) (kept for ipywidgets compatibility, please use Row)
+ * [AppLayout](/documentation/components/layout/app_layout) Not often used directly, since Solara will already wrap your page in it. Sometimes re-used in a new `Layout` component.

solara/website/pages/{docs/content/10-howto/80-embed.md → documentation/advanced/content/10-howto/40-embed.md}

@@ -40,4 +40,4 @@ Solara uses a cookie to implement sessions. To support cookies settings in an if
 
 ## Embed into an existing page
 
-If embedding into an iframe does not suit your needs (for example, dialogs not being fullscreen), [please contact us](/docs/contact) and we can discuss other options.
+If embedding into an iframe does not suit your needs (for example, dialogs not being fullscreen), [please contact us](/contact) and we can discuss other options.

solara/website/pages/{docs → documentation/advanced}/content/20-understanding/06-ipyvuetify.md

@@ -11,7 +11,7 @@ material design based widgets.
 
 ## Reacton and ipyvuetify
 
-We consider ipyvuetify one of the most essential ipywidget libraries, and that is the reason why [Reacton](/docs/understanding/reacton) ships with
+We consider ipyvuetify one of the most essential ipywidget libraries, and that is the reason why [Reacton](/documentation/advanced/understanding/reacton) ships with
 generated ipyvuetify components to make your app type safe.
 
 ```solara

solara/website/pages/{docs → documentation/advanced}/content/20-understanding/12-reacton-basics.md

@@ -90,7 +90,7 @@ In words
    1. Solara create `el = ButtonClick()` from your component.
    1. The `display(el)` triggers the call to Reacton.
    1. The render call enters the render phase, which will call the function body (which we call render function) of the `ButtonClick` component.
-   1. Our ButtonClick render function calls [`use_state`](/api/use_state). Because this is our first render phase, this returns the initial value (0).
+   1. Our ButtonClick render function calls [`use_state`](/documentation/api/hooks/use_state). Because this is our first render phase, this returns the initial value (0).
    1. The ButtonClick render function returns a Button element (not a widget!) with `description="Clicked: 0 times"`.
    1. The Reacton render call is done with the render phase, and enters the reconciliation phase, where it looks at the difference between the real widgets and the virtual widgets tree (represented by the Reacton elements). We find there is no previous widget associated with the virtual widget (or element) and decide to create a widget.
    1. Asynchronously via the Jupyter protocol, a widget model and view are created and displayed to the user in the browser.

solara/website/pages/{docs → documentation/advanced}/content/20-understanding/15-anatomy.md

@@ -9,10 +9,10 @@ As a reference, we provide this "anatomy" image of our favorite `ClickButton` co
 
  * Import `solara` and you also get the `reacton` namespace with it (saves typing, and finding/remembering which hooks is in which packages)
  * Add a `@solara.component` decorator to turn your function into a component.
- * Start with `use_state` hooks and other hooks. This avoids issues with [conditional hooks](/docs/understanding/rules-of-hooks) or hooks in loops.
+ * Start with `use_state` hooks and other hooks. This avoids issues with [conditional hooks](/documentation/advanced/understanding/rules-of-hooks) or hooks in loops.
  * Data/state flows down (to children)
  * Information (events, data) flows up from children via events and callbacks (`on_<some_event_name>=my_callback`).
- * If you need multiple components, use a [parent container component](/api#layout) as context manager. A good default name to give this context manager is `main`. Don't forget to return it in your render function!
+ * If you need multiple components, use a [parent container component](/documentation/components/layout/app_layout) as context manager. A good default name to give this context manager is `main`. Don't forget to return it in your render function!
  * The body of your component (the function you wrote) is called the render function.
  * In between the hooks as defining all your elements, you put your custom code, like checking variables, defining callbacks, and other logic.
  * The only way for a component to cause itself to rerender is to have state (using `use_state`) and change it (calling the second return value with a different value).

solara/website/pages/{docs → documentation/advanced}/content/20-understanding/18-containers.md

@@ -51,7 +51,7 @@ Page = FancyClickButton
 ```
 
 
-Here we use an [HBox](/api/hbox) to lay out two child components horizontally.
+Here we use an [HBox](/documentation/components/layout/hbox) to lay out two child components horizontally.
 
 
 ## Cleaner way to add children to containers
@@ -96,7 +96,7 @@ with some_named_context_manager() as this_is_my_name:
     print("some other code")
 ```
 
-Where the last example assigns the context manager to a variable. In Solara we only need to do that to the top context manager, since we need to return that in our [render function](/docs/understanding/anatomy).
+Where the last example assigns the context manager to a variable. In Solara we only need to do that to the top context manager, since we need to return that in our [render function](/documentation/advanced/understanding/anatomy).
 
 All Reacton or Solara components return elements that can be used as context managers. Context managers allow for code to be executed before and after your code block inside of the context manager. This allows us to capture all elements created inside of the context manager. If you want to know more about context managers, consult the Python documentation since this is not Solara specific.
 
@@ -138,7 +138,7 @@ Page = FancyClickButton
 Instead of returning the main container, Solara also allows you to not have a return value (or return `None`).
 If that is the case, Solara will look at what elements you created. If you created one, that element will be taken
 as a return value instead. If you make more than one element, those elements will be automatically wrapped by
-a [Column](/api/column). The only benefit of returning an element, is that we can infer the correct return type,
+a [Column](/documentation/components/layout/column). The only benefit of returning an element, is that we can infer the correct return type,
 which can be useful for testing purposes. Users should probably never return an element, but use the automatic
 container feature.
 

solara/website/pages/{docs → documentation/advanced}/content/20-understanding/40-routing.md

@@ -13,15 +13,15 @@ Setting up routing can be repetitive, and therefore Solara comes also with a mor
 
 ### Based on a directory
 
-Using [`generate_routes_directory(path: Path) -> List[solara.Route]:`](/api/generate_routes_directory) we can request Solara to give us a list of
+Using [`generate_routes_directory(path: Path) -> List[solara.Route]:`](/documentation/api/routing/generate_routes_directory) we can request Solara to give us a list of
 routes by scanning a directory for Python scripts, Notebooks and Markdown files.
 
-This function is being used by Solara if you run solara server with a directory as argument name, as used in [our Multi Page guide](/docs/howto/multipage). More details can be found there.
+This function is being used by Solara if you run solara server with a directory as argument name, as used in [our Multi Page guide](/documentation/advanced/howto/multipage). More details can be found there.
 
 
 ### Based on a Python package
 
-Similar to the previous section [`generate_routes(module: ModuleType) -> List[solara.Route]:`](/api/generate_routes) will return a list of routes by scanning a Python package or module for `Page` components, or `app` elements. Again, more information can be found at [our Multi Page guide](/docs/howto/multipage).
+Similar to the previous section [`generate_routes(module: ModuleType) -> List[solara.Route]:`](/documentation/api/routing/generate_routes) will return a list of routes by scanning a Python package or module for `Page` components, or `app` elements. Again, more information can be found at [our Multi Page guide](/documentation/advanced/howto/multipage).
 
 ## Manually defining routes
 
@@ -59,7 +59,7 @@ routes = [
 
 ### Defining route components
 
-If you do define a `Page` component, you are fully responsible for how routing is done, but we recommend using [use_route](/api/use_route).
+If you do define a `Page` component, you are fully responsible for how routing is done, but we recommend using [use_route](/documentation/api/routing/use_route).
 
 An example route definition could be something like this:
 
@@ -180,9 +180,9 @@ routes = [
 ]
 ```
 
-In the case where you did not specify a `Page` component, label is used for the [Title](/api/title) component.
+In the case where you did not specify a `Page` component, label is used for the [Title](/documentation/components/page/title) component.
 
-If you need to store more data in the route, you are free to put whatever you want in the `data` attribute, see also [Route](/api/route).
+If you need to store more data in the route, you are free to put whatever you want in the `data` attribute, see also [Route](/documentation/api/routing/route).
 
 
 
@@ -194,14 +194,14 @@ Note that all routes are relative, since a component does not know if it is embe
 Therefore you should never use the `route.path` for navigation since the route object has no knowledge of the full url
 (e.g. `/docs/basics/ipywigets`) but only knows its small piece of the pathname (e.g. `ipywidgets`)
 
-Using [`resolve_path`](/api/resolve_path) we can request the full url for navigation.
+Using [`resolve_path`](/documentation/api/routing/resolve_path) we can request the full url for navigation.
 
 ```python
 def resolve_path(path_or_route: Union[str, solara.Route], level=0) -> str:
     ...
 ```
 
-We can pass this full URL to the [`solara.Link`](/api/link) component, e.g. like:
+We can pass this full URL to the [`solara.Link`](/documentation/components/advanced/link) component, e.g. like:
 
 ```python
 @solara.component
@@ -217,7 +217,7 @@ def LinkToIpywidgets():
 
 ## Fully manual routing
 
-If you want to do routing fully manually, you can use the [`solara.use_router`](/api/use_router) hook, and use the `.path` attribute.
+If you want to do routing fully manually, you can use the [`solara.use_router`](/documentation/api/routing/use_router) hook, and use the `.path` attribute.
 
 ```python
 import solara

solara/website/pages/{docs → documentation/advanced}/content/20-understanding/50-solara-server.md

@@ -67,7 +67,7 @@ The JSON format may be subject to change.
 
 By default, solara runs in development mode. This means, it will:
 
-   * Automatically [reload your project files](docs/reference/reloading) by watching files on the filesystemn
+   * Automatically [reload your project files](/documentation/getting_started/reference/reloading) by watching files on the filesystemn
    * Load debug version of the CSS files and JavaScript files for improved error messages (which leads to larger asset files).
 
 To disabled all of these option, pass the `--production` flag, or set the environment variable `SOLARA_MODE=production`.

solara/website/pages/{docs/content/50-enterprise → documentation/advanced/content/30-enterprise}/10-oauth.md

@@ -8,7 +8,7 @@ You have probably used OAuth without realizing it when signing into various onli
 
 ## Installing
 
-To install Solara with OAuth support, make sure you have [Solara Enterprise](/docs/enterprise) install by run the following command:
+To install Solara with OAuth support, make sure you have [Solara Enterprise](/documentation/advanced/enterprise) install by run the following command:
 
 ```bash
 $ pip install solara solara-enterprise[auth]
@@ -152,8 +152,8 @@ ZgrzSLUyft-JvnNMNJ2LgbCFVqcxPOatANAQhMD5EYU
 
 Solara provides two convenient components for creating a user interface for login and logout:
 
- 1. [Avatar](/api/avatar): This component shows the user's avatar.
- 2. [AvatarMenu](/api/avatar_menu): This component shows a menu with the user's avatar and a logout button.
+ 1. [Avatar](/documentation/components/enterprise/avatar): This component shows the user's avatar.
+ 2. [AvatarMenu](/documentation/components/enterprise/avatar_menu): This component shows a menu with the user's avatar and a logout button.
 
  ## Python version support
 

solara/website/pages/{docs/content/10-howto → documentation/advanced/content/40-development}/01-contribute.md

@@ -7,8 +7,8 @@ You do not need to be a developer to contribute to Solara. We welcome all contri
 
 We use [GitHub to manage issues](https://github.com/widgetti/solara/issues/new) and you should not hesitate to report any bug you find. Please include as much information as possible for us to be able to reproduce the bug. Yes, reporting a bug/issue is a contribution!
 
-It might take a while for us to get back to you. If the bug is urgent, and you are able to provide financial support for its rapid resolution, please [contact us](/docs/contact).
-If you can fix the bug yourself, please consider submitting a pull request instead, see [the development guide](/docs/development) for more information.
+It might take a while for us to get back to you. If the bug is urgent, and you are able to provide financial support for its rapid resolution, please [contact us](/contact).
+If you can fix the bug yourself, please consider submitting a pull request instead, see [the development guide](/documentation/advanced/development/setup) for more information.
 
 If you are unable to address the bug yourself and find it challenging to provide financial support, please be assured we are still committed to rectifying bugs and resolving issues. However, please understand that our ability to address these issues may be impacted by our resources at hand, as sustaining this project also entails financial obligations. Your patience and understanding in this matter is highly appreciated 🙇.
 
@@ -16,7 +16,7 @@ If you are unable to address the bug yourself and find it challenging to provide
 
 The documentation is mostly written in Markdown, and can be found at [in the main repository](https://github.com/widgetti/solara/tree/master/solara/website/pages).
 
-You can use the GitHub web interface to edit the files, or clone the repository and edit them locally. See [the development guide](/docs/development) for more information.
+You can use the GitHub web interface to edit the files, or clone the repository and edit them locally. See [the development guide](/documentation/advanced/development/setup) for more information.
 
 If you locally want to render the documentation, run:
 
@@ -26,10 +26,10 @@ $ solara run solara.website.pages
 
 ## Examples or showcase
 
-If you have a complete program you want to share, and you think it would be cool to be listed at [our showcase page](/showcase), [please contact us](/docs/contact).
+If you have a complete program you want to share, and you think it would be cool to be listed at [our showcase page](/showcase), [please contact us](/contact).
 
 If you want to show a particular way of using Solara that you think is very useful
-for others, but it is not a complete program, consider adding to [the examples](/docs/examples). See [the development guide](/docs/development) for more information.
+for others, but it is not a complete program, consider adding to [the examples](/documentation/examples/). See [the development guide](/documentation/advanced/development/setup) for more information.
 
 ## Share your experiences and ideas
 

solara/website/pages/{docs/content/90-development → documentation/advanced/content/40-development}/10-setup.md

@@ -1,9 +1,9 @@
 # Development
 
-See also [the contributing guide](/docs/howto/contribute) for more information on how to contribute to Solara.
+See also [the contributing guide](/documentation/advanced/development/contribute) for more information on how to contribute to Solara.
 ## Development setup
 
-Assuming you have created a virtual environment as described in [the installation guide](/docs/installing), you can install a development install of Solara using:
+Assuming you have created a virtual environment as described in [the installation guide](/documentation/getting_started/installing), you can install a development install of Solara using:
 
     $ git clone git@github.com:widgetti/solara.git
     $ cd solara