> For the complete documentation index, see [llms.txt](https://divoc.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://divoc.digit.org/platform/configuration/configuring-the-certification-and-verification-component/configuring-certificates/step-3-configure-the-certificate-template.md).
# Step 3: Configure the certificate template
Each country will have a separate certificate template with country-specific branding, and language.
**Steps:**
a. The DIVOC certificate template has been designed in the HTML format. To configure the HTML**-**based certificate template according to your country’s requirement, open [**certificate\_template.html**](https://github.com/egovernments/DIVOC/blob/main/backend/certificate_api/configs/templates/certificate_template.html) and map the dynamic fields in the certificate template.
```
| Beneficiary Name |
Beneficiary Parent Name |
| {{name}} |
{{parentName}} |
```
b. Any modifications that you make (such as combining address fields as a single string) to the address value must be performed in controller.js. The dynamic values will be sent from[ **controller.js**](https://github.com/egovernments/DIVOC/blob/main/backend/certificate_api/src/routes/certificate_controller.js).
```
function prepareDataForVaccineCertificateTemplate(certificateRaw, dataURL) {
certificateRaw.certificate = JSON.parse(certificateRaw.certificate);
const {certificate: {credentialSubject, evidence}} = certificateRaw;
const certificateData = {
name: credentialSubject.name,
parentName: credentialSubject.parentName,
age: credentialSubject.age,
gender: credentialSubject.gender,
identity: formatId(credentialSubject.id),
beneficiaryId: credentialSubject.refId,
recipientAddress: formatRecipientAddress(credentialSubject.address),
vaccine: evidence[0].vaccine,
vaccinationDate: formatDate(evidence[0].date) + ` (Batch no. ${evidence[0].batch} )`,
vaccineValidDays: `after ${getVaccineValidDays(evidence[0].effectiveStart, evidence[0].effectiveUntil)} days`,
vaccinatedBy: evidence[0].verifier.name,
vaccinatedAt: formatFacilityAddress(evidence[0]),
qrCode: dataURL,
dose: evidence[0].dose,
totalDoses: evidence[0].totalDoses,
isFinalDose: evidence[0].dose === evidence[0].totalDoses,
currentDoseText: `(${getNumberWithOrdinal(evidence[0].dose)} Dose)`
};
return certificateData;
}
```
**Note:**
* To check the PDF/print version, which will be generated after an update, open the HTML file in the browser and check for the print preview.
* The page size should be A4 as the HTML is developed according to A4 dimensions.
[](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://divoc.digit.org/platform/configuration/configuring-the-certification-and-verification-component/configuring-certificates/step-3-configure-the-certificate-template.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.