introduce inlang.com/new as main guided flow for creating new project

[samuelstroschein]

📺 loom

Problem

• The CLI init only works for a subset of users (web devs with node.js installed)
• Thus, we have multiple ways to create a new project that all need to be explained and maintained

Proposal

Have one way to create a new project that works for every user persona via a guided setup on inlang.com/new.

Pros

• no "getting started" explanation (!!!) -> just "create a new project"
• we can hyper optimize that one way an inlang project is created
• less effort because only one way to create an inlang project needs maintenance

Cons

• as long as local repositories are not supported by @inlang/lix, creating a project requires signing-in [BUT strong argument now to push @inlang/project-lisa top open local repos]

Additional information

• @inlang/lix needs less auth requirements ASAP :D Otherwise, users are steered away by the auth scopes

[samuelstroschein]

Overall the UX is just so much better: "Create a new project". Done. Like a simple SaaS.

[Suyashtnt]

we can hyper optimize that one way an inlang project is created

what does this mean? Also some people may not want to use the website to create a project. I know I would much prefer using the CLI or manually creating the files over using a website.

[samuelstroschein]

Users would not be using the website. The /new command opens a window in the browser that guides a user through setting up a project.

Hyper optimizing a new project flow refers to the possibility to analyze the setup experience and improve it in one channel and one channel only.

[samuelstroschein]

clarification - a cli can still be used to create a project

The proposal is a resource allocation question:

"Can we/should we maintain N times flow to create a new project?"

I argue no. Have one guided way to create a new project to deliver the best user experience by optimizing one guided flow instead if N guided flows given resource constraints.

Example user flow in the CLI

The CLI user flow is unguided, no select modules or similar user input is required. The CLI hands-off once guidance is required to inlang.com/new

1. User executes 'inlang project new'

2. CLI creates 'project.inlang.json' file with no installed modules.

3. CLI prompts "should I try to install suitable modules?"

4. tries to auto derive suitable modules, if fails proceeds to step 5

(5. CLI prompts "couldn't derive suitable modules. Do you want to try the guided setup?" If yes, opens inlang.com/new

[Suyashtnt]

What if the project is local only? Would it spin up a localhost server which can edit the files?

[samuelstroschein]

@felixhaeberle step 5 is open the browser and open the local repository.

@Suyashtnt lix can open local repositories in the upcoming months

[jannesblobel]

@Suyashtnt Are you familiar with Lix? Samuel has mentioned Lix a few times, and I can imagine this is new to someone outside the company. :D

[Suyashtnt]

I have no idea about Lix. What is it? I assumed it was a code name for some internal tool

[samuelstroschein]

@Suyashtnt landing page/repo coming soon! TL;DR a version control backend to build apps that can open local and remote repositories :)

[samuelstroschein]

created an issue #1583