|
1 | | -# frontend |
| 1 | +<a href="https://discord.gg/FTpBM7xU"><img src="https://img.shields.io/badge/discord-chat-magenta.svg"></a> |
| 2 | +[](https://hub.docker.com/repository/docker/butschster/buggregator) |
| 3 | +[](https://twitter.com/buggregator) |
2 | 4 |
|
3 | | -## Build Setup |
| 5 | + |
4 | 6 |
|
5 | | -```bash |
6 | | -# install dependencies |
7 | | -$ npm run install |
| 7 | +# Buggregator Frontend SPA |
8 | 8 |
|
9 | | -# serve with hot reload at localhost:3000 |
10 | | -$ npm run dev |
| 9 | +Welcome to the official repository for the Buggregator Frontend Single Page Application (SPA), a crucial component of the Buggregator. This repository focuses exclusively on the frontend aspect of Buggregator, developed using Nuxt.js framework and enriched with Storybook for an enhanced component-driven development experience. |
11 | 10 |
|
12 | | -# build for production and launch server |
13 | | -$ npm run build |
14 | | -$ npm run start |
| 11 | +## Overview |
15 | 12 |
|
16 | | -# generate static project |
17 | | -$ npm run generate |
| 13 | +Buggregator is a comprehensive, lightweight server designed for debugging applications written on PHP, JS, etc. This repository is tailored to work seamlessly with the Buggregator server, providing a user-friendly interface and interactive features that make debugging more efficient and less cumbersome. |
18 | 14 |
|
19 | | -# run storybook server |
20 | | -$ npm run sb |
21 | | -``` |
| 15 | +## Contribution |
22 | 16 |
|
23 | | -For detailed explanation on how things work, check out the [documentation](https://nuxtjs.org). |
| 17 | +Contributions to the Buggregator Frontend SPA are always welcome. Whether it's fixing bugs, improving documentation, or suggesting new features, your input is valuable. Please read our contribution guidelines before submitting your pull request. |
24 | 18 |
|
25 | | -## Special Directories |
| 19 | +## Support |
26 | 20 |
|
27 | | -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. |
28 | | - |
29 | | -### `assets` |
30 | | - |
31 | | -The assets directory contains your uncompiled assets such as Stylus or Sass files, images, or fonts. |
32 | | - |
33 | | -More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/assets). |
34 | | - |
35 | | -### `components` |
36 | | - |
37 | | -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. |
38 | | - |
39 | | -More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/components). |
40 | | - |
41 | | -### `layouts` |
42 | | - |
43 | | -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. |
44 | | - |
45 | | -More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/layouts). |
46 | | - |
47 | | - |
48 | | -### `pages` |
49 | | - |
50 | | -This directory contains your application views and routes. Nuxt will read all the `*.vue` files inside this directory and setup Vue Router automatically. |
51 | | - |
52 | | -More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/get-started/routing). |
53 | | - |
54 | | -### `plugins` |
55 | | - |
56 | | -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`. |
57 | | - |
58 | | -More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/plugins). |
59 | | - |
60 | | -### `static` |
61 | | - |
62 | | -This directory contains your static files. Each file inside this directory is mapped to `/`. |
63 | | - |
64 | | -Example: `/static/robots.txt` is mapped as `/robots.txt`. |
65 | | - |
66 | | -More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/static). |
67 | | - |
68 | | -### `store` |
69 | | - |
70 | | -This directory contains your Vuex store files. Creating a file in this directory automatically activates Vuex. |
71 | | - |
72 | | -More information about the usage of this directory in [the documentation](https://nuxtjs.org/docs/2.x/directory-structure/store). |
73 | | - |
74 | | - |
75 | | -## Contributing |
76 | | - |
77 | | -We enthusiastically invite you to contribute to Buggregator Server! Whether you've uncovered a bug, have innovative feature suggestions, or wish to contribute in any other capacity, we warmly welcome your participation. Simply open an issue or submit a pull request on our GitHub repository to get started. |
78 | | - |
79 | | -We use the [help wanted]([https://github.com/buggregator/frontend/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%2](https://github.com/buggregator/spiral-app/issues)2) label to categorize all issues that would benefit from your help in the repository. |
80 | | - |
81 | | -### Why Should Developers Contribute to Open Source? |
82 | | - |
83 | | -Open source contributions, such as to Buggregator Server, present a unique and rewarding opportunity, especially for junior developers. |
84 | | - |
85 | | -Here are a few reasons why you should consider contributing: |
86 | | - |
87 | | -1. **Experiment with New Technologies:** Open source projects can expose you to technologies and frameworks you might not encounter in your daily job. It's an excellent opportunity to learn and try out new things. |
88 | | -2. **Expand Your Network:** Collaborating on open source projects connects you with a global community of developers. You can learn from their experiences, and they can learn from yours. |
89 | | -3. **Improve Your Résumé:** Potential employers often value open source contributions. They demonstrate initiative, technical competency, and the ability to work collaboratively |
90 | | -4. **Learn Best Practices:** Code reviews and feedback in open source projects are valuable learning tools. They expose you to different perspectives and ways to improve your code. |
91 | | -5. **Create Impact:** Your contributions can help others and make a meaningful impact on the project. The feeling of seeing your code being used by others is immensely satisfying. |
92 | | - |
93 | | -**Remember, every great developer was once a beginner. Contributing to open source projects is a step in your journey to becoming a better developer. So, don't hesitate to jump in and start contributing!** |
| 21 | +If you encounter any issues or have questions, feel free to open an issue in this repository. For more detailed discussions or support, join our community on [Discord](https://discord.gg/FTpBM7xU). |
0 commit comments