UI are directly cut into HTML static pages, is it necessary to write HTML?

as detailed in the title: what I just saw simply surprised me. ideo/3563" rel=" nofollow noreferrer "> directly using the static page cut by UI (the previous minute) or a Baidu library can also explain my guilt.

when I see this place, I feel a little guilty. I always take the marking map given by UI, write the structure a little bit, write the style a little bit, can I not feel guilty? What I did before the relationship was in vain, is it really ill-informed and short-sighted?

so there are two questions:

(1) first of all, I would like to ask UI staff, according to the Baidu document above, you can indeed cut into html, but what I use now are the marked pictures cut by UI colleagues with Sketch, or do I have to tap HTML and css, a little bit? according to your different ways, as a front-end, do I have a more efficient way to work?

(2) secondly, I would like to ask the front-end engineer, if it is really the above implementation, then the front-end is only left to write a little js interaction, excuse me, as a peer, do you usually work so efficiently? Or is my way too stupid?

Note: looking forward to your advice and waiting for your good news.

Mar.18,2021

1.sketch cut directly into html is like, which means that it can improve the efficiency of front-end development engineers, free from writing pages, and do other more and more meaningful things, because essentially measuring dimensions, writing pages is a physical task, as long as you master it skillfully, it is difficult to improve in quantity, which means that there will not be much difference in efficiency between a very powerful person and an ordinary person
2. This method should not be used in large-scale production now, probably because there are several problems

.
1.
2.
3.IE8

3. We do not rule out the possibility that the html that can be automatically generated in the future can be directly used in production, which is also a good thing


  1. No matter what industry, the substitutability of low-end repetitive labor is always the highest. I took a look at the example you gave me. It seems to be based on PS slices. At present, machine learning has achieved the ability to sketch the page infrastructure.
  2. but machines also have certain shortcomings. For example, at present, they are not smart enough to make technology selection for demand, and the front end still has to decide on its own to adopt targeted strategies for different needs. Page layout can only be said to be an auxiliary tool, just like CAD for industrial design. In addition, the front-end structure of the separation of HTML, CSS and JavaScript may also be a threshold, and if MVVM were not so popular, everyone might still be proud of the way they used the original production tools.
  3. tools have to adapt to productivity after all, so they can also be created on their own. If you think your work is repetitive and massive, consider finding wheels / building your own wheels. Don't refuse to grow.
  4. in the final analysis, we should constantly improve our knowledge and strive for "irreplaceable".
MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-7b0908-1cae0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-7b0908-1cae0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?