I didn't look into WordPress but I found out it is simple and very easy to use CMS..... I want to dig deeper eventually use it but wondering if I should or not..... cause I don't know its faults or pitfalls, Any advice please

Wordpress is amazing and fucking awful.

Pro:
It's admin dashboard is beautiful, easy to use, and has a lot of features. And it has a ton of plugins you can quickly add.

Con:
The API (for templates, and in general) is just stupid. Like the_post() or get_the_title(). Just global methods floating around, no type of encapsulation/meaningful structure. Another thing to consider, a few of the templates, and A LOT of the plugins haven't been updated in years and are vulnerable to exploits.

@see https://exploit-db.com/search/...

But that being said, it's still totally a viable option. It's just something you have to keep and eye out for.

Answer these questions and I'll give you my recommendation.

Do you know PHP? If not, do you want to learn PHP/MySQL?

How much time do you want to invest on setting up the site?

Is the site you envision just a standard blog, or do you have extra features you want to add.

what are you planning to do? i am using WP from last 6 years, and i never faced any issue. there is wide variety of plugins to provide you automatic security, and other features, you just need to focus on theme design. I even created 2 plugins to show posts in side baar.

@rozzzly I do know PHP and have worked with Code Igniter to create web apps but just found out that for a website there is a CMS which myt help me deliver websites to clients..... as am looking to open an IT company and website dev myt be helpful in running cost

@amitgupta I am a beginner in WordPress so am finding correct resources so as to sharpen my skills..... I am visioning to create websites and later be able to create my own themes and plugins. i will be grateful if you accept to be as one of my mentor

@SirPally I would be happy to sort out your problems related to WP. However as I worked on WP last time around 3 years back, my knowledge may be a bit older. But i'll try my best. You also join WordPress.stackexchange.com

@SirPally You'll hate wordpress then. Any self respecting developer should. It's a steaming pile of crap.

The most commonly used features in wordpress can be bunged together on a framework within a couple of days, so why subject yourself to the horror that is wordpress?

What I've done in the past is:

Make a wordpress install. Use a .htaccess to prevent anyone from visiting the front facing site, but leave paths to the admin dashboard open.

Then make your own front end, like @PiranhaGeorge says, use a framework such as yii or laravel (they're much better than CI)

Then write your ORM models for post, comment, category, to connect to the wordpress tables. If you want, and I would, you can define nice aliases for the wordpresses column names.

For example, the table for posts is named "wp_posts", you would name your model "Posts", and then you can rename/map/alias the columns so that "post_author", and "post_title" become "authorID" and "title" respectively. That might force you to write raw join queries slightly differently because it doesn't have the "post_" prefix for the column name, but that's easy to remedy, and besides the ORM handles all that for you, example:

Posts:where('title', '@rozzzly is awesome')->get() will return the post with that title despite the fact that it uses the pretty name, and not "wp_title"

From there you can use your framework to build anything you want for the front end. AND you get to continue using the wordpress dashboard; since it and the frontend work on the same table.

Beyond that, um disable or highjack the wordpress admin code to block things like "themes" or rewrite some of it to work the way you want. You can also use the wordpress api to add new sections to the admin menu. Then you don't even need to deal with that terrible api because you can just load your framework, and existing models/views/etc into the view that wordpress displays. That way 95% of your development is in your hands, but you still get the dashboard.

You'll probably also want to do something with mod_rewrite to make sure the admin panel has a proper url/subdomain and stuff like "go to live site" work because wordpress still things it's just a standard wordpress installed on the domain's root.

Never ever consider PHP period

I'm all about NodeJS now; same language in the browser and on the server. Allows you to do async stuff unlike php. I do however write in TypeScript (javascript with strict typing).

Also React and Redux are teh shit!!