Creating customizable params for different levels of elements
Opened this issue · 0 comments
This is something I'll be suggesting to the Astra design team tomorrow, but I wanted to open up an issue on it for the sake of recording it and throwing it to the void if anyone has ideas.
I think a key component in Aureus to making it successful will be customization without complication. What I mean by that is something like a Caard website where they are pre-built templates and customization options, but not SO many that it paralyzes the user.
I also want this to be able to be used by really resource-constrained organizations and people. These may be people that have no experience in UI/UX, best practices, etc. So, I want to handle the grunt load of that to enable them to focus on the mission of their resource.
As we develop Aureus for Astra and others, I'm proposing a system of customizable params for each "type" of item - e.g: params for all labels, buttons, views, etc. This will hopefully allow programmatic changes in an easy way while removing the burden.
On a further note, (and a glimpse into our future), I secretly dreamed that if Flutter developed along well enough, Aureus could be a drag and drop web interface tool that requires no actual programming on the user side. This is also a step in potentially supporting that (though not confirmed to be in the roadmap, just another star-specked dream of mine).
That being said, we'll be thinking about this as we continue to evolve Aureus and make it the best it can be. Ideas / comments / gift cards to Starbucks welcome.