I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
If you're comfortable building a website based on your projects or the kind of brief you'd expect from a client, then don't wait until you're "ready" or "good enough" at say animations or transitions - because you can always learn more and you'll pass up opportunities. Do the best with what you know now and learn by doing.
You can follow tutorials and videos but applying a new skill to a real world problem is where skills become practical and you reinforce and remember them.
I like the idea of starting with a minimal website and then if it suits the project or the client requests then add things. If you are smart about using an existing theme or saving ideas from websites you like, you can add the frontend polish without coding it from scratch. I've used a Bootstrap theme for example which handles resizing and fading in and out of a navbar. I dig into how it works and I tweak it or I turn it off if it no longer makes sense, but I started from a working case in a complete theme rather than figuring out one CSS line at a time, which can be frustrating for a newbie.
Also I find using bootstrap, bulma, etc. are great CSS frameworks which make it easy to add transitions and similar using a CSS class so it abstracts away from the underlying details. You can always go deeper and see what rules are being applied and override them. For me it is important to prototype quickly and get the behavior working, so I can get fast feedback loop for myself without getting stuck in learning a lot of CSS out of context and trying to add it to my site. I've even used Wix.com to prototype something without coding and then build it with Bulma / Bootstrap components or theme.
Lastly, don't assume what a theoretical client wants before you've talked to them and seen their needs.
Maybe the brief you realize asks for too much pizazz and you turn them down.
Maybe they ask for a specific popping up of text or images from the side of the page and you don't know how to do it - but you spend 30min googling it and making proof of concept and see if they like it. Or maybe their request doesn't ask for transitions and animations, but towards the end of the project after you've decided on colors and layout and content and the form still feels wooden and 1990s, then you can talk with the client about if they want the button to change color or move when it is hovered over and pressed.
And you don't know how to do it yet, but you find a tool like this:
It takes your input and generates a preview and CSS for you and then you copy the CSS bits that make work and you adjust them
So basically I like the learn by doing and learn by example approaches as it means you might have a strength or niche but can always diversify your skills. And once you know how to do something new (like transitions or a gallery) on one client or your demo site, you can now offer that to other clients .
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you're comfortable building a website based on your projects or the kind of brief you'd expect from a client, then don't wait until you're "ready" or "good enough" at say animations or transitions - because you can always learn more and you'll pass up opportunities. Do the best with what you know now and learn by doing.
You can follow tutorials and videos but applying a new skill to a real world problem is where skills become practical and you reinforce and remember them.
I like the idea of starting with a minimal website and then if it suits the project or the client requests then add things. If you are smart about using an existing theme or saving ideas from websites you like, you can add the frontend polish without coding it from scratch. I've used a Bootstrap theme for example which handles resizing and fading in and out of a navbar. I dig into how it works and I tweak it or I turn it off if it no longer makes sense, but I started from a working case in a complete theme rather than figuring out one CSS line at a time, which can be frustrating for a newbie.
Also I find using bootstrap, bulma, etc. are great CSS frameworks which make it easy to add transitions and similar using a CSS class so it abstracts away from the underlying details. You can always go deeper and see what rules are being applied and override them. For me it is important to prototype quickly and get the behavior working, so I can get fast feedback loop for myself without getting stuck in learning a lot of CSS out of context and trying to add it to my site. I've even used Wix.com to prototype something without coding and then build it with Bulma / Bootstrap components or theme.
Lastly, don't assume what a theoretical client wants before you've talked to them and seen their needs.
Maybe the brief you realize asks for too much pizazz and you turn them down.
Maybe they ask for a specific popping up of text or images from the side of the page and you don't know how to do it - but you spend 30min googling it and making proof of concept and see if they like it. Or maybe their request doesn't ask for transitions and animations, but towards the end of the project after you've decided on colors and layout and content and the form still feels wooden and 1990s, then you can talk with the client about if they want the button to change color or move when it is hovered over and pressed.
And you don't know how to do it yet, but you find a tool like this:
It takes your input and generates a preview and CSS for you and then you copy the CSS bits that make work and you adjust them
So basically I like the learn by doing and learn by example approaches as it means you might have a strength or niche but can always diversify your skills. And once you know how to do something new (like transitions or a gallery) on one client or your demo site, you can now offer that to other clients .