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.
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
Vue.js support #1258
Comments
The core team is currently focused on tailoring a good editing experience with React, we're still pre v1.0 and a lot of things are moving. TinaCMS could work with Vue.js, but we'll need help from the VueJS community to adapt and maintain all the packages for VueJS. We could provide guidance in the process if anyone is interested in porting those packages. Maybe it might be worth waiting for VueJS 3.x at this point? |
This is awesome! Definitely needed, but not a small enhancement to take on. The entire Tina UI is built with React. We've talked about converting it to web components (with Stencil) to mitigate this issue. I would take a look at this PR to see some previous discussion. |
hello I'm interested in this, is there any current development that I could help with this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
👀 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
👀 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Please open this issue to track the progression of Vue.js |
Would love to see if there are any plans to add Vue or Nuxt support. |
To have this in the docs as "planned" and then having it basically "dead" for 3 years? Not sure that's the best way to get new customers. I was so excited by finding it to support Vue/Nuxt… guess not. |
Nuxt Studio is built on top of Nuxt Content module and is a really good alternative if you love working with Vue. |
I use netlify to manage markdown content in git in vue nuxt. # start netlify cms, make sure to have a sep port, if running more than one website at a time
# change port in static\admin\config.yml
yarn start:cmsProxy
yarn dev
# navigate to localhost:3000/admin to see cms system here's my package.json {
"name": "nuxt-content-article",
"version": "1.0.0",
"private": true,
"scripts": {
"dev": "nuxt",
"build": "nuxt build",
"start": "nuxt start",
"generate": "nuxt generate",
"lint:js": "eslint --ext .js,.vue --ignore-path .gitignore .",
"lint:style": "stylelint **/*.{vue,css} --ignore-path .gitignore",
"lint:stylefix": "stylelint **/*.{vue,css} --fix --ignore-path .gitignore",
"lint:fix": "eslint --ext .js,.vue --fix --ignore-path .gitignore .",
"lint": "yarn lint:js && yarn lint:style",
"start:cms": "netlify dev --port=8891",
"start:cmsProxy": "npx netlify-cms-proxy-server"
},
"lint-staged": {
"*.{js,vue}": "eslint",
"*.{css,vue}": "stylelint"
},
"dependencies": {
"@nuxt/content": "^1.11.1",
"nuxt": "^2.14.12",
"prism-themes": "1.5.0"
},
"devDependencies": {
"@nuxtjs/eslint-config": "^5.0.0",
"@nuxtjs/eslint-module": "^3.0.2",
"@nuxtjs/stylelint-module": "4.0.0",
"@nuxtjs/tailwindcss": "^3.4.2",
"babel-eslint": "10.1.0",
"eslint": "^7.17.0",
"eslint-config-prettier": "^7.1.0",
"eslint-plugin-nuxt": "^2.0.0",
"eslint-plugin-prettier": "^3.3.1",
"husky": "^4.3.7",
"jquery": "^3.5.1",
"lint-staged": "^10.5.3",
"netlify-cli": "^2.69.10",
"prettier": "^2.2.1",
"stylelint": "13.8.0",
"stylelint-config-prettier": "8.0.2",
"stylelint-config-standard": "20.0.0"
}
} |
Summary
I would love to use tinacms with Vue.js. Vue.js is a great framework with a good learning curve.
Motivation
I'm a vue.js junior dev and we don't have much open source alternative with git-based cms. Tinacms seems very interesting for jamstack websites. I noticed that there was no issue asking for a vue.js support.
List of packages that should be adapted :
The text was updated successfully, but these errors were encountered: