From what I know, a general necessary steps/guide of making a well structured website would be:
Analysis (basic visual of the website usage flow, interactions, what happens when, etc...)
Database structure
Layout Design
Development
If anything is missing or you have a different way of work, It would be very helpfull for the rest of us to know of. So please comment below!
Off course somebody would say that these are different "departments" and each one of them is handled by the specific team but I'm really talking of a low/medium complexity website that we can finish on our own (why not learn something new?).
So, I would like to stick on the Designing part...
Designing a website is an area that can "eat" a lot of my time and cause "going back and forth" while developing...
So, I thought of asking in here brothers and sisters, how you proceed on that area?
Which Software or tools are you using for designing your layouts?
I searched in here and found this nice reference from Freddy:
But concidering this is about 5 years old, is there anything more/new that you could propose?
We stick to unified designs. As many know repeatedly creating 'dashboards' that all essentially do the same thing is monotonous to say the least. We decided that one 'look' can suit all (of course if can be branded). Fully responsive, streamlined, great UI and UX, and tested over years by thousands of Users themselves this approach saves us hundreds of hours. Just about every component within Wappler has a 'block' of its own within this. We have already done the layout essentially so we just pick what the Client wants and drag and drop it in.
It fast-tracks Projects and accelerates deployment. We know it inside out. I'd highly recommend this approach. We are not in to wire framing and using tools outside of Wappler these days. We really don't have the time in all honesty.
For everything else there are some truly amazing commercial templates out there that have done it all before so why try to re-invent the wheel... Obviously if a Client wants to go their own way we'll work with them as we have that capacity. But once they realise how much of the budget can be saved by implementing our in-house designs they soon change their minds and tend to go with our suggestions.
Although its not software or a tool it is a great philosophy to adopt. We do use VSC on occasion but this is purely for source code and nothing else. Wappler is our tool and software of choice.
There are literally tens of thousands of professionally designed templates out there - yes, they do take a it of work to 'Wapplerize' but once this is done you end up with a great looking interface that has been tested by many.
I'm with @Cheese on the philosophy of putting the resources where they have the most effect ie. on the backend. Let others do the hard work on the design front. Once clients find out the time / budget savings then 100% of them in my experience agree the same.