[x] Fixed Top Menu (link to the site page where the elements is demonstrated)
[x] Info page
[x] Contact Submission Form
[ ] Logo
It will be an exercise in term learning. Product Manager has to have a perfect knowledge of UI element names. If the difference is minimal we can buy this design.
I can tell you, from my experience of buying themes, that even the best of them have mediocre markup quality (they sell design/visuals and the markup feels like extra burden). So for all real projects we had to apply tons of customizations and basically ended up with "from-scratch" markups each time. My hope is that, as this project is demo project, we won't need that depth.
So the first step is a draft of all pages. The more detailed it will be, the less mistakes we'll make further. The second step is an inventarization of the theme(s). What it provides and what it doesn't.
Again, we should be as thorough and precise as possible. Finally, after we buy a theme, we have everything we need to mock up our pages.
I would rather buy it if it saves time.
It's hard to say what'll save more time: using something like Material UI / Bootstrap or using something like a theme. It depends on the elements we need so we have to make a list of them.
Libraries often have better coverage of low-level elements like buttons.
Themes often have better coverage of high-level elements like registration-pages.
Consider that many themes are made on top of libraries and that is the best case when the design matches your needs.
I suspect a theme will be a better choice but we have to prove that by listing elements we need and elements theme provides side by side.
Moved from https://github.com/AntonKilk/FA_app/issues/2
I propose @AntonKilk, after he succeeds with https://github.com/AntonKilk/FA_app/issues/3 to inspect https://gogo-react.coloredstrategies.com/ and create a list of real widgets 1) we need 2) the theme provides.
Like this:
Theme XyZ
It will be an exercise in term learning. Product Manager has to have a perfect knowledge of UI element names. If the difference is minimal we can buy this design.
I can tell you, from my experience of buying themes, that even the best of them have mediocre markup quality (they sell design/visuals and the markup feels like extra burden). So for all real projects we had to apply tons of customizations and basically ended up with "from-scratch" markups each time. My hope is that, as this project is demo project, we won't need that depth.
So the first step is a draft of all pages. The more detailed it will be, the less mistakes we'll make further. The second step is an inventarization of the theme(s). What it provides and what it doesn't. Again, we should be as thorough and precise as possible. Finally, after we buy a theme, we have everything we need to mock up our pages.
It's hard to say what'll save more time: using something like Material UI / Bootstrap or using something like a theme. It depends on the elements we need so we have to make a list of them.
Libraries often have better coverage of low-level elements like buttons. Themes often have better coverage of high-level elements like registration-pages.
Consider that many themes are made on top of libraries and that is the best case when the design matches your needs.
I suspect a theme will be a better choice but we have to prove that by listing elements we need and elements theme provides side by side.