Merge branch 'main' of https://github.com/opral/inlang

Author: samuelstroschein

packages/plugins/i18next/README.md

@@ -1,3 +1,9 @@
+---
+title: i18next Plugin for Inlang - Translation Management
+description: Connect your i18next JSON translation files to your inlang project. Use Fink for translation management, Sherlock for inline previews, and CLI for linting.
+og:image: https://cdn.jsdelivr.net/npm/@inlang/plugin-i18next@latest/assets/banner.svg
+---
+
 # i18next Plugin for Inlang
 
 This plugin enables your inlang project to read and write [i18next](https://inlang.com/m/kl95463j) translation files.
@@ -258,7 +264,3 @@ Run the following commands in your terminal (node and npm must be installed):
 2. `npm run dev`
 
 `npm run dev` will start the development environment which automatically compiles the [src/index.ts](#getting-started) files to JavaScript ([dist/index.js](#getting-started)), runs tests defined in `*.test.ts` files and watches changes.
-
----
-
-_Is something unclear or do you have questions? Reach out to us in our [Discord channel](https://discord.gg/gdMPPWy57R) or open a [Discussion](https://github.com/opral/inlang/discussions) or an [Issue](https://github.com/opral/inlang/issues) on [Github](https://github.com/opral/inlang)._

packages/plugins/json/README.md

@@ -1,10 +1,12 @@
-# What does this plugin do?
+# JSON Plugin for Inlang
+
+> **Deprecated:** This plugin is deprecated in favor of the [inlang message format plugin](https://inlang.com/m/reootnfj/plugin-inlang-messageFormat), which provides a simpler, more robust solution.
 
 This plugin is a general purpose plugin to read and write messages of json files.
 
 > The plugin uses the inlang SDK v1 API but can be used in V2 projects.
 >
-> A slight difference is that `languageTag` is called `locale` in v2 projects. Use `languageTag` for this plugin.   
+> A slight difference is that `languageTag` is called `locale` in v2 projects. Use `languageTag` for this plugin.
 
 ## Manual Installation
 
@@ -121,18 +123,6 @@ An array of strings that are used to ignore certain files. The strings are match
 
 The message IDs are sorted in the order in which they appear in the sourceLanguage file. The nesting or flattening of IDs is detected on a file-by-file basis. If the sourceLanguage file contains nested IDs, the plugin will also create nested IDs in the targetLanguage files. If the sourceLanguage file contains flattened IDs, the plugin will also create flattened IDs in the targetLanguage files.
 
-# Supercharge your i18n workflow by installing the Inlang Visual Studio Code extension (Sherlock)
-
-The plugin can be used with [Sherlock - VS Code extension](https://inlang.com/m/r7kp499g/app-inlang-ideExtension) to extract keys from your code, display inline annotations, have quality checks with [lint rules](https://inlang.com/c/lint-rules) & more. There are only 2 steps to get started:
-
-1. Install: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=inlang.vs-code-extension).
-2. Add the correct syntax matcher:
-   - [m function matcher](https://inlang.com/m/632iow21/plugin-inlang-mFunctionMatcher) or
-   - [t function matcher](https://inlang.com/m/698iow33/plugin-inlang-tFunctionMatcher)
-3. Optional: Add lint rules: https://inlang.com/c/lint-rules
-4. 🎉 Done!
-
-
 # Contributing
 
 ## Getting started
@@ -143,15 +133,3 @@ Run the following commands in your terminal (node and npm must be installed):
 2. `npm run dev`
 
 `npm run dev` will start the development environment which automatically compiles the [src/index.ts](#getting-started) files to JavaScript ([dist/index.js](#getting-started)), runs tests defined in `*.test.ts` files and watches changes.
-
-## Publishing
-
-Run `npm run build` to generate a build.
-
-The [dist](./dist/) directory is used to distribute the plugin directly via CDN like [jsDelivr](https://www.jsdelivr.com/). Using a CDN works because the inlang config uses dynamic imports to import plugins.
-
-Read the [jsDelivr documentation](https://www.jsdelivr.com/?docs=gh) on importing from GitHub.
-
----
-
-_Is something unclear or do you have questions? Reach out to us in our [Discord channel](https://discord.gg/gdMPPWy57R) or open a [Discussion](https://github.com/opral/inlang/discussions) or an [Issue](https://github.com/opral/inlang/issues) on [Github](https://github.com/opral/inlang)._

packages/plugins/json/marketplace-manifest.json

@@ -3,10 +3,14 @@
 	"id": "plugin.inlang.json",
 	"icon": "./assets/icon.png",
 	"displayName": {
-		"en": "JSON translation files"
+		"en": "JSON translation files (Deprecated)"
 	},
 	"description": {
-		"en": "This plugin enables using JSON files for messages. It is not library specific and can be used with any framework."
+		"en": "Deprecated: Use the inlang message format plugin instead. This plugin enables using JSON files for messages."
+	},
+	"deprecated": {
+		"reason": "Use the inlang message format plugin instead.",
+		"replacement": "plugin.inlang.messageFormat"
 	},
 	"pages": {
 		"/": "./README.md",

packages/plugins/m-function-matcher/README.md

@@ -1,33 +1,49 @@
-### Introduction
+---
+title: m Function Matcher - Paraglide JS Integration for Sherlock
+description: Enable inline translation previews and linting for Paraglide JS m.message() function calls in VS Code with Sherlock.
+og:image: https://cdn.jsdelivr.net/npm/@inlang/plugin-m-function-matcher@latest/assets/sherlock-preview.svg
+---
 
-This plugin provides the integration for [Paraglide JS](https://inlang.com/m/gerre34r/library-inlang-paraglideJs)` into the inlang Visual Studio Code extension (Sherlock). It allows you to extract messages from your code, view them inline in the text editor, and get lints for your messages.
+# m Function Matcher for Sherlock
 
-Match examples:
-```ts
-m.myMessage()
-```
-```ts
-m.another_message()
-```
+This plugin enables [Sherlock](https://inlang.com/m/r7kp499g/app-inlang-ideExtension) (VS Code extension) to recognize `m.message()` function calls used by [Paraglide JS](https://inlang.com/m/gerre34r/library-inlang-paraglideJs).
 
+![Sherlock inline preview](https://cdn.jsdelivr.net/npm/@inlang/plugin-m-function-matcher@latest/assets/sherlock-preview.svg)
 
-### Usage
+## What it does
 
-The plugin will automatically extract messages from your code and show them inline in the editor. You can then click on the message to open the web editor and translate the message.
+- **Inline previews**: See translations directly in your code editor
+- **Message extraction**: Extract hardcoded strings into messages
+- **Linting**: Get warnings for missing or invalid message references
 
-1. Install the [Visual Studio Code extension (Sherlock)](https://inlang.com/m/r7kp499g)
-2. Install this plugin
-3. ✨ See your messages appear inline in the editor
+## Supported file types
 
-> There might be a delay before the messages appear in the editor. This is because the plugin needs to be downloaded first. If you want to make sure that everything is setup correctly, reload your workspace.
+- TypeScript (`.ts`, `.tsx`)
+- JavaScript (`.js`, `.jsx`)
+- Svelte (`.svelte`)
+- Vue (`.vue`)
+- Astro (`.astro`)
 
-### Manual installation
+## Installation
 
-```diff
-// project.inlang/settings.json
+Add the plugin to your `project.inlang/settings.json`:
+
+```json
 {
-  "modules" : [
-+    "https://cdn.jsdelivr.net/npm/@inlang/plugin-m-function-matcher@latest/dist/index.js"
-  ]
+	"modules": [
+		"https://cdn.jsdelivr.net/npm/@inlang/plugin-m-function-matcher@latest/dist/index.js"
+	]
 }
 ```
+
+Then install [Sherlock](https://marketplace.visualstudio.com/items?itemName=inlang.vs-code-extension) from the VS Code marketplace.
+
+## Matched patterns
+
+The plugin recognizes these patterns:
+
+| Pattern        | Example                         |
+| -------------- | ------------------------------- |
+| Simple call    | `m.welcome()`                   |
+| With variables | `m.greeting({ name: "World" })` |
+| In JSX         | `{m.button_label()}`            |

packages/plugins/m-function-matcher/assets/sherlock-preview.svg

@@ -7,7 +7,8 @@
 		".": "./dist/index.js"
 	},
 	"files": [
-		"./dist"
+		"./dist",
+		"./assets"
 	],
 	"publishConfig": {
 		"access": "public"