Separate the theme in a dedicated repository #80
Description
We have seen the theme has too much opinion. It's aimed at AmphiBee's usage.
That way, we should version it in it's own repository under the AmphiBee ownership.
If we do so, the app won't have any theme anymore, which is not ideal.
We should then do two things :
- on a regular composer create project pollora/pollora command, we should ask the user to generate a theme from scratch, and let him use the created theme as he wishes.
- Use vite to build files from the theme to the public folder only. (no tailwind, no sass conf, no opionin besides the copy)
- If the user then wants to use tailwind, then he's free to do so or not.
- It's been decided this theme will support blade views.
- on an AmphiBee install, we should script a composer require of the AmphiBee default theme at the right version.
- This theme can hold any AmphiBee opinion