At least one cloud service; even if you can't automatically spin up a K8s cluster or whatever, you should be able to set up an app service and deploy your code.
Frontend Stuff
CSS/HTML/Javascript
At least one of React/Vue/Angular
Accessibility, including ARIA and Semantic HTML
How to test frontend code
Mobile/Responsive design
Backend Stuff
Some backend language, and a web development framework for that; .NET/ASP, Python/Django, Ruby/Rails, etc. I know NodeJS exists, but we use Javascript on the frontend because we have to, there are actual good languages for use on the backend.
Some SQL, or at least some method of interacting with databases. An ORM is good, or you can use a statement mapper, or just whatever driver Mongo comes with.
A test framework for their backend stuff; XUnit, Moq, whatever Python and Ruby use.
This is extremely rough, based both on my own priorities and a desire to keep things kinda general.
Thank you for sharing. I'm missing a few points on the list but I'm getting there (can't really decide on the back-end language). Glad you mentioned ARIA, all front-end tutorials seem to forget about them or never mention them.
Welcome. Personally I like C#/.NET for the backend language, but that might be influenced by the fact that I'm working at Microsoft right now.
TBH, something like 60% of dealing with accessibility is a) make sure everything has the right alt/title tags, b) make sure your colors have enough contrast, and c) use the semantically appropriate element. You don't always need to use ARIA, but you should at least know it's there for when you do need it.
Great points, I am actually writing a series of articles related to accessibility these days so I'll definitely keep these in mind. We use C# at work for backend stuff so it might be a good choice.
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.
Must Have Some Basic Familiarity With-
Frontend Stuff
Backend Stuff
This is extremely rough, based both on my own priorities and a desire to keep things kinda general.
Thank you for sharing. I'm missing a few points on the list but I'm getting there (can't really decide on the back-end language). Glad you mentioned ARIA, all front-end tutorials seem to forget about them or never mention them.
Welcome. Personally I like C#/.NET for the backend language, but that might be influenced by the fact that I'm working at Microsoft right now.
TBH, something like 60% of dealing with accessibility is a) make sure everything has the right alt/title tags, b) make sure your colors have enough contrast, and c) use the semantically appropriate element. You don't always need to use ARIA, but you should at least know it's there for when you do need it.
Great points, I am actually writing a series of articles related to accessibility these days so I'll definitely keep these in mind. We use C# at work for backend stuff so it might be a good choice.