Okay, cool, then you know what you need to do (use a separate task/script to generate those in content).
I will add one thing: you can be really terse with the markdown files. For instance, you can generate a content file for each record in your data file, and make the title of the content match a value in the data. Then in that section’s single template you can pull the rest of info over.
So you’d have a file at /content/people/jane.md read:
And then in your /layouts/section/people.html pull in the other info, via named value.
I suggest this, because then you can edit your people info in one file, and the creation task should be a little simpler.
@maiki I kinda like your idea for some things. That’s a good idea.
For the specific task I have in mind, what I’m trying to do is basically import the content pulled from another database. After that, I will just have to maintain this new files that I generated. I could basically delete the yml databases.