nuxt-modules / nuxt-modules/ionic
docs: Motivations behind this package and limitations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 457
- Forks
- 53
- Avg merge
- 7h 32m
- Merged PRs (30d)
- 21
Description
📚 Is your documentation request related to a problem?
I personally would like to know what are the motivations behind this package, and what are the known limitations or limitations you have been thinking about. It seems quite obvious to me that the goal behind nuxt with ionic allows cross platform development with one codebase and still get the advantages of nuxt. To my understanding, just like with next.js in react world, people are mainly using nuxt for the developer experience and SSR/SSG for SEO performance. Correct me if I'm wrong, but SSR shines for unpredictable data (e.g. user generated data) and SSG shines for stable data. One of my main concern is: do SSR and SSG work in this package? There is this package in next world, but they say SSR doesn't work out of the box.
Lastly, are there any other undocumented known limitations?
Knowing and documenting those two points could help other developers have a sense of a kind of roadmap and contribute more easily perhaps.
🔍 Where should you find it?
Seems like one of the first things to tell. It's always good to start with WHY (see Simon Sinek) in my opinion.
ℹ️ Additional context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing documentation and checking how this Nuxt Ionic package behaves with SSR and SSG. Confirm the package's motivations, supported rendering modes, and other known limitations, then document the verified findings in the introductory documentation so contributors and users can understand the roadmap and constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, nuxtjs, react
- Domain
- documentation, mobile-dev, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100