diff --git a/.babelrc b/.babelrc
new file mode 100644
index 0000000..84c2e57
--- /dev/null
+++ b/.babelrc
@@ -0,0 +1,16 @@
+{
+ "env": {
+ "test": {
+ "presets": [
+ [
+ "@babel/preset-env",
+ {
+ "targets": {
+ "node": "current"
+ }
+ }
+ ]
+ ]
+ }
+ }
+}
diff --git a/.editorconfig b/.editorconfig
new file mode 100644
index 0000000..5d12634
--- /dev/null
+++ b/.editorconfig
@@ -0,0 +1,13 @@
+# editorconfig.org
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..48d2ca2
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,92 @@
+# Created by .ignore support plugin (hsz.mobi)
+### Node template
+# Logs
+/logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+.history/
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# TypeScript v1 declaration files
+typings/
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+
+# next.js build output
+.next
+
+# nuxt.js build output
+.nuxt
+
+# Nuxt generate
+dist
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless
+
+# IDE / Editor
+.idea
+
+# Service worker
+sw.*
+
+# macOS
+.DS_Store
+
+# Vim swap files
+*.swp
diff --git a/README.md b/README.md
index 0e06634..557a022 100644
--- a/README.md
+++ b/README.md
@@ -1,92 +1,69 @@
# shop-pc
-马士兵严选pc
+## Build Setup
-## Getting started
+```bash
+# install dependencies
+$ npm install
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+# serve with hot reload at localhost:3000
+$ npm run dev
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+# build for production and launch server
+$ npm run build
+$ npm run start
+# generate static project
+$ npm run generate
```
-cd existing_repo
-git remote add origin http://internel-git.mashibing.cn/yanxuan-frontend/shop-pc.git
-git branch -M main
-git push -uf origin main
-```
-## Integrate with your tools
+For detailed explanation on how things work, check out the [documentation](https://nuxtjs.org).
+
+## Special Directories
-- [ ] [Set up project integrations](http://internel-git.mashibing.cn/yanxuan-frontend/shop-pc/-/settings/integrations)
+You can create the following extra directories, some of which have special behaviors. Only `pages` is required; you can delete them if you don't want to use their functionality.
-## Collaborate with your team
+### `assets`
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+The assets directory contains your uncompiled assets such as Stylus or Sass files, images, or fonts.
-## Test and Deploy
+More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/assets).
-Use the built-in continuous integration in GitLab.
+### `components`
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+The components directory contains your Vue.js components. Components make up the different parts of your page and can be reused and imported into your pages, layouts and even other components.
-***
+More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/components).
-# Editing this README
+### `layouts`
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
+Layouts are a great help when you want to change the look and feel of your Nuxt app, whether you want to include a sidebar or have distinct layouts for mobile and desktop.
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/layouts).
-## Name
-Choose a self-explaining name for your project.
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+### `pages`
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+This directory contains your application views and routes. Nuxt will read all the `*.vue` files inside this directory and setup Vue Router automatically.
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/get-started/routing).
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+### `plugins`
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+The plugins directory contains JavaScript plugins that you want to run before instantiating the root Vue.js Application. This is the place to add Vue plugins and to inject functions or constants. Every time you need to use `Vue.use()`, you should create a file in `plugins/` and add its path to plugins in `nuxt.config.js`.
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/plugins).
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
+### `static`
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
+This directory contains your static files. Each file inside this directory is mapped to `/`.
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+Example: `/static/robots.txt` is mapped as `/robots.txt`.
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/static).
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
+### `store`
-## License
-For open source projects, say how it is licensed.
+This directory contains your Vuex store files. Creating a file in this directory automatically activates Vuex.
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/store).
diff --git a/assets/scss/global.scss b/assets/scss/global.scss
new file mode 100644
index 0000000..3b8e20e
--- /dev/null
+++ b/assets/scss/global.scss
@@ -0,0 +1,34 @@
+
+* {
+ -webkit-box-sizing: border-box; box-sizing: border-box;
+
+ -webkit-touch-callout:none; /*系统默认菜单被禁用*/
+ -webkit-user-select:none; /*webkit浏览器*/
+ -khtml-user-select:none; /*早期浏览器*/
+ -moz-user-select:none;/*火狐*/
+ -ms-user-select:none; /*IE10*/
+ user-select:none;
+ &:after, &:before {
+ @extend *;
+ }
+}
+body, dl, dd, h1, h2, h3, h4, h5, p, figure, form, ul, ol { margin: 0; font-size: .16rem;}
+ul, ol, input, button { padding: 0;}
+ul, ol, li { list-style: none;list-style-type: none}
+h1, h2, h3, h4, h5 { font-size: 100%;}
+input { border: 0; margin: 0;}
+img { width: 100%;}
+a, button, input, optgroup, select, textarea, img { outline:none; -webkit-tap-highlight-color: rgba(0,0,0,0); }
+a, img { -webkit-touch-callout: none; border: 0;}
+html, body { position: absolute; min-height: 100%; height: 100%; width: 100%;}
+input, textarea, img, button { vertical-align: middle; outline: none;}
+body {
+ font-family: PingFang SC, Microsoft YaHei, Helvetica, STHeiTi, sans-serif !important;
+ color: #333; -webkit-font-smoothing: antialiased; font-smoothing: antialiased;
+ overflow-anchor: none}
+table {border-collapse: collapse; border-spacing: 0;
+ color: #333;}
+a { text-decoration:none;
+ color: #333;
+ &:hover { text-decoration:none;}
+}
diff --git a/components/BsHeader.vue b/components/BsHeader.vue
new file mode 100644
index 0000000..85c89f8
--- /dev/null
+++ b/components/BsHeader.vue
@@ -0,0 +1,18 @@
+
+
+
我是公共页头
+
+
+
\ No newline at end of file
diff --git a/components/UiMoney.vue b/components/UiMoney.vue
new file mode 100644
index 0000000..75d22c9
--- /dev/null
+++ b/components/UiMoney.vue
@@ -0,0 +1,18 @@
+
+
+