feat: Rebrand to License Authority with Govt of Goa branding

- Replace TLAS with License Authority throughout documentation
- Add Government of Goa emblem/logo (Ashoka Chakra style)
- Update frontend branding to match documentation
- Add configurable Swagger API link via VITE_API_BASE_URL env var
- Fix Docker build for VitePress (git dependency, .dockerignore)
- Fix helmet security headers for HTTP deployments
- Add CORS support for VM deployment

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Mahi
2026-02-10 00:46:25 -04:00
parent 435889ee79
commit 6ec8d3236d
34 changed files with 203 additions and 113 deletions

View File

@@ -2,9 +2,9 @@
layout: home
hero:
name: "TLAS"
text: "Tokenized License Approval System"
tagline: Enterprise blockchain infrastructure for government license lifecycle management
name: "License Authority"
text: "Government of Goa, India"
tagline: Blockchain-powered license management for secure, transparent, and tamper-proof government services
actions:
- theme: brand
text: Platform Overview
@@ -12,6 +12,9 @@ hero:
- theme: alt
text: API Documentation
link: /developers/
- theme: alt
text: Swagger API
link: /swagger-redirect
features:
- icon: 🔐
@@ -44,6 +47,20 @@ features:
}
</style>
<script setup>
import { onMounted } from 'vue'
const apiBaseUrl = import.meta.env.VITE_API_BASE_URL || ''
onMounted(() => {
const swaggerLink = document.querySelector('a[href="/swagger-redirect"]')
if (swaggerLink) {
swaggerLink.href = `${apiBaseUrl}/api/docs`
swaggerLink.target = '_blank'
}
})
</script>
---
## Documentation by Role
@@ -60,7 +77,7 @@ features:
## Standards & Compliance
TLAS is designed and implemented in accordance with:
This platform is designed and implemented in accordance with:
| Standard | Scope |
|----------|-------|
@@ -97,7 +114,7 @@ For detailed architecture documentation, see [Solution Architecture](/overview/s
| Component | Version | Release Date |
|-----------|---------|--------------|
| TLAS Platform | 1.0.0 | February 2026 |
| Platform | 1.0.0 | February 2026 |
| API Version | v1 | February 2026 |
| Documentation | 1.0.0 | February 2026 |