Miles Murgaw

We should implement some default CSS to make the built projects look slightly better. Similar to how browsers have their own default styles and fonts.

Currently, we have only two panes, the editor and the viewer. We will eventually want more panes, but the current implementation is baked-in. It would be great to have a...

Separate `dxp.css` into multiple different organized css files. Ideally, we could also use SCSS (with hot reloading) for it's ability to have CSS child ids/classes within a parent scope. E.g....

### Request Add a section about manually created signals and when you may want to use them. There is a [short section](https://dioxuslabs.com/learn/0.6/guide/state/#signals-and) about manually-created signals but it only states that...

Setting Default For Signal Props Is Verbose

4

## Request If you have a `ReadOnlySignal` or `Signal`, it can be verbose to use the `#[props(default = x)]` syntax. For example: ```rust #[derive(Props, Clone, PartialEq)] pub struct SomeProps {...

Support Ability To Extend Props From Other Props

2

## Feature Request It'd be helpful to have the ability to extend from another component's props: ```rust #[derive(Props, Clone, PartialEq)] pub struct Comp1Props { abc: bool, disabled: bool, } //...

Adds `ReadOnlySignal::create(T)` which is a shorthand for `ReadOnlySignal::new(Signal::new(T))`. This helps with #3920 Seems like `Signal.into()` also currently works.

## Issue If a prop variable (function argument or struct field) is unused, the unused clippy lint does not go off. This is likely due to the generated builders from...

Adds basic [Parler TTS](https://github.com/huggingface/parler-tts) support using the [Candle integration](https://github.com/huggingface/candle/tree/main/candle-examples/examples/parler-tts). This supports both Mini and Large Parler models. This implementation is very basic with no streaming and limited output methods. I...