A comprehensive Vue.js-based solution for hotel operations, providing seamless booking management, guest services, transaction processing, and reporting capabilities.
- ποΈ Room inventory management and availability tracking
- π§³ Guest-facing booking portal with self-service options
- π¨βπΌ Staff dashboard for booking administration
- π³ Integrated payment processing system
- π Comprehensive reporting and analytics
- π± Responsive design for all devices
| Configuration | File / Location | Action Required |
|---|---|---|
| API Endpoint | urls.js |
β Set the correct backend API endpoint |
| Backend URL | main.js |
π Set the correct backend hosting: deployed, local, network |
| Backend Connectivity | hrbms-backend |
π Ensure complete integration and successful communication |
Misconfiguration can lead to:
- API connection failures
- Image loading issues
- Data synchronization issues
- Double-check all endpoint URLs
- Test all connections in a staging environment before production
- Avoid hardcoding sensitive data; use the designated configuration files
hrbms-frontend/
βββ src/
β βββ assets/ # Static assets like images, svgs
β βββ components/ # Reusable Vue components
β βββ mixins/ # Vue Mixins
β βββ plugins/ # Vue plugins configuration
β βββ router/ # Application routing
β βββ store/ # Vuex state management
β βββ utils/ # Helper functions and utilities
β βββ views/ # Page components
β βββ App.vue # Root component
β βββ main.js # Entry point
βββ public/ # Public static assets
The application follows a modular architecture with clear separation of concerns:
- Presentation Layer: Vue.js components and Vuetify UI framework
- State Management: Centralized Vuex store for application data
- Service Layer: API integration and third-party services
- Utility Layer: Helper functions and shared logic
npm install # π¦ Installs all required node modules| Command | Description |
|---|---|
npm run serve |
π§ Start in development mode with hot-reload |
npm run build |
π¦ Build for production (minified and optimized) |
npm run lint |
π§Ή Lint and fix code issues |
| Issue | Solution |
|---|---|
| API timeout errors | Check network connectivity and backend server status |
| Authentication failures | Verify correct API credentials in urls.js |
| CORS errors | Ensure backend has proper CORS configuration for your domain |
| Data synchronization issues | Check local storage quota and clear cache if necessary |
| Image loading issues | Verify correct API endpoint in url urls.js |
Use the following emojis to indicate the nature of your commits:
| Emoji | Code | Description |
|---|---|---|
| π― | :100: |
Full functionality implementation |
| π§ | :wrench: |
Code improvement / refactor |
| π | :bug: |
Bug fix |
| π | :bookmark_tabs: |
Documentation and comments |
| β | :coffee: |
Minor or initial changes |
| π§ | :construction: |
Work in progress |
| ποΈ | :wastebasket: |
Code or file deletion |
| π | :notebook: |
README updates |
| βοΈ | :pencil2: |
Typo or naming corrections |
| β»οΈ | :recycle: |
Code refactoring |
| π | :twisted_rightwards_arrows: |
Branch merge |
| βͺ | :rewind: |
Reverting changes |
| π± | :iphone: |
Responsive design changes |
| π | :pushpin: |
Hotfixes |
developer: For main developmentfeature/feature-name: For new featureshotfix/issue-name: For critical fixesrelease/version: For release preparation
- Follow Vue.js style guide
- Use ESLint configuration
- Write meaningful comments
- All API requests must use HTTPS
- Sensitive data must be encrypted at rest and in transit
- User authentication tokens should be stored securely
- Implement proper input validation to prevent injection attacks
- Regular security audits are conducted on the codebase
For security issues, please contact the security team at
spcf.ictdu@spcf.edu.ph.
- π¨βπ» Gabriel Alfonso M. Gatbonton - Senior Frontend Developer
- π¨βπ» Prince Charles M. Clemente - Senior Frontend Developer
- π¨βπ» Rhymeses E. Cortez - Junior Frontend Developer