4 ms·
Feel the same way but assumed that is just because I am not a front end dev who had better ways to do it. Would like to know what is the current workflow? Supp
by omarhaneef 4y ago
Feel the same way but assumed that is just because I am not a front end dev who had better ways to do it.
Would like to know what is the current workflow? Suppose you have a mockup pencil drawing on a napkin, what is the next step?
Create a header, menu, main, footer and start filling it in?
Go on github and find a design you like?
When do you bring tailwind into it?
- throwaway743 4y agoDon't use a css framework unless you don't know how to design or don't have a designer. In my experience, you end up stripping out/overwriting more than the help it suggests it provides. Also, from concept start to final product, the process is extensive. There are plenty of resources online, but boiled down > start with a concept, research/validation, wires/prototypes, test/reiterate, design exploration, design, test/reiterate, dev, test/reiterate 10+x, release, repeat. Missing a bunch of details and likely steps, but that's the gist.
- omarhaneef 4y agoI'll add this: I don't know how to design and I don't have a designer.
- throwaway743 4y agoAh word. Yeah then ain't no shame in using a framework, but give a shot at styling based on design inspirations you find. Design's just another system with rules.
- mattlondon 4y agoBefore doing anything make sure you get your UX design team/designer/person responsible for what it looks like to finalise the design. Full specs required for fonts, colours, sizing, padding, accessibility labels etc before a single line of code is written is the optimal situation, but not always realistic - get as much as you can agreed first. This is because from experience designers et al like to fiddle around with things a lot before it is "done" so don't waste time coding before the specification is ready. Once you have a stable design/specification to work from you can start - I like to plan out the DOM before writing any code to avoid the excessive "firing arrows" the author struggles with. I generally try to code up the raw HTML first, then progressively add CSS afterwards. I avoid CSS frameworks like tailwind/bootstrap wherever I can as they get you started quicky yes, but in the long run make it harder to get exactly what you want (see previous remake a out designers liking to fiddle)