project requirements Paraglide Adapters standalone

[linear[bot]]

Context

Users for different paraglide "adapters" need to understand what paraglide is, then choose the adapter, and oftentimes use both paraglide plus the adapter.

"Adapters" are complicated to communicate and hurt conversion.

Proposal

Drop "adapters" from communication.

Sure adapters leverage paraglide js, but do users need to know that? Probably not. They can direct install paraglide-next and run off.

• docs simplified because a user doesn't need to read or understand paraglide js if they are interested in paraglide-x
• adoption simplified because users only need paralide-x instead of paraglide-js + paraglide-adapter-{x}

@inlang/paraglide-js
@inlang/paraglide-next
@inlang/paraglide-astro
@inlang/paraglide-sveltekit
@inlang/paraglide-solidstart

[linear[bot]]

PARJS-18 Make Paraglide Adapters available under new Package names

[samuelstroschein]

@loris.sigrist would it be better for branding to include js or not?

I find myself saying "use paraglide js" and not "use paraglide".

@inlang/paraglide-js
@inlang/paraglide-js-next
@inlang/paraglide-js-svelte
@inlang/paraglide-js-sveltekit
@inlang/paraglide-js-react

[LorisSigrist]

I don't really see the value-add of the JS. I understand that we may want to have non-js packages in future, but those would be served from different package-registries.