Hi guys, I have started my career as a web developer and then I moved to internet marketing before about 3 years. Since I have some free time I decided update my web developing knowledge and skills. I can develop websites using WordPress, Squarespace, Bootstrap and Wix.
I am really interested to know other latest things that I should learn to be an up-to-date developer. 
For beginner it good to know simple web builders. Also you should learn Javascript (jQurey).
I beg to differ… if you want to delve into web development, web builders are exactly the kind of thing you’d better steer clear of IMHO. As I understand it, @ireshsl already has some experience with these anyway.
This really depends on what you want to do. Check sitepoint articles for some appetizers. 
As for some basics, @Viktor mentioned jQuery, which is certainly very useful and quite omnipresent. Also have a look at SCSS if you haven’t already – nobody is writing plain CSS any more AFAICT*. And at some point you’ll probably want a template engine like twig (PHP) or handlebars (JS).
But apart from that it’s hard to give flat suggestions. My advice would be to dip into a couple of smaller libraries you can use modularly, rather than full-blown frameworks which might require a lot of learning for rather specific purposes.
*Edit: Just noticed that you know bootstrap… well then you’ll certainly know SCSS as well.
FWIW that’s my take too.
I am…
Fair enough, but why?
Probably because I’m a project manager and not actively developing websites for a living. It serves my purposes, and I’ve yet to get into anything that required me to take what I know further.
Ah okay, thanks. Well yes, I was thinking of a development environment; when setting up a new project deploying an SCSS compiler is a no-brainer, but again, only as far as I can tell. BTW, since SCSS compiles to CSS anyway it’s certainly not required, it just makes life much easier.
In my case, because that’s all I need. I’m not buildimg huge sites, and using any kind of framework is not only unnecessary, but overkill, and makes life more, rather than less, complicated.
I’ve a feeling @PaulOB also prefers to write plain CSS…
Haha ok ok, I stand corrected! 
I just had the impression from my own (limited) experience.
I certainly agree with that! But SCSS is not a framework is it?
I don’t use a CSS pre-processor either. I just seems like one more thing…
Sorry - poorly worded response there. No, it’s not, but the same criteria apply for me. It’s not something I need. I can write plain CSS to do what I want without the need to spend time learning a new system which is superfluous to my requirements.
(I’m not saying there’s no place for it - merely answering your point that “nobody writes plain CSS”.)
You can use Bootstrap without Sass or Less (what the current version is based in). Most people who use Bootstrap are not compiling it themselves.
As far as OP goes, you shouldn’t make the move to a preprocessor before knowing CSS anyway.
Get a strong foundation on HTML/CSS and understand what JavaScript does for you. You can make a large interactive website just using these.
There are a billion tools, workflows, and frameworks you can learn and more changing every day. Skip them all and just get an understanding of the core HTML/CSS/JS and move to these things when you feel you need them.
He singeth my song…
I totally agree that you should learn the basics of html, css, javascript, php etc before you head into the preprocessors and libraries. In the end, if you have an understanding of the foundations, you will have an easier time understanding and being able to use SASS, LESS, JQuery, etc. effectively. (BTW I’ve never used a CSS preprocessor, and at this point in time, have no interest in doing so.)
I may be more of an exception than the rule but I still write in plain css because the way I work none of the pre-processors have anything to offer me that I can’t do more quickly by hand.
Most of my work is for small design companies who send me a PSD and a few hours later I send back the css and html which they then use as templates for the other pages. (I have yet to see anyone who uses a preprocessor being able to keep up with me. By the time they’ve booted all their systems up and running I’ve finished anyway.)
Before I started slowing down on work I was doing 5 of these conversion a week and rarely saw the same page again and thus it wasn’t an issue for me or for the clients.
The only time I’ve needed pre-processors is with complex things like animations where you need to repeat something hundreds of times and then pre-processors are useful for looping through and creating the code more quickly,
I can see the benefit in a medium to large or long standing project to use a pre-processor but to me I find it’s just something else that gets in the way as I like the feel of real CSS:).
As I said in a previous thread I think pre-processors are just something programmers dreamed up just to annoy me
Couldn’t agree more. I definitely see the uses of pre-processors, but there are also definitely cases where they’re not really needed.
What’s your opinion on them, @RyanReese? I’m sure I remember us talking about Sass vs LESS but not, I don’t think, whether you always use them.
So coming into my current job, I “knew” Sass. It’s very easy to pick up if you come from a CSS background. I too, like Paul, thought “let me race a Sass person, vs me with vanilla CSS - See who comes out on top”. I’ve been at this job for near 8 months now and these are my opinionis on Sass (note we PURELY use Sass at work).
If you can establish a base guideline in terms of design, to where you can establish a code base, like our work has, where you have mixins, functions, and other useful Sass-specific functions in there, then yes I can see how a Sass person can develop faster (let’s ignore setup time here, since vanilla CSS would definitely win out here).
Our master code base is written in Sass and it is useful. I like it being in Sass for a few reasons. We make use of several mixins, which can take parameters, which are coded out by default (e.g. hamburger menu sliding from the left, sliding from the right, etc. All of that is pre-programmed and a front end developer just has to select hte differnet option when including the mixin. It’s easier to change the parameter than trying to get a FED to change the transform value.
It does make our life easier.
I agree with this sentiment, some. But I think you are a bit of an exception Paul. You’re not a standard developer. In general, it will speed most developers up. If you knew Sass and your system workflow like the back of your hand, I think it could be useful. However I don’t see you having a need for it. I have a pretty good idea of what you work on and I don’t think you’d benefit too much.
That all being said, if I had to stop working with this company and do freelance work, I probably wouldn’t use Sass, because my designs would vary greatly and I wouldn’t be able to have a consistency in my code base. My freelance clients designs could vary greatly. With this copmany, while our designs can vary greatly, the designs are based on our product. And our code base is written with the product in mind, so all in all, we don’t have to contort very much to meet the designs. It does happen some but it’s not bad. All consistency would be lost outside of this company.
I do see usefulness in a company setting, for Sass, where you are working with a product. Given what I’ve learned at this company, I don’t honestly see how you can NOT use Sass or another preprocessor. However, in freelance, I would highly recommend not bothering with Sass (not saying it wouldn’t be useful though), because of the simple fact you wouldn’t be able to get too much out of it.
Sass has made our work life much easier and it’s great. It made me appreciate Sass and preprocessors and what they can offer All the different branches from which you can customize your website just by changing a few variables. We have a configuration file where we can set all the colors, fonts, image paths (e.g. $image-dir will point to our image folder so in case it ever changes…). There are so much good things about Sass but for small stuff like Paul does, or in a non-company setting where you have a product, I agree with Paul. It’s slow and there’s really no point other than trying to look cool. I think it would actually be slower.
That’s just my two cents. I hope I didn’t leave anything off.
Thanks a lot for all your replies. 
I am sorry but I couldn’t mention that I have a very good experience in web developing. Since my field is internet marketing I am not willing to spend more time to learn to learn new languages and etc. I just want to new content management systems, frame works and other tools that popular in the industry at the moment.
For an example one Squarespace. It doesn’t take time to lean but it’s very useful for me because some my clients have used it develop their websites.
Thanks again guys!
Update
I know HTML and CSS very well and I have developed about 10 websites from scratch. As I mentioned in the first post I have started my career as a web developer. So I know the value of learning new languages. But it’s just not my requirement at the moment. 
If you’re not willing to learn HTML/CSS at a basic level, then there’s no point in trying to learn anything else. The best you’re going to get to is being able to blindly fumble around. You can learn a working knowledge both of these in a couple days.
In the end, you’re just going to waste more time by not understanding what you’re doing and blindly fumbling around trying to get things to work or do something that you want, than it would take to learn them.