Bbo/solo vs pool

[benjaminbours]

The goal was to try to make it as easy as possible for users to understand the choice we offer to them. A pool or not a pool? How are they suppose to know? Technical users they will know of course, but maybe the random dude doesn't and he wants to mine.

I am not expecting this to ever be merged, definitely not a key feature and the layout / purpose is debatable, but it was good to experience this dioxus framework. I am familiar with React and I feel at home with this component base system, even if it's a bit frustrating and weird to write HTML that way.

This PR is still a WIP but any feedback would be appreciated.

For example, I have written a part with custom CSS because I am much faster than to go check tailwind doc for each classes. I also dislike deeply the readability of the HTML with tailwind and I prefer to use CSS naming convention such as BEM. So basically I am not respecting the project's conventions as soon as I arrive. How flexible are we here?

I also noticed a few things if I may.

• Too much things are span in the HTML. HTML semantic is important for content indexation and SEO in general.
• Trying to use tailwind, I realize in the tailwind.css file included in the project, it is missing some classes mentioned in the doc. In my case, I noticed w-1/2 is missing.
• I had to go in the doc of dioxus to find the command to serve with hot reloading. Could be nice to have it documented in the README.

I could create issues for each of these points if I receive a positive confirmation that it could improve the project.