It is, but as a general suggestion: Skip SFML for now.
It's nice that you'd like to give SFML a try, but in the end you're most likely making things harder for you that way. Start slow.
Learn C++ basics first, focus on writing simple command line/console programs. Once you understand the basics, such as variables, pointers, functions, classes, object lifetime, inheritance, etc. grab SFML and do something more/visual.
While this sounds more boring (which it actually might be from time to time), this allows you to understand a limited subset of functionality/topics first before throwing you even more into the way. Some parts of SFML (or pretty much any bigger library such as SDL) will require prior knowledge to be used properly. For example, SFML's resource holding classes should never be initialized in a static way at the start of your program and they should be freed before you destroy your last window.
If you don't know how scoping works or when objects are actually destroyed, obeying simple rules such as this becomes at least twice as hard for you, probably creating bugs that are really hard to track down (even for more experienced programmers).
