New backend seeds and documentation adjustments

[dkargatzis]

Title

[Add a short title for your pull request here]

Description

[Describe the changes made by this pull request and why they are necessary.]

Related Issues

[List any related issues or pull requests that this pull request addresses]

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Screenshots (if applicable)

[Include any relevant screenshots to help explain the changes made by this pull request]

Checklist

• I have read the CONTRIBUTING document.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have tested my changes thoroughly.
• I have added tests to cover my changes.
• All new and existing tests passed.

Please add an x inside the square brackets to check off each item in the checklist.

Additional Notes (if applicable)

[Include any additional notes or context that might be helpful for reviewers]

[dimeloper]

I would suggest that we keep the naming structure consistent, like:

(runtime-)language-framework-frameworkVariant

• In this case node-express-js should be node-js-express.
• node-express-mogoose-js should be node-js-express-mongoose.
• node-epxress-starter-js should be node-js-express-starter.

Such a structure except from consistency would also offer better sorting (if e.g. I'm looking for js variants or ts variants)