A guide, instead of an app or module inside of the marketplace, is a piece of content specifically designed to help users with a specific task. Guides are written in markdown and can contain custom web components to make them more interactive.
The unique identifier should always be written in camelCase like this: camelCase.camelCase.camelCase
displayName
Please follow the Apple Style Guide and write the first letter of a new word in the title always in uppercase, e.g. Language Tag. Rule of thumb: The first letter of the first word always has to be uppercase, except your displayName is a name written in lowercase letters everywhere else like npm for example.
description
Please make sure to describe your guide as simple as possible. It is best practice to write 100 to 200 characters.
readme
The readme acts as documentation for your guide and is written in markdown. Feel free to use github flavored markdown, additionally you use inlang's custom web components (doc-elements).
keywords
Keywords are always written in lowercase e.g. i18n, adoptable …
Create a pull request with your changes and wait for approval from our team. Usually, this will take less than 24 hours. After that, your guide will be available on the inlang website.
Feel free to join our Discord if you have any questions or need help with publishing your guide.