Renderers are now packages, not features. (#387)

* feat: use synchronous router design

* feat: function to get router out of dom

* chore: restructure workspace to use renderers as packages, not features

docs/guide/src/en/__unused/advanced-guides/rsx.md

@@ -33,7 +33,7 @@ let name = "jane";
 let pending = false;
 let count = 10;
 
-dioxus::ssr::render_lazy(html! {
+dioxus_ssr::render_lazy(html! {
     <div>
         <p> "Hello, {name}!" </p>
         <p> "Status: {pending}!" </p>
@@ -51,7 +51,7 @@ When helpful, the Dioxus VSCode extension provides a way of converting a selecti
 It's also a bit easier on the eyes than HTML.
 
 ```rust
-dioxus::ssr::render_lazy(rsx! {
+dioxus_ssr::render_lazy(rsx! {
     div {
         p {"Hello, {name}!"}
         p {"Status: {pending}!"}

docs/guide/src/en/__unused/composing.md

@@ -159,7 +159,7 @@ force_render(ScopeId(0));
 
 In our guides, we frequently use the phrase "re-render" to describe updates to our app. You'll often hear this paired with "preventing unnecessary re-renders." But what exactly does this mean?
 
-When we call `dioxus::desktop::launch`, Dioxus will create a new `Scope` object and call the component we gave it. Our `rsx!` calls will create new nodes which we return back to the VirtualDom. Dioxus will then look through these nodes for child components, call their functions, and so on until every component has been "rendered." We consider these nodes "rendered" because they were created because of our explicit actions.
+When we call `dioxus_desktop::launch`, Dioxus will create a new `Scope` object and call the component we gave it. Our `rsx!` calls will create new nodes which we return back to the VirtualDom. Dioxus will then look through these nodes for child components, call their functions, and so on until every component has been "rendered." We consider these nodes "rendered" because they were created because of our explicit actions.
 
 The tree of UI that dioxus creates will roughly look like the tree of components presented earlier:
 

docs/guide/src/en/__unused/event_javascript.rs

@@ -12,7 +12,7 @@ Instead of passing a closure, you can also pass a string to event handlers – t
 use dioxus::prelude::*;
 
 fn main() {
-    dioxus::desktop::launch(App);
+    dioxus_desktop::launch(App);
 }
 
 fn App(cx: Scope) -> Element {

docs/guide/src/en/__unused/index.md

@@ -16,7 +16,7 @@ For the simplest of apps, all of your state can enter the app from the root prop
 ```rust
 let all_content = get_all_content().await;
 
-let output = dioxus::ssr::render_lazy(rsx!{
+let output = dioxus_ssr::render_lazy(rsx!{
     div {
         RenderContent { content: all_content }
     }

docs/guide/src/en/getting_started/mobile.md

@@ -24,7 +24,7 @@ cargo install --git https://github.com/BrainiumLLC/cargo-mobile
 And then initialize your app for the right platform. Use the `winit` template for now. Right now, there's no "Dioxus" template in cargo-mobile.
 
 ```shell
-cargo mobile init 
+cargo mobile init
 ```
 
 We're going to completely clear out the `dependencies` it generates for us, swapping out `winit` with `dioxus-mobile`.
@@ -61,7 +61,7 @@ Edit your `lib.rs`:
 use dioxus::prelude::*;
 
 fn main() {
-    dioxus::mobile::launch(app);
+    dioxus_mobile::launch(app);
 }
 
 fn app(cx: Scope) -> Element {

docs/guide/src/en/getting_started/ssr.md

@@ -21,10 +21,10 @@ If you just want to render `rsx!` or a VirtualDom to HTML, check out the API doc
 // We can render VirtualDoms
 let mut vdom = VirtualDom::new(app);
 let _ = vdom.rebuild();
-println!("{}", dioxus::ssr::render_vdom(&vdom));
+println!("{}", dioxus_ssr::render_vdom(&vdom));
 
 // Or we can render rsx! calls directly
-println!( "{}", dioxus::ssr::render_lazy(rsx! { h1 { "Hello, world!" } } );
+println!( "{}", dioxus_ssr::render_lazy(rsx! { h1 { "Hello, world!" } } );
 ```
 
 However, for this guide, we're going to show how to use Dioxus SSR with `Axum`.
@@ -84,7 +84,7 @@ And then add our endpoint. We can either render `rsx!` directly:
 
 ```rust
 async fn app_endpoint() -> Html<String> {
-    Html(dioxus::ssr::render_lazy(rsx! {
+    Html(dioxus_ssr::render_lazy(rsx! {
             h1 { "hello world!" }
     }))
 }
@@ -100,7 +100,7 @@ async fn app_endpoint() -> Html<String> {
     let mut app = VirtualDom::new(app);
     let _ = app.rebuild();
 
-    Html(dioxus::ssr::render_vdom(&app))
+    Html(dioxus_ssr::render_vdom(&app))
 }
 ```
 

docs/guide/src/en/interactivity/index.md

@@ -1,3 +1,3 @@
 # Interactivity
 
-So far, we've learned how to describe the structure and properties of our user interfaces. However, most interfaces need to be interactive in order to be useful. In this chapter, we describe how to make a Dioxus app that responds to the user.
+So far, we've learned how to describe the structure and properties of our user interfaces. However, most interfaces need to be interactive in order to be useful. In this chapter, we describe how to make a Dioxus app that responds to the user.