-### Immediate +### β‘ Immediate
+ +### π‘ During Development + +
+ +
` of target elements with text content that you'd like to extract keywords from.
+- For example, if there is a new **About Us** page:
+
+```jsx copy
+return (
+
+ Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor...
+
+)
+```
+
+### Inspect the public pages file definition
+
+- Open the `"/server/src/scripts/page_indexer/data.js"` file.
+- Observe the Object structure of the elements in the `sites[]` array, eg., the entry for the public "Weather Services" page,
+
+ ```js copy
+ const sites = [
+ {
+ path: 'weather-services',
+ name: 'ACAP Services',
+ info: 'Seasonal and 10-Day Weather Forecasts, and Special Weather Advisory',
+ selectors: [
+ '#contents-seasonal-forecast',
+ '#contents-tenday-forecast',
+ '#contents-special-weather-forecast'
+ ]
+ },
+ ...
+ ]
+ ```
+
+
+ - Failing to add appropriate `"selectors"` will skip indexing the search keywords.
+ - Ensure all public pages load correctly. There will be errors in indexing if a page is inaccessible or has loading errors.
+
+
+### Add a new page file entry
+
+- Create a new entry in the `"/server/src/scripts/page_indexer/data.js"` file under the `sites[]` array corresponding to a newly-created public page.
+- For example, to add the **About Us** page from **step #1**:
+
+ ```js copy
+ const sites = [
+ {
+ path: 'about-us',
+ name: 'About Us',
+ info: 'Information and details about our company',
+ selectors: ['#about-us-content']
+ },
+ ...
+ ]
+
+### Test extracting keywords
+
+- Set `LIVE_ORIGIN=http://localhost:3000` in the server `.env`
+- Run the local website
+ ```sh copy
+ npm run dev
+ ```
+
+- Open `http://localhost:3000` to verify the site is running.
+
+- Run the server NPM script
+ ```sh copy
+ npm run build:page_index
+ ```
+
+ Fix errors that may occur during this step.
+
+- If there are no errors in the previous step, type keyword(s) from the sample **About Us** page in the **Search Bar**, eg.,
+ ```text copy
+ lorem ipsum
+ ```
+
+ The **About Us** page should display in the search results.
+
+ 
+
+### Commit the `data.js` file
+
+If there are no errors in the previous steps and the search keyword(s) appear in **step #4**, proceed to commit and push the updated `data.js` file.
+
+### Deploy
+
+When you push changes, GitHub Actions will automatically run `npm run build:page_index` during deployment. Verify that the new keywords appear in the live Search Bar.
+
+
diff --git a/docs/pages/post-installation/weather-forecasts/tenday-forecast.mdx b/docs/pages/post-installation/weather-forecasts/tenday-forecast.mdx
index 7ecbf10e..df53d210 100644
--- a/docs/pages/post-installation/weather-forecasts/tenday-forecast.mdx
+++ b/docs/pages/post-installation/weather-forecasts/tenday-forecast.mdx
@@ -4,6 +4,10 @@ import { Callout, Steps } from 'nextra/components'
+
+Starting **August 31, 2025**, PAGASA will no longer provide the **10-Day Excel files**. Check the [Announcements](/announcements/pagasa-10day-excel) section for more information.
+
+
## Introduction
ACAP sources its 10-day weather forecast data from PAGASA's public 10-day weather forecast data (available as Excel files from day 1 - day 10) in their **10-Day Climate Forecast** web page at https://www.pagasa.dost.gov.ph/climate/climate-prediction/10-day-climate-forecast.
+
+
+