WEB junior engineer (CSS, not considering JS for the moment) means that the project can be completed independently. At least the following capabilities should be available: 1. able to independently complete the project and restore the design draft perfectly. 2. there are very few websites that support self-adaptation and do not support self-adaptation. 3. response-oriented support. After all, there are more and more cross-screen scenarios. 4. I can understand a CSS framework and use it as an introduction to refining my own abstract capabilities to intuitively understand how other people solve code reuse problems. 5. Be able to communicate, learn, and collaborate with other project team members, and be familiar with some coding specifications. However, WEB Junior Engineers (CSS, do not consider JS for the moment) are able to complete the project independently.
At least the following capabilities should be available:
1. able to independently complete the project and restore the design draft perfectly.
2. There are very few websites that support self-adaptation and do not support self-adaptation.
3. responsive support. After all, there are more and more cross-screen scenarios.
4. Be able to understand a CSS framework. As an introduction to refining your own abstract capabilities, you can use it to intuitively understand how other people solve code reuse problems.
5. Be able to communicate, learn, and collaborate with other project team members, and be familiar with coding specifications.
Then, JavaScript is not required at this time. JS is another problem.
====================================
I learned about JS in 1.21 days. This is not a real engineer at all.
2. Videos are basically impossible to teach you, and they won't be so fast. The simplest reason (maybe not appropriate) is to watch 10 thousand years of football. Can you play well. Reply: one month, you know at most what the various attributes are doing. You don't have to step on and fill in traps in real projects all the year round. For example, you may know a lot of words in January, but you may not necessarily write an essay. In actual projects, CSS is written like this. There is an idea, but I don't know or forget how to write the specific CSS. So Google and find something, for example, the common CSS Tricks website has a lot of ready-made code available, and then try the effect in Devtools to solve most CSS programming problems. In fact, it does not take a month to understand the core concepts of CSS, such as selector, pseudo selector, and cascading, it will take less than a month to work with the search engine and devtools.
Transcending CSS: The Fine Art of Web Design
CSS3: The Missing Manual
Kids shoes, the concept of front-end should be put aside. This is very deep. I think we should first set the goal to: learn the basic css and html, and write websites that can be viewed, understand other knowledge systems, such as frameworks and response styles. They can be used easily and cooperate with colleagues. (From the perspective of your goal, I personally think that it is enough for you to finish 5th points after one month's effort)
Learning and using with passion varies from person to person. cross-browser differences take a long time to accumulate. The attributes of some css2 will also be accumulated for a long time. At the same time, css3 is very deep, it also takes a long time to study and accumulate. Optical css? No. You must work with html. Under correction, adaptive design and responsive design are two different concepts. It is unrealistic to grasp them in a short time without mixing a pot of porridge.
It's okay to simply learn whether css can be used to exit the website. It's better to see a lot of problems when someone brings them. I used to have a colleague with no foundation. At that time, I was still familiar with this, some of the things he wrote over the past two months are more skillful than me, but there are still many things that need to be accumulated. It is impossible for him to fully understand and practice those problems. He worked very hard, it is one session shorter than me. As for whether to adopt a responsive approach, whether to standardize standardized coding, and whether to learn more knowledge systems, it depends on your own efforts and learning methods. One month also has to learn, six months also have to learn, two years also have to learn, ten years also have to learn, in short, there is no end to learning.
Finally, I am not a professional front-end developer. I am an amateur. I just need some tools for this technology. However, to learn and use, we must follow the principles of standardization and specialization. We also need to master a lot of knowledge, learn advanced things, and grasp the level of knowledge, which is less demanding, after all, don't rely on it for dinner. Determine the preconditions again:
1. Must it be within one month?
2. Is it zero-based?
---------------------
If there is no foundation,
Capability 1, which can be fully achieved;
Capability 2 & capability 3 can be merged. With your preconditions, I suggest you understand both 2 and 3 as adaptive, although the response type is not completely adaptive. However, you must, within a month ,,,,
Capability 4 may not all be available: It's okay to understand a CSS framework.
But it is difficult for you to "feel" how other people solve the code reuse problem, because it requires experience accumulation.
You do not have a certain amount of work experience. If someone tells you, you may not understand why you want to do so ..
Capability 5 is no problem at all. People have to communicate with each other. A standard is a standard.
----------------------
How can I within a month?
If you are a zero-Basic full-time (30 days) student,
Learning html three days ago;
Learn css in the next week;
Learn html + css cut chart in another week;
Learn compatibility and adaptability in another week;
Four days later, I will study each homepage, Topic Page, content page, CSS file structure, and naming rules of each major website ,,
30 days. Although the time is tight, you can.
----------------------
If you can do what I mentioned above, it means that your learning ability is not bad;
At the same time, you will have some PS with basic image editing capabilities ,,
If you get 4 K in Beijing, it should not be a problem ,,
---------------------
Boldly predict ,,
If you have 4 K employees and have learned some JS and JS frameworks, such as JQ, within three months ,,
So you can change your job after half a year, 6 K can look forward,
After that, it depends on your own efforts ..
That's it.
This is my public account. If you have time, check it out ..
Don't introduce me. I have claimed to be an engineer for a month. You have made me unable to claim to be a zombie for two years. How can I live!
It is possible that the focus is on how much time you can spend and whether you can stick to it.
In a month, you can follow the html, css, and js content on w3c schools to complete the simple page. Then you need to know how to use search to solve the problem.
This process is boring and annoying. But if you stick to it, there will be gains. This answer has already become an advertisement for various users. First, change the junior Web Front-end development engineer in the question to Web page creation or Web page reconstruction. Based on the ability described, this is not a real web Front-end development engineer, but a web page creation.
Second, the subject's question reaches this level in a month, which is unlikely (I am talking about front-end Tips ). Html + css is not as simple as the subject thinks, and of course it is not that difficult as JavaScript. There are no shortcuts to learning. The first item that the subject says can be achieved in a month is already very successful. I still remember that when I first learned css, I downloaded a css2.1 chm manual, all of which were practiced from start to end.
I dare not tell anyone that I have learned css. Simple: Baidu searches for 21 days to learn html, 21 days to learn css, 21 days to learn javascript, and 9 days to rest.
