Internationalization: move guide to en folder and preserve its history. (#494)

* chore: move guide to en folder

* docs: add english as language

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

@@ -0,0 +1,29 @@
+# Best Practices
+
+## Reusable Components
+
+As much as possible, break your code down into small, reusable components and hooks, instead of implementing large chunks of the UI in a single component. This will help you keep the code maintainable – it is much easier to e.g. add, remove or re-order parts of the UI if it is organized in components.
+
+Organize your components in modules to keep the codebase easy to navigate!
+
+## Minimize State Dependencies
+
+While it is possible to share state between components, this should only be done when necessary. Any component that is associated with a particular state object needs to be re-rendered when that state changes. For this reason:
+
+- Keep state local to a component if possible
+- When sharing state through props, only pass down the specific data necessary
+
+## Reusable Libraries
+
+When publishing a library designed to work with Dioxus, we highly advise using only the core feature on the `dioxus` crate. This makes your crate compile faster, makes it more stable, and avoids bringing in incompatible libraries that might make it not compile on unsupported platforms.
+
+
+❌ Don't include unnecessary dependencies in libraries:
+```toml
+dioxus = { version = "...", features = ["web", "desktop", "full"]}
+```
+
+✅ Only add the features you need:
+```toml
+dioxus = { version = "...", features = "core"}
+```