HTML/CSS preview in Axure. How bad is it?

Question

css

I'm at the design stage for my project. Initially, I thought to do everything in PSD, and then using special services to receive converted HTML / CSS sources for further manual edits and improvements (the level of knowledge in layout is minimal, but still there is + when the layout stage comes, I will actively learn). Those. I don’t plan to make a complete layout from scratch (but if I press it, I can plunge into the sphere).
Now there are thoughts, why not make interactive design in Axure and then not make something digestible from its export to HTML / CSS. But it is repulsive that many people say about the terrible code that comes out. And what attracts me is that I will work with an interactive prototype, you can solve UX / UI issues in the process, and then export to HTML / CSS and start cleaning it (which looks more attractive to me than writing from scratch, see below PS ).
Actually the question is:
Should I start this story with Axure? How big is the amount of changes that need to be made to the code? What are the most common "mistakes" and oversights in exporting? Or is it generally better not to mess with all this and work according to the PSD > Layout strategy?
PS:I ask you to form an answer with the understanding that I have some ideas about layout, but I would not undertake everything from scratch - I'm not sure of my abilities. I'm a fast learner, but this is different...

Answer 1

Axure is interactive prototypes in the first place, layout based on such programs will be almost unreadable. It is better to give your project to a professional for layout, and then, based on the layout, deal with the code, add something to change something. Set yourself the goal of doing exactly the same, sometimes peeping, in my opinion there will be more benefits. Alternatively, find a skeleton similar to your layout and learn block by block.