Understanding the DDD Concept

Good,

I'm starting a new application, relatively simple, and I want to structure it in the DDD concept.

I read a lot on the internet, I saw many examples and meanings, but I would like to know more simply.

Given the following structure (the pattern I found most on the internet):

• "Project" .Application: Class Library where my persistence / repository and interface;
• "Project" .Domain: Class Library where mine "Models / Entities";
• "Project" .Infra.Data: Class Library responsible for mapping the models (mapping / fluentAPI);
• "Project" .MVC: Standard MVC project, but without Models and Directly explicit repositories;

Is this structure correct? So I plan to stick with it for my next projects and reshape some that have already been deployed.