Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Docs] Missing documentation on how to setup Uno.Extensions in an existing project #2321

Closed
1 task done
agneszitte opened this issue Jun 4, 2024 · 4 comments · Fixed by #2326
Closed
1 task done

[Docs] Missing documentation on how to setup Uno.Extensions in an existing project #2321

agneszitte opened this issue Jun 4, 2024 · 4 comments · Fixed by #2326
Assignees
@eriklimakc
Labels
kind/consumer-experience Categorizes issue or PR as related to improving the experience of consumers kind/documentation Categorizes an issue or PR as relevant to 3rd party dependencies that are consumed by this project triage/untriaged Indicates an issue requires triaging or verification.

Comments

@agneszitte
Copy link
Contributor

agneszitte commented Jun 4, 2024 •
edited
Loading

What would you like clarification on

How to setup Uno.Extensions in an existing project

Similar to what we did for Uno.Themes/Uno.Toolkit here:

Concern?

  • Getting started with Uno

Additional info

At the same time, we should add proper tabs for Wizard Vs Cli when creating a solution for Uno.Extensions
Like for Uno.Themes/Uno.Tookit here:

Instead of having everything like this here:
https://platform.uno/docs/articles/external/uno.extensions/doc/GettingStarted.html#1-creating-the-app
@agneszitte agneszitte added kind/consumer-experience Categorizes issue or PR as related to improving the experience of consumers kind/documentation Categorizes an issue or PR as relevant to 3rd party dependencies that are consumed by this project triage/untriaged Indicates an issue requires triaging or verification. labels Jun 4, 2024
@eriklimakc eriklimakc mentioned this issue Jun 6, 2024
Merged
1 task
@eriklimakc
Copy link
Contributor

As discussed with @nickrandolph privately we're just adding instructions for Single Project template and guiding people to the Migrating to Single Project docs if they are using and older template.

The goal is to move all documents for extensions to just single project.

cc @agneszitte

@agneszitte
Copy link
Contributor Author

As discussed with @nickrandolph privately we're just adding instructions for Single Project template and guiding people to the Migrating to Single Project docs if they are using and older template.

The goal is to move all documents for extensions to just single project.

cc @agneszitte

@jeromelaban what do you think?
We have details for legacy templates for other parts of the documentation for example:

So in my head Uno.Extensions documentation should at least give the same type of info for legacy templates, as not anyone can easily migrate or update in some context.

@jeromelaban
Copy link
Member

If it's possible to keep the original content, sure. If not, let's go for single project.

@nickrandolph
Copy link
Contributor

I think multi-head instructions are going to lead to a lot of confusion. With single project we can simply refer to Features, rather than the package references where it needs the .WinUI suffix in some cases, and not in others

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eriklimakc eriklimakc

Labels
kind/consumer-experience Categorizes issue or PR as related to improving the experience of consumers kind/documentation Categorizes an issue or PR as relevant to 3rd party dependencies that are consumed by this project triage/untriaged Indicates an issue requires triaging or verification.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs: Add guide to Install Extensions in existing app unoplatform/uno.extensions
4 participants
@nickrandolph @jeromelaban @agneszitte @eriklimakc