Adding New link onto landing page

Bridgeconn · Sep 25, 2023 · b3c665c · b3c665c
1 parent 71de791
commit b3c665c
Show file tree

Hide file tree

Showing 3 changed files with 30 additions and 17 deletions.
diff --git a/app/static/data/services.json b/app/static/data/services.json
@@ -34,18 +34,44 @@
     },
     "auth": {
         "title":"Auth & Access Management",
-        "content":"Access Restriction is implemented for all the endpoints in different levels based on the API’s content priority. User level, Content level, Application level-based security is added to each endpoint. Some of the endpoints are open accessible and others are restricted to user-roles only. User with specific role permission can only access those APIs. Access to endpoints can be done with the help of authorized token. The security implemented for the Vachan Engine contents are based on Role Based Access Control (RBAC) Auwhich restricts the access based on user's role, access-tags etc."
+        "content":"Access Restriction is implemented for all the endpoints in different levels based on the API’s content priority. User level, Content level, Application level-based security is added to each endpoint. Some of the endpoints are open accessible and others are restricted to user-roles only. User with specific role permission can only access those APIs. Access to endpoints can be done with the help of authorized token. The security implemented for the Vachan Engine contents are based on Role Based Access Control (RBAC) Auwhich restricts the access based on user's role, access-tags etc.",
+        "links":[
+            {
+                "link1":"https://github.com/Bridgeconn/vachan-api/blob/version-2/docs/AccessManagement-RBAC.md",
+                "linkname1":"Access Management",
+                "button":"false"
+            },
+
+            {
+                "link2":"https://github.com/Bridgeconn/vachan-api/blob/version-2/app/auth/api-permissions.csv",
+                "linkname2":"API Permissions",
+                "button":"false"
+            },
+
+            {
+                "link3":"https://github.com/Bridgeconn/vachan-api/blob/version-2/app/auth/access_rules.json",
+                "linkname3":"Access Rules",
+                "button":"false"
+            }
+        ]
     },
     "graphql": {
         "title":"GraphQL",
-        "content":"GraphQL module for Vachan Engine is a specification for web APIs that offers a compelling alternative to REST. This module serves as a middle layer between client applications and data sources. With its powerful query language, GraphQL enables declarative data fetching, eliminating the need for over-fetching or under-fetching. Initially implemented using Graphene, we are now migrating to the Strawberry library, ensuring access to the latest GraphQL advancements. It is hosted alongside our REST API services, this integration allows you to leverage the best of both worlds. While REST provides familiar GET, PUT, and POST endpoints, GraphQL empowers you with flexible and precise data retrieval."
+        "content":"GraphQL module for Vachan Engine is a specification for web APIs that offers a compelling alternative to REST. This module serves as a middle layer between client applications and data sources. With its powerful query language, GraphQL enables declarative data fetching, eliminating the need for over-fetching or under-fetching. Initially implemented using Graphene, we are now migrating to the Strawberry library, ensuring access to the latest GraphQL advancements. It is hosted alongside our REST API services, this integration allows you to leverage the best of both worlds. While REST provides familiar GET, PUT, and POST endpoints, GraphQL empowers you with flexible and precise data retrieval.",
+        "links":[
+            {
+                "link1":"",
+                "linkname1":"GraphQL",
+                "button":"false"
+            }
+        ]
     },
     "microservices": {
         "title":"Micro Services",
         "content":"Vachan Engine microservices architecture is broken down into a set of independently functioning services, each serving a specific business capability. These services communicate with each other through well-defined APIs, typically using lightweight protocols such as HTTP or messaging systems.",
         "links":[
             {
-                "link1":"https://miro.com/app/board/uXjVPGg6dwk=/%20",
+                "link1":"",
                 "linkname1":"Microservices",
                 "button":"false"
             }

diff --git a/app/static/scripts/services.js b/app/static/scripts/services.js
@@ -28,18 +28,6 @@ window.onload = loadSeriveData();
 const delay = ms => new Promise(res => setTimeout(res, ms));
 
 
-// async function setServiceContent(serviceName) {
-//     await loadSeriveData();
-//     const currentData = serviceContent[serviceName]
-//     if (currentData){
-//         serviceHeader.innerText = currentData.title;
-//         serviceBody.innerText = currentData.content;
-//     } else{
-//         // failed to get data
-//         serviceBody.innerText = 'something went wrong! Failed to load data';
-//     }
-// }
-
 async function setServiceContent(serviceName) {
     await loadSeriveData();
     const currentData = serviceContent[serviceName];

diff --git a/app/templates/landing_page.html b/app/templates/landing_page.html
@@ -104,6 +104,7 @@
 </head>
 
 <body>
+  <!-- Navigation Bar -->
   <nav class="navbar sticky-top navbar-expand-xl navbar-light bg-light py-2" style="box-shadow: 0px 4px 6px rgba(0, 0, 0, 0.1);">
     <div class="container-fluid">
       <a class="navbar-brand d-flex align-items-center" href="#About">
@@ -153,8 +154,6 @@
   </nav>
 
 
-
-
   <!-- Top Banner -->
   <a id="About"></a>
   <section class="section hero py-5">