> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/access/local-governance-stack/dashboards-and-analytics/dashboards-and-analytics-service-configuration/dashboards-ui-configuration/dashboards-about-and-faqs.md).

# Dashboards - About & FAQs

About and Purpose page for National Dashboard Enhancement

## Overview - About Page

An about the dashboard page that describes the purpose of the dashboard as well as the source of the data is required to be built as per the feedback received from the demos.

**Web URL:-**[![](https://cdn.jsdelivr.net/npm/@egovernments/digit-ui-css/img/browser-icon.png)**mSeva**](https://qa.digit.org/digit-ui/employee/dss/national-about)&#x20;

The file location in Digit-Dev:- ../modules/dss/src/pages/About.js

The file location in egov-mdms-data:- ../../pb/dss-dashboard/About.json

code

```
{
                        "titleHeader": "DSS_QUES_WHAT_CAN_DASBOARD_VIEWER_SEE_N_DO",
                        "define": [
                            "DSS_ANS_WHAT_CAN_DASBOARD_VIEWER_SEE_N_DO"
                        ],
                        "subdefine": [
                            "FOLLOWING_VIEWER_DO_ON_DASHBOARD"
                        ],
                        "definePoints": [
                            {
                                "point": "PERFORMANCE_METRICS"
                            },
                            {
                                "point": "RESPECTIVE_STATE'S_PERFORMANCE"
                            },
                            {
                                "point": "PERFORMANCES_IN_FORM_VISUALIZATIONS"
                            },
                            {
                                "point": "SERVICE-WISE_PERFORMANCE"
                            },
                            {
                                "point": "YEAR_PERFORMANCE"
                            }
                        ],
                        "subdefinePoints": [
                            {
                                "point": "STUDY_THE_PERFORMANCES"
                            },
                            {
                                "point": "SEE_COMPARISONS_OF_INTER-STATE"
                            },
                            {
                                "point": "SEE_COMPARISON_ON_YEAR-WISE"
                            },
                            {
                                "point": "DOWNLOAD_THE_DATASET"
                            },
                            {
                                "point": "SHARE_DATA_ANALYTICS"
                            }
                        ]
                    }
```

**OUTPUT**

<figure><img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/Oy2dCb65YAAXJ7rfOviy/image.png" alt=""><figcaption></figcaption></figure>

## **Add Content**

To add a question we need to mention `titleHeader`

To add the first point we need to mention `define`

To add the first sub-points we need to mention `definePoints`

To add the second point we need to mention `subdefine`

To add the second sub-points we need to mention `subdefinePoints`

## **Remove Content**

If we need to remove the content we need to delete it according `titleHeader,define,definePoints, subdefine`, `subdefinePoints`

<figure><img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/TQoO6s1Vqg1YcNNuxBvg/image.png" alt=""><figcaption></figcaption></figure>

## **Overview - FAQ Page**&#x20;

To enhance the dashboard and make it more user-friendly, an FAQ page is to be developed so that users can access it from any page for any queries that they may have regarding any acronyms or how to navigate.

**Web URL:-**[![](https://cdn.jsdelivr.net/npm/@egovernments/digit-ui-css/img/browser-icon.png)**mSeva**](https://qa.digit.org/digit-ui/employee/dss/national-faqs)\
\
**The File location in Digit-Dev:- ../dss/src/pages/FAQs**

**The File location in egov-mdms-data:- ../../pb/dss-dashboard/FAQs.json**

**code**

```
{
                        "question": "QUES_THREE_HOW_CAN_I_VIEW_VALUES_GRAPH",
                        "answer": [
                            {
                                "ans": "FOR_PIE_CHARTS"
                            },
                            {
                                "point": "HOVER_OVER_THE_INDIVIDUAL_SLICES"
                            }
                        ],
                        "subAnswer" : [
                          {
                            "ans": "FOR_LINE/BAR_GRAPHS"
                        },
                        {
                            "point": "HOVER_OVER_HE_INE/BAR"
                        }
                        ]
                      }
```

**OUTPUT**

<figure><img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/KWPvGmaOgMfqUAF7jx3k/image.png" alt=""><figcaption></figcaption></figure>

## **Add Content**

To add a question we need to mention `question`

To add the First point we need to mention `answer, ans`

To add the First sub-points we need to mention `answer, point`

To add the Second point we need to mention `subAnswer, ans`

To add the Second sub-points we need to mention `subAnswer, point`

## **Remove Content**

If we need to remove the content we need to delete it according `question, answer, subAnswer, ans, point`

<figure><img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/PaHTD0DInlwTqbI4JGRM/image.png" alt=""><figcaption></figcaption></figure>

#### roleactions.json:- path:- ../../pb/ACCESSCONTROL-ACTIONS-TEST/actions-test.json <a href="#roleactions.json-hardbreak-path-..-..-pb-accesscontrol-actions-test-actions-test.json-hardbreak" id="roleactions.json-hardbreak-path-..-..-pb-accesscontrol-actions-test-actions-test.json-hardbreak"></a>

```
   {
      "rolecode": "EMPLOYEE",
      "actionid": 2373,
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "EMPLOYEE",
      "actionid": 2374,
      "actioncode": "",
      "tenantId": "pb"
    }
```

#### ***actions-test.json:-*** **path:- ../../../ACCESSCONTROL-ACTIONS-TEST/actions-test.json** <a href="#hardbreak-actions-test.json-hardbreak-path-..-..-..-accesscontrol-actions-test-actions-test.json-har" id="hardbreak-actions-test.json-hardbreak-path-..-..-..-accesscontrol-actions-test-actions-test.json-har"></a>

```
{
      "id": 2373,
      "name": "ABOUT DASHBOARD",
      "url": "url",
      "displayName": "About Dashboard",
      "orderNumber": 11,
      "parentModule": "ndss-dashboard",
      "enabled": true,
      "serviceCode": "NDSS",
      "code": "null",
      "path": "NatDashboard.About",
      "navigationURL": "/digit-ui/employee/dss/national-about",
      "leftIcon": "places:business-center",
      "rightIcon": ""
    },
    {
      "id": 2374,
      "name": "FAQS",
      "url": "url",
      "displayName": "FAQs",
      "orderNumber": 12,
      "parentModule": "ndss-dashboard",
      "enabled": true,
      "serviceCode": "NDSS",
      "code": "null",
      "path": "NatDashboard.FAQs",
      "navigationURL": "/digit-ui/employee/dss/national-faqs",
      "leftIcon": "places:business-center",
      "rightIcon": ""
    }
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/local-governance/access/local-governance-stack/dashboards-and-analytics/dashboards-and-analytics-service-configuration/dashboards-ui-configuration/dashboards-about-and-faqs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
