`elastic-package create package` of type content, renders the readme template at `docs`

[teresaromero]

When creating a package of type content the template for the readme goes into doc folder.

elastic-package/internal/packages/archetype/package.go

Line 51 in aca24a9

logger.Debugf("Write docs readme")

As the content type package does not have a _div folder, when the command elastic-package check runs the readme updater, it does not detect the content package readme file, so the file goes as template format all along into the build and build zip.

Some solutions for this could be:

• Implement the _dev folder at the content type packages, so the templates land there and they can be updated correctly into the docs
• When creating the content package, go a step ahead and do the render of the readme in that moment. This way the readme file will be static.

[jsoriano]

When creating the content package, go a step ahead and do the render of the readme in that moment. This way the readme file will be static.

I think this needs to be done in any case because it affects all types of packages.