Initial import

This commit is contained in:
Flatlogic Bot 2026-05-25 13:16:29 +00:00
commit 923e754c17
871 changed files with 81300 additions and 0 deletions

View File

@ -0,0 +1,13 @@
{
"permissions": {
"allow": [
"WebSearch",
"Bash(npm run build:*)",
"Bash(grep:*)",
"Bash(npm ls:*)",
"Bash(ls:*)",
"Bash(git grep:*)",
"Bash(npx vue-tsc:*)"
]
}
}

17
.env Normal file
View File

@ -0,0 +1,17 @@
# Light Blue Vue - Environment Configuration
# Copy this file to .env.local for local development
# API Configuration
VITE_API_URL=http://localhost:3000/api
VITE_APP_TITLE=Light Blue Vue
# Feature Flags
VITE_ENABLE_ANALYTICS=false
VITE_ENABLE_ERROR_TRACKING=false
# External Services (optional)
# VITE_SENTRY_DSN=
# VITE_GA_TRACKING_ID=
# Google Maps API Key (required for Maps page)
VITE_GOOGLE_MAPS_API_KEY=

14
.env.example Normal file
View File

@ -0,0 +1,14 @@
# Light Blue Vue - Environment Configuration
# Copy this file to .env.local for local development
# API Configuration
VITE_API_URL=http://localhost:3000/api
VITE_APP_TITLE=Light Blue Vue
# Feature Flags
VITE_ENABLE_ANALYTICS=false
VITE_ENABLE_ERROR_TRACKING=false
# External Services (optional)
# VITE_SENTRY_DSN=
# VITE_GA_TRACKING_ID=

39
.gitignore vendored Normal file
View File

@ -0,0 +1,39 @@
# Dependencies
node_modules
# Build outputs
dist
dist-ssr
*.local
# Environment files
.env.local
.env.*.local
# Logs
npm-debug.log*
yarn-debug.log*
yarn-error.log*
pnpm-debug.log*
# Editor directories and files
.idea
.vscode
*.suo
*.ntvs*
*.njsproj
*.sln
*.sw?
# OS files
.DS_Store
Thumbs.db
# TypeScript cache
*.tsbuildinfo
# Test coverage
coverage
# Vite
*.local

46
CODE_OF_CONDUCT.md Normal file
View File

@ -0,0 +1,46 @@
# Contributor Covenant Code of Conduct
## Our Pledge
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
## Our Standards
Examples of behavior that contributes to creating a positive environment include:
* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact@flatlogic.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/

120
CONTRIBUTING.md Normal file
View File

@ -0,0 +1,120 @@
# Contributing to Light Blue
Your contributions are welcome and are greatly appreciated! Every little bit helps, and credit
will always be given.
Please take a moment to review this document in order to make the contribution process easy and
effective for everyone involved.
## Conduct
Please, follow the [golden rule](https://en.wikipedia.org/wiki/Golden_Rule). Be respectful, even to
those that are disrespectful.
## Feedback
Feedback is the breakfast for champions! We'd love to hear your opinions, discuss potential
improvements, architecture, theory, internal implementation, etc. Please, join or start a new
conversation in our [issue tracker](https://github.com/flatlogic/light-blue-vue-admin/issues).
## Documentation
We need your help with improving documentation to the project. This might be the easiest way for
you to contribute, because you don't even need to clone the repo but can edit or create new `.md`
files right from GitHub website as described [here](https://help.github.com/articles/editing-files-in-your-repository/).
## Bugs & Feature Requests
Before opening an issue, please:
* Check [Documentation](https://demo.flatlogic.com/light-blue-vue-admin/documentation).
* Search the [issue tracker](https://github.com/flatlogic/light-blue-vue-admin/issues) to make sure
your issue hasnt already been reported.
* If your issue sounds more like a question, please post it on StackOverflow.com instead with the
tag [sing-app](http://stackoverflow.com/questions/tagged/light-blue-vue-admin).
## Pull Requests
Before you submit a [pull request](https://help.github.com/articles/using-pull-requests/) from your
forked repo, check that it meets these guidelines:
* If the pull request adds functionality, the docs should be updated as part of the same PR.
* Create a separate PR for each small feature or bug fix.
* [Squash](http://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git)
your commits into one for each PR.
* When contributing to an opt-in feature, apply the `[feature/...]` tag as a prefix to your PR title
## Style Guide
We follow [Airbnb's Style Guide](https://github.com/airbnb/javascript) for best practices writing javascript code.
## Commit Message Guidelines
We have very precise rules over how our git commit messages can be formatted. This leads to **more
readable messages** that are easy to follow when looking through the **project history**. But also,
we use the git commit messages to **generate the ngx-admin change log**.
### Commit Message Format
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
format that includes a **type**, a **scope** and a **subject**:
```
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
```
The **header** is mandatory and the **scope** of the header is optional.
Any line of the commit message cannot be longer 100 characters! This allows the message to be easier
to read on GitHub as well as in various git tools.
### Revert
If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of
the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is
the SHA of the commit being reverted.
### Type
Must be one of the following:
* **feat**: A new feature
* **fix**: A bug fix
* **docs**: Documentation only changes
* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing
semi-colons, etc)
* **refactor**: A code change that neither fixes a bug nor adds a feature
* **perf**: A code change that improves performance
* **test**: Adding missing tests or correcting existing tests
* **build**: Changes that affect the build system, CI configuration or external dependencies
(example scopes: gulp, broccoli, npm)
* **chore**: Other changes that don't modify `src` or `test` files
* **relese**: Release version commit
### Scope
The scope could be anything specifying place of the commit change. For example
`menu`, `sidebar`, etc.
### Subject
The subject contains succinct description of the change:
* use the imperative, present tense: "change" not "changed" nor "changes"
* don't capitalize first letter
* no dot (.) at the end
### Body
Optional. Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
The body should include the motivation for the change and contrast this with previous behavior.
### Footer
Optional. The footer should contain any information about **Breaking Changes** and is also the place to
reference GitHub issues that this commit **Closes**.
**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines.
The rest of the commit message is then used for this.
## License
By contributing to Light Blue, you agree that your contributions will be licensed under its
[MIT license](https://github.com/flatlogic/sing-app/blob/master/LICENSE).

21
LICENCE Normal file
View File

@ -0,0 +1,21 @@
MIT License
Copyright (c) 2018 Flatlogic, LLC
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

179
README.md Normal file
View File

@ -0,0 +1,179 @@
# Light Blue Vue - Modern Vue 3 Admin Dashboard Template
[View Demo](https://flatlogic.com/templates/light-blue-vue/demo) | [Download](https://github.com/flatlogic/light-blue-vue/archive/refs/heads/master.zip) | [More Templates](https://flatlogic.com/templates) | [Discord Community](https://discord.gg/flatlogic-community) | [Support Forum](https://flatlogic.com/forum)
[![image](https://user-images.githubusercontent.com/1212194/54691119-c3172500-4b33-11e9-8f2f-1a5e1610dbc5.png)](https://flatlogic.com/admin-dashboards/light-blue-vue/demo)
**Originally a premium product priced at $69+, made available for free in January 2025!**
Looking for a perfect codebase generator for your Startup? Try [Flatlogic AI Web App Generator](https://flatlogic.com/generator).
---
## Why Light Blue Vue?
- **Modern Stack**: Vue 3.5+ with Composition API, TypeScript, and Vite
- **Tons of Components**: Hundreds of ready-to-use UI elements, charts, and more
- **Type-Safe**: Full TypeScript support with strict mode
- **Fast Development**: Vite for instant HMR and fast builds
- **Join the Community**: [Flatlogic Discord](https://discord.gg/flatlogic-community) is where the action happens
- **Free Node.js Backend**: Pair it up with [this backend](https://github.com/flatlogic/nodejs-backend) to go full-stack
---
## Quick Start
1. **Clone the repo**
```bash
git clone https://github.com/flatlogic/light-blue-vue.git
cd light-blue-vue
```
2. **Install dependencies**
```bash
npm install
```
3. **Run the development server**
```bash
npm run dev
```
Navigate to http://localhost:3000/
4. **Build for production**
```bash
npm run build
```
5. **Preview production build**
```bash
npm run preview
```
---
## Available Scripts
| Command | Description |
|---------|-------------|
| `npm run dev` | Start development server with HMR |
| `npm run build` | Build for production |
| `npm run preview` | Preview production build locally |
| `npm run type-check` | Run TypeScript type checking |
| `npm run lint` | Run ESLint and auto-fix issues |
| `npm run test` | Run tests with Vitest |
---
## Features
- Vue 3.5+ with Composition API and `<script setup>`
- TypeScript with strict mode
- Vite 6 for fast development and builds
- Pinia for state management
- Vue Router 4 with type-safe routing
- Bootstrap 5 with Bootstrap Vue Next
- Multiple chart libraries (ApexCharts, Highcharts, ECharts, amCharts)
- Google Maps integration
- FullCalendar integration
- Form validation
- Responsive design for all devices
- Dark-themed UI
---
## Tech Stack
| Category | Technology |
|----------|------------|
| Framework | Vue 3.5+ |
| Language | TypeScript |
| Build Tool | Vite 6 |
| State Management | Pinia |
| Routing | Vue Router 4 |
| UI Framework | Bootstrap 5 / Bootstrap Vue Next |
| Charts | ApexCharts, Highcharts, ECharts, amCharts 5 |
| Maps | Google Maps, amCharts Maps |
| Calendar | FullCalendar 6 |
| HTTP Client | Axios |
| Styling | SCSS |
| Testing | Vitest |
| Linting | ESLint |
---
## Project Structure
```
src/
├── api/ # API services and HTTP client
├── assets/ # Static assets (images, icons)
├── components/ # Reusable Vue components
│ ├── Header/
│ ├── Sidebar/
│ ├── Widget/
│ └── ...
├── composables/ # Vue composables (hooks)
├── directives/ # Custom Vue directives
├── documentation/ # Documentation pages
├── pages/ # Page components (routes)
│ ├── Dashboard/
│ ├── Charts/
│ ├── Ecommerce/
│ ├── Forms/
│ ├── Tables/
│ └── ...
├── router/ # Vue Router configuration
├── store/ # Pinia stores
├── styles/ # Global SCSS styles
├── types/ # TypeScript type definitions
└── main.ts # Application entry point
```
---
## Components
- **UI Elements**: Badge, Card, Carousel, Modal, Buttons, Alerts, Progress, Tabs, etc.
- **Charts**: Line, Area, Bar, Pie, Donut, Sparklines, and more
- **Forms**: Validation, Wizard, Elements, Inputs
- **Dashboards**: Analytics, Visits
- **Pages**: Profile, E-commerce, Calendar, Email, Error pages
- **Maps**: Google Maps, Vector Maps
---
## Available Variants
| | **Material** | **Transparent** | **Classic** | **Sofia** | **Flatlogic** |
|---------------|--------------|-----------------|-------------|-----------|---------------|
| **React** | [React Material Admin](https://github.com/flatlogic/react-material-admin-full) | [Light Blue React](https://github.com/flatlogic/light-blue-react) | [Sing App React](https://github.com/flatlogic/sing-app-react) | [Sofia React](https://github.com/flatlogic/sofia-react) | [One React](https://github.com/flatlogic/one-react) |
| **Angular** | [Angular Material Admin](https://github.com/flatlogic/angular-material-admin-full) | [Light Blue Angular](https://github.com/flatlogic/light-blue-angular) | [Sing App Angular](https://github.com/flatlogic/sing-app-angular) | - | - |
| **Vue** | [Material Vue](https://github.com/flatlogic/material-vue-full) | [Light Blue Vue](https://github.com/flatlogic/light-blue-vue) | [Sing App Vue](https://github.com/flatlogic/sing-app-vue) | - | - |
| **Bootstrap** | - | [Light Blue HTML5](https://github.com/flatlogic/light-blue-html5) | [Sing App HTML5](https://github.com/flatlogic/sing-app-html5) | - | [One Bootstrap](https://github.com/flatlogic/one-bootstrap-template-full) |
---
## How to Contribute
- **Star this repo** - show some love
- **Report bugs** - open an issue
- **Submit PRs** - improvements are welcome
- **Join the [Discord](https://discord.gg/flatlogic-community)** - meet fellow devs
---
## About Flatlogic
[Flatlogic AI Software Engineer](https://flatlogic.com/ai-software-development-agent) builds modern business software so you don't have to. Our AI Software Development Agent helps you generate, deploy, and maintain enterprise applications with minimal effort.
---
## License
This template is free to use under the MIT license. Modify it, extend it, make it your own.
---
> **Questions or feedback?**
> Join our [Flatlogic Community Discord](https://discord.gg/flatlogic-community) or visit our [support forum](https://flatlogic.com/forum).

BIN
__MACOSX/._light-blue-vue Normal file

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Some files were not shown because too many files have changed in this diff Show More