Command Center: 8290-6500Police Station: 8551-6401Fire Station: 8874-6177CDRRMO: 8290-6500City Health Office: 8367-3406Mayor's Office: 8871-4343
History

Changelog

Keep track of the latest updates and improvements

Recent Updates

Current
Compare on GitHub
Added
  • `police-clearance` now has a `/service-details/police-clearance` page (#299) — it previously linked out to the `/services/certificates` category page only. The record is renamed "National Police Clearance" (`id` unchanged, so existing links keep resolving), and the `detail` block's `office` gives the current issuance site — the Lingkod Pinoy Center, Basement Level, Robinsons Place, relocated there in May 2024 per PNP Las Piñas' official Facebook announcement — kept independent of `pnp-laspinas`'s own Agency record in `agencies.json` (its City Hall headquarters address, untouched). `processSteps` and `requirements` are transcribed from the PNP's official "How to Apply" guide; both sources are cited per ADR-0005 with `covers` scoping each to what it actually backs
  • Office and Service pages now carry a Data source card with three distinct states, instead of one hedge covering both "no source recorded" and "source recorded but never re-checked" (#243, ADR-0005). With no `sources` at all, the card says we're still documenting where the details came from — about our documentation backlog, not the data's reliability. With `sources` but no `verifiedOn`, it says plainly that the citation was matched to the record after the fact, not recorded by whoever transcribed it, and hasn't yet been confirmed against the original. Only once a source names both what was checked and when does the card state "Checked against source \<date\>". Citation and verification are independent facts — the citation is never gated behind the check — and there is no checkmark or badge in any state, a tick would read as certification this site cannot grant. Shared by both pages through a new `UiDataSourceStatus` component
  • Records can now cite more than one source (#243), for cases like an Office taking its location and hours from the Citizen's Charter but its phone from the city's key-officials directory, because the charter carries no contact numbers. Each cited document is listed, and an optional `covers` field records which fields a secondary source backs. No Office record uses a second source yet; backfilling that is follow-up work
  • Added the `useDataSources` composable, which both detail pages read the verified/unverified gate through, so the rule has one implementation rather than two that can drift (#243)
  • Added the Agency responsible-body tier (`agencies.json` + `Agency` type + `configHelper`/View-resolver accessors) for national government offices in the city, starting with `pnp-laspinas` (Las Piñas City Police Station) (#198, ADR-0004); its location and phone are since verified against their sources, see below (#243)
  • Added the Agency detail page, `/agencies/<id>` (#272), mirroring the Office detail page (#207): identity, contact and location resolved through the `agencyView` facade (ADR-0002), plus the Services the Agency provides. It reuses the shared `UiDataSourceStatus` component for provenance instead of a second hand-rolled Data source card (#243, ADR-0005) — `pnp-laspinas` is the first record whose verified sources render anywhere. The Agency responsible-body card on `/services/<category>` now links to this page instead of surfacing a bare `tel:` contact
  • Added an optional `facebook` field to the Agency schema/type (#295, follow-up to #272), mirroring the field Office already carries — same name, type, and Contact-details-card rendering (a real link, "Facebook Page" text, opens in a new tab with `rel="noopener noreferrer"`). `pnp-laspinas` already cited its official Facebook page in `sources` for provenance (ADR-0005), but provenance isn't a contact channel, so `sources` was never read for this — `agencies.json` now also carries the URL as `facebook`, and the Agency detail page's Contact details card renders it next to Phone
  • Added a "National Agencies" section to `/government` (#295, follow-up to #272), reading through the existing Agency `configHelper` accessor. Kept as its own section rather than folded into "Key Offices" — ADR-0004 deliberately separates the Office tier (city departments, RA 7160) from the Agency tier (national government offices with a local presence), the same call `sitemap.vue` already made for its own "National Agencies" section in this same PR. The section matches the rest of the page's visual convention exactly (same wrapper/padding, alternating background, `UiSectionHeader` primary-blue badge, card and grid) — the tier distinction is carried entirely by the section's own heading and "not part of its own structure" description line, not by a different badge or card treatment. It's the last section on the page, below Barangays
  • Added a `/barangays` page rendering the Barangay directory (the 20 `subdivisions.json` records), reading through the same accessor as `government/index.vue`'s Subdivisions section, and linked it from the main nav between Government and Statistics (#198)
  • Added the Barangay responsible-body tier (`Service.providedByBarangay`): Barangay-level Services now link to the `/barangays` directory instead of a stand-in Office record (#198, ADR-0004)
  • The Government page's Key Offices cards now show the Office's Facebook page as a clickable link alongside its phone and email. The card is no longer itself the anchor — an `<a>` inside an `<a>` is invalid HTML, so the "View office" CTA carries the link and stretches over the card, which keeps whole-card click-through while letting the Facebook link sit above it (#199)
  • Added official Facebook pages for five more Offices — `cswdo`, `city-agriculture`, `city-engineering`, `city-planning` and `cdrrmo` — which render as a Facebook Page link on each Office page. `civil-registry` and `city-health` already carried theirs; the `facebook` field and its rendering are pre-existing (#199)
Changed
  • The Agency detail page's breadcrumb and bottom back link no longer route through `/services` — an Agency is not a Service (#295, follow-up to #272). Repointed to `/government` (Government -> agency name), matching the Office detail page's own crumb shape; the back link now reads "All national agencies" instead of "All services", consistent with the new National Agencies section it links to. `/government`'s SEO description and hero copy were also updated to mention national agencies now that the page carries that section
  • Redefined `verifiedOn` in ADR-0005 (#243): transcribing a value out of a source IS confirming the record against it, so `verifiedOn` is set at transcription time, not held back for a separate audit pass. Re-checking the SAME source later bumps that source's `verifiedOn` in place — there is deliberately no separate audit/proofread date, since a proofread makes the identical claim as the transcription, only fresher, and a second field would only encode the confidence gradient `#237` already rejected. Checking a DIFFERENT source, or a live confirmation (e.g. a phone call), adds a new `sources[]` entry instead — the ADR now documents that a source need not be a document, provided it's named specifically enough to repeat (which office, which channel), mirroring the existing rule against citing a contributor's own photo or scan
  • Provenance is now an ordered `sources[]` array on Service, Office and Agency, replacing the single `sourceUrl` / `sourceName` pair; all 16 existing records were migrated, and the Office/Service Data source card now renders three distinct states off it (see above) instead of the one hedge it showed before (#243, ADR-0005). Trust is derived from what a record cites, never asserted by a status field — the Agency-scoped `dataStatus` enum is deleted, and ADR-0005 supersedes the deferred generalized flag noted in ADR-0003 and ADR-0004
  • A cited document is hyperlinked only when the issuing authority publishes it online, and rendered as plain text otherwise (#243, #238). Most Las Piñas citizen's charters are tarpaulins at the office window or PDFs handed over on request, so a link is not evidence of verification and its absence never marks a record unverified
  • The Service page's "Verified Source" card is renamed "Data source" and now states a check only when one has happened (#243). The old heading claimed verification for records that had never been checked against anything
  • Unified `officials.departments[]` with the canonical `Office` entity so a city office is modelled once (#199, ADR-0003): `officials.json` now holds people only — each department head is an `Official` with an `officeId` pointing at the Office it heads — while office identity, description and contact live solely in `offices.json`. The `abbreviation` moves onto `Office`, and the department's lossy `services` field (Office → one Category) is dropped in favour of the canonical `Service.providedBy` direction
  • The Government page's "Key Offices" section now renders Offices joined to their heads through the `configHelper` accessor layer, grouped by Office Group; it replaces the dead placeholder grid that read `officials.departments` directly and linked the retired `/service-details/<slug>` namespace (#199, also removes one of the two dead blocks listed in #234). The head's name is not published: the incumbent names carried over from the old `officials.departments` data are unsourced and may name people who have left office, so the join decides which Offices appear but the person stays hidden until verified (#279)
  • A Service's responsible body now resolves through three tiers — Office, Agency, Barangay — instead of Office alone; the "Responsible Offices" section on `/services/<category>` is renamed "Where to Get This" and renders all three (#198, ADR-0004)
  • Removed the `barangay-hall` and `police-station` stub `Office` records from `offices.json`; `barangay-clearance`, `barangay-id`, and `police-clearance` are repointed to their new Agency/Barangay tiers instead of a fake Office (#198, ADR-0004)
  • Moved `useLanguage`'s ~400-line inline dictionary out of the composable into three per-locale data files, `app/config/language/{en,fil,ilo}.json` (#256). Adding or correcting a translation is now a data change — edit or add a JSON file — instead of editing composable source and redeploying; `useLanguage` itself keeps only selection/lookup behaviour, and its public surface (`language`, `setLanguage`, `translate`) and every rendered string are unchanged
  • `.husky/pre-commit` now lints only staged files via `lint-staged`, instead of running `pnpm lint` (full-repo `eslint .`) on every commit (#246). An untracked scratch file at the repo root — one the commit doesn't even touch — could fail the commit under the old hook; `pnpm lint` invoked directly still lints the whole repo, and `ci.yml`'s full-repo lint/typecheck/test gate on every PR is unchanged. Typecheck and test stay repo-wide in the hook too, since they're whole-program checks a staged-file subset can't answer
  • Recategorized `cedula` (Community Tax Certificate) from `business` to `tax-payments` (#285, per #255's ruling, ADR-0006) — it's a tax paid to obtain a document needed for many unrelated reasons, not business-exclusive. Also fixed its `url` from the stale `/services/business` to `/services/tax-payments`, matching its new category's own href, since `pageViews.ts` treats a `url` that differs from the resolved category href as an explicit override link — left stale, Cedula's card would have silently linked back to the Business category page
Removed
  • Retired the `government` Service Category outright, with no replacement (#286, per #255's ruling). Zero Services ever referenced it, and its stated contents ("general city services, property management, and personnel records") are Office-page material under ADR-0003, not Category material. Pure deletion from `categories.json` — `getServiceCategories()`/`getCategoryBySlug('government')` already excluded it as hidden, and now it's simply gone rather than gated
  • Retired the `online` Service Category (#288, per #255's ruling, ADR-0006): it modeled a delivery channel, not a task a resident came to do. All 5 of its Services were duplicate online-delivery records of a Service already cataloged under Business/Taxation and are deleted outright — `online-business-billing`/`online-rpt-billing` duplicated `business-tax`/`real-property-tax` respectively (View & Pay bills), `online-new-business` duplicated `business-permit-new`, `online-business-renewal` duplicated `business-permit-renewal`, and `online-payment-order` ("various city fees") had no confident 1:1 match and is likewise deleted rather than force-merged. The two Business counterparts (`business-permit-new`, `business-permit-renewal`) already carried a verified `detail.onlineLink` to `https://cityoflaspinas.ph/`, so no new field was needed there. `business-tax` and `real-property-tax` have no identified online channel — no delivery-channel fact was recorded for them, and no new field was introduced. (Las Piñas does not use any third-party e-payment platform for these services; an earlier pass of this work incorrectly attributed the duplication to one — corrected.) `categories.json`'s `online` entry is deleted; `navigation.json` never referenced it (confirmed, no-op there, same as #286/#287)
Fixed
  • The site served no crawlable icon at all — no `apple-touch-icon`, no web manifest, no `rel="icon"` link, only an implicit 32px `/favicon.ico` (699 bytes), which is under the 64px floor the Better LGU Directory's crawler requires and left betterlaspinas.org one of only three Active portals with no logo in its logo wall (#310). Generated `apple-touch-icon.png` (180×180), `icon-192.png` and `icon-512.png` from the colour brand mark (`public/assets/images/logo/better-laspinas-logo.svg`), recolouring its navy landmass to light grey (`#CED4DA`) and compositing it plus the mark's yellow sun onto a solid navy `#0032A0` ground — matching the palette already shipped in `favicon.ico` and `opengraph.png`, not the `#0066eb` UI theme colour, which is a different token from the icon's brand-mark ground. `public/favicon.svg` was rebuilt the same way (navy background rect + recoloured landmass) instead of staying a byte-identical copy of the transparent-background colour SVG, since a transparent navy mark is unreliable on a dark browser tab strip. `public/site.webmanifest`'s `background_color` (the splash-screen ground) now matches at `#0032a0`; `theme_color` (browser-UI tint) is left at `#0066eb`, tracking `site.json`'s `themeColor` as a legitimately distinct token. Linked all three icons plus `rel="manifest"` in `nuxt.config.ts`'s `app.head.link`. `/favicon.ico` is kept as the legacy fallback. No PWA module is configured (re-verified) and no CSP change was needed — `manifest-src 'self'` and `img-src 'self' https: data:` already permit same-origin manifest/icon requests
  • A Service's Category display name is no longer stored on the Service record — it's derived from `categoryId` through the Category record at read time (`getServiceCategoryName`, and `toServiceDetailView`'s `categoryLabel`/`categoryHref` for `/service-details/<id>` breadcrumbs), so it can no longer disagree with itself (#245). It already had: 5 of 12 Categories (`agriculture`, `environment`, `infrastructure`, `public-safety`, `social-services`) carried a different display name on their Service records than on the Category record, invisibly, because nothing enforced agreement. `ServiceItem.category` and `ServiceDetail.category`/`categoryLink` are removed from the type, schema and `services.json`; `categoryId` becomes required (already present on 100% of records). `services.schema.json`'s `additionalProperties: false` now makes reintroducing either field a validation failure, not just a lint nit — `pnpm validate` fails on it, case added to the test suite
  • Fixed the Data source card understating a multi-source record's strongest state: when every source is independently verified, the summary line said only "Sourced from these documents.", the same neutral copy shown when none are — a resident could not tell a record where both documents were checked from one where neither was (#243). `UiDataSourceStatus` now asserts "Checked against all sources." when all of a record's sources carry `verifiedOn`, without naming a date — sources can carry different `verifiedOn` dates, and the record-level `checkedOn` is only the most recent of them, so a single date in the summary would misstate the others; the per-entry lines already carry each source's own date. The wording covers two sources and three-or-more without branching, and the mixed case (some verified, some not) is unchanged — it still reads "Sourced from these documents." and asserts no check, which was the fix landed in 4dbd0d5
  • Reworded the Data source card's state-2 copy from "Matched to this document after the fact. Not yet confirmed against the original." to "Sourced from this document. No check recorded yet." (plural: "these documents") (#243). "After the fact" was internal jargon, "the original" contradicted the citation named immediately above it, and the old wording read as an imperative-adjacent warning even though state 2 is meant to be as neutral a statement of record as state 3 — "no check recorded" describes our log, not the data's reliability
  • Fixed the Data source card misrepresenting a multi-source record when only some of its sources carry `verifiedOn` (#243): `useDataSources`' `verifiedOn` is the most recent date *across* all sources, so a record with one checked and one unchecked source still rendered a single "Checked against source \<date\>" line covering both. `UiDataSourceStatus` now renders each source's own status inline whenever the sources in a record don't all share the same verified state, and the summary line beneath the list drops to a neutral "Sourced from these documents." rather than asserting a check that not every entry has. Single-source records are unaffected — they still render exactly as before
  • Removed the duplicate, dead `sources` slot the schema carried on `officeDetail` alongside the real one on `office` (#243): only the `office`-level `sources` has a TypeScript counterpart and renders on the Office page, so a record written into the `detail` block would have validated silently and never surfaced, misleading a future contributor into thinking detail-level provenance is supported. No `offices.json` record used it. `services.schema.json` and `agencies.schema.json` were checked for the same pattern and don't have it — Service provenance lives only on `serviceDetail.sources` (genuinely read via the resolved detail view) and Agency provenance only on the top-level `agency`
  • Restored `pnp-laspinas`'s second source (#243): the record had migrated to a single citation, dropping the official Facebook page that backs its address alongside the LGU key-officials directory that backs its phone. `covers` now attributes `location` to the Facebook page and `phone` to the directory, primary (directory) first. Both sources also carry `verifiedOn: 2026-08-03`, matching the author date of the commits recording that a human directly checked the address and landline against both sources on that date — a real check the deleted `dataStatus: "verified"` used to encode and that `covers` now lets us restore without overclaiming the rest of the record, since `name`, `description` and `icon` are covered by neither source
  • Added a `pattern` requiring `verifiedOn` to be `YYYY-MM-DD` in the `agencies`, `offices` and `services` schemas (#243). `useDataSources` picks the most recent `verifiedOn` by raw string comparison, which is only correct for zero-padded ISO dates; the pattern makes that assumption enforced rather than implicit. `published` gets no such pattern — nothing computes from it, and its documented shape is a bare year, e.g. `"2022"`. This is a format check, not the honesty check ADR-0005 deliberately leaves to render — a regex confirms a date is well-formed, not that the record was actually checked
  • Keyed the Data source card's source list on `name` plus index instead of `name` alone, in both `offices/[slug].vue` and `service-details/[slug].vue` (#243): nothing enforces `name` uniqueness within a record's `sources[]`, so a repeated name previously wasn't a stable key
  • Backfilled `verifiedOn` on Citizen's Charter citations that were already checked against the source, scoped honestly via `covers` rather than blanket-stamped (#243). `city-engineering`'s Office record gets `covers: ["phone"]`, `verifiedOn: "2026-08-05"` — the charter's own "Contact Information" line for that office names `8873-3004`, matching the stored number, and `docs/citizens-charter/city-engineer.md` has since been verified line by line against the source PDF (#213). All 8 charter-cited Services (`business-permit-new`, `business-permit-renewal`, `special-permit`, `business-status-certificate`, `ctc-business-license`, `occupational-permit`, `occupational-permit-jobseeker`, `safety-seal`) get `covers: ["fee", "processingTime", "quickStats", "requirements", "processSteps", "faqs"]`, `verifiedOn: "2026-08-05"` — `docs/citizens-charter/business-permits.md` was fully verified line by line against the PDF in the same `#213` pass, and drift found there was already corrected into `services.json`. The other 6 Offices citing the charter (`civil-registry`, `city-treasurer`, `city-assessor`, `cswdo`, `city-planning`, `city-health`) are left at state 2, unstamped: their charter transcriptions document transactions only, not office-level contact/location/hours fields, so there is nothing to honestly scope `covers` to. `city-assessor` specifically is NOT stamped for phone or email — its transcription still carries the "verify against the PDF" caveat unresolved, and the phone number it prints is separately flagged `_(verify)_` and known wrong (a 4/6 transposition, per #199/#281). `city-planning`'s only charter-listed phone number belongs to the Public Relations & Information Office's feedback line, not the office's own — it doesn't match the stored number at all
  • Replaced six Office phone numbers that were all the same `(078) 326-5001` placeholder — a Cagayan Valley area code, not Las Piñas (#199). Five now carry the number published in the city's key-officials directory, which independently agrees with the number held by the department record each Office duplicated: `city-treasurer` `(02) 8871-4339`, `city-assessor` `(02) 8874-6781`, `city-agriculture` `(02) 8519-5687`, `city-budget` `(02) 8511-0779`, and `city-general-services` `(02) 8871-6195`. `city-accounting` is left blank because the two sources disagree, as is the new BPLO record and `human-resource-management`, which the directory does not list; sourcing those three is tracked separately. Note that `docs/citizens-charter/city-assessor.md` transcribes the assessor's number as `8874-4781` and is flagged for verification — that transcription is wrong
  • Added a missing `Office` record for the Business Permits & Licensing Office (`business-permits-licensing`), which had a department entry but no canonical Office (#199, ADR-0003). Its phone is left blank for the same reason
  • Corrected the City Civil Registry abbreviation from `MCR` (Municipal Civil Registrar — a pre-cityhood holdover) to `CCR`, and dropped the abbreviation from the `CSWDO` and `CDRRMO` Office names, which now carry it in the dedicated `abbreviation` field instead of rendering it twice (#199)
  • Normalised the City Engineering Office phone to `(02) 8873-3004`, matching the area-code format every other Office uses, and added the City Social Welfare & Development Office's landline `(02) 8403-7045` from the city's key-officials directory; the mobile number it previously carried in the `phone` field moves to `mobile` (#199)
  • Restored the City Planning & Development Office phone `(02) 8872-0921`, which was dropped alongside the `(078) 326-5001` placeholders even though it was never one of them (#199). It comes from the department record the Office absorbed, not from the Citizen's Charter the record cites in `sourceName`; per-record provenance is #243's job and this record's source label should be revisited when that lands
  • Resolved the `CAO` abbreviation collision between the City Assessor's Office and the City Agriculture Office (#199): the City Agriculture Office publishes `CAO` as its own official handle, while the city's directory lists the assessor as plain "Assessor" with no acronym, so the assessor's abbreviation is dropped. `pnpm validate` now rejects two Offices sharing an abbreviation
  • Corrected the Building Permit processing time to 5 days (was "5-10 days"), matching the DAY 1 – DAY 5 step table in `docs/citizens-charter/city-engineer.md`, which was verified line by line against the source PDF (#213)
  • Corrected BPLO service fees and processing times that had drifted from the Citizen's Charter, after verifying `docs/citizens-charter/business-permits.md` line by line against the source PDF (#213): Occupational Mayor's Permit (Regular) is ₱250 (was "Varies by Assessment") and takes ~1 hour 35 minutes (was ~3 hours); the First Time Job Seeker permit takes 1 hour 30 minutes (was ~3 hours); Business Permit Renewal takes 3 hours 10 minutes (was ~3 hours); Certificates on Status of Business and Certified True Copy both take 1 hour (were "Approx. 1 hour")
  • Fixed the service search's category chips, popular-search list, and recent-search history all being narrowed to a soft-launch subset behind commented-out `TODO`s, well after the gated content shipped: category chips now derive from `getServiceCategories()` filtered to categories with at least one live service (plus a restored "All" chip so the filter can be cleared from the UI), the curated popular-search terms are re-validated against live services at runtime instead of hand-uncommented, and recent searches are no longer silently dropped by a stale whitelist (#233)
  • Fixed the production build failing on `[postcss] ENOENT ... open '<root>/tailwindcss'` after Nuxt 4.5.1 (#266) pulled in Vite 8: `app/assets/css/main.css` now imports `tailwindcss/index.css` instead of the bare `tailwindcss` specifier, which Vite 8's bundled postcss-import cannot resolve
  • Fixed the Privacy Policy describing analytics, cookies, and automatic data collection this static site doesn't do; it now states plainly what the site actually stores (language and recent searches, kept on-device) and what its host (Cloudflare Pages) logs on its own (#258)
  • Fixed Terms of Use asserting a blanket public-domain grant that contradicted `LICENSE`; it now states the two/three-way split that `LICENSE` actually grants — official government source data outside copyright, presentation content under CC BY 4.0, source code under MIT (#258); its section anchor is renamed `#public-domain` → `#content-licensing` to match (#258)
  • Fixed page content touching the screen edges at certain viewport widths by setting the container's max-width below each breakpoint
  • Fixed pre-commit going red on any checkout with agent worktrees or root scratch files present: `vitest.config.ts` now excludes `.claude/**`, and `.gitignore` now excludes `.claude/` and common scratch-file patterns so repo-wide `eslint .` no longer trips on them (#230, #231, #232)
  • Anchored the agent scratch-file `.gitignore` patterns (`.scratch/`, `research.md`, `architecture-review.html`, `HANDOFF-*.md`, `handoff-*.md`, `.antigravitycli/`) to the repo root with a leading `/`, so they no longer match at any depth — aligning with `CONTRIBUTING.md`'s stated root-only intent (#231, follow-up to #259)
  • Normalised the `pnp-laspinas` Agency phone to `(02) 8808-7395`, matching the area-code format every other Office/Agency record uses (#243). The number itself is unchanged, so its existing `verifiedOn` citation still holds
  • `categories.json` is now the single source of truth for Category visibility (#284, #287, ADR-0006). Previously three places disagreed: `navigation.json`'s per-item `hidden` (8 of 10 categories hidden), `categories.json`'s `hidden` (2 of 10), and a hardcoded `LIVE_CATEGORY_IDS` set in `configHelper.ts` (all 10 treated as live, ignoring the nav hides — the gap search indexed against). `navigation.json`'s 8 hides are ported into `categories.json` first so the migration is lossless, then `LIVE_CATEGORY_IDS` is deleted and `getServicesConfig()`, `getNavigationConfig()`'s Services submenu, `getCategoryBySlug`, and `getServicesByCategory` all join against `categories.json`'s `hidden` instead. A hidden Category now cascades to everything under it — its page, its Services in search, and their detail pages all become unreachable together, not merely unlisted from the nav — so flipping one Category's `hidden` flag is a single, consistent edit instead of three. Search goes from indexing 41 of 50 Services (the old hardcoded gate) to 14 of 50, matching the 2 currently-launched categories (Certificates, Business); rendered nav/search/category-page output is otherwise unchanged
  • Fixed `death-certificate`'s "Related Services" card linking to `cswdo-services`, a Service whose Category (`social-services`) is hidden — `getServiceBySlug('cswdo-services')` correctly returns undefined for it since #287's cascade, so the link 404'd, which was itself #287's own AC#6 ("no orphaned links to a hidden Category's page or one of its Services' detail pages") going unmet. Added `isLinkedPageVisible` to `configHelper.ts`, which resolves a raw `/service-details/<slug>` or `/services/<slug>` editorial link through the same canonical, hidden-aware accessors every page uses; `serviceDetailView` (`pageViews.ts`) now filters `relatedServices` through it before rendering, so a link auto-hides when its target's Category is hidden and auto-reappears if the flag is later flipped back, with no data edit needed. A repo-wide audit of every `relatedServices`/nav/static-link surface found this was the only orphan — the Services nav submenu, home page, `/services` index, and `/sitemap` hardcoded category links were already gated by `getNavigationConfig()` or their own component-local `hidden` flags
  • Fixed the Agency detail page's SEO title/description title-casing the URL slug instead of using the Agency's real name — `/agencies/pnp-laspinas` rendered "Pnp Laspinas | National Agency" (#295, follow-up to #272), even though the page's own `<h1>` already correctly rendered `agency.name`. `seo.global.ts`'s generic per-route-param interpolation ran every param through `slugToTitleCase`, which can't recover a real name from an id. Added `resolveSlugDisplayName`, which overrides the `{{slug}}` template var with the record's real name for `agencies-slug` and `offices-slug` routes, resolved through the existing `getAgencyById`/`getOfficeBySlug` `configHelper` accessors — never a direct JSON import — so the title can't drift from the catalog. `agencies-slug` now reads "Las Piñas City Police Station | National Agency"; `offices-slug` got the same fix since it carried the identical defect, just harder to notice on slugs like `civil-registry` that happen to title-case plausibly (`cdrrmo` did not: it title-cased to "Cdrrmo" instead of "City Disaster Risk Reduction & Management Office")

v1.2.0

2026-05-10
Compare on GitHub
Added
  • Launched "Business, Trade & Investment" category with comprehensive guides for New and Renewal Business Permits, featuring online application support and official Citizen's Charter attribution
  • Added "Safety Seal Certificate" service to the Business category with full requirements and procedures
  • Added "Issuance of Special Permit" service to the Business category with full Citizen's Charter details
  • Added "Occupational Mayor's Permit (Regular)" service with full Citizen's Charter details
  • Added "Occupational Mayor's Permit (First Time Job Seeker)" service highlighting assistance under R.A. 11261
  • Added "Certificates on Status of Business" service for verification of registered entities via the BPLO
  • Added "Certified True Copy" of Business License and Mayor's Permit service
  • Nuxt Schema Org integration to enhance site name display in search results
  • Page-specific Open Graph (OG) image configuration and JSON-driven description management
Changed
  • Revamped the Changelog page with a modern vertical timeline, improved visual hierarchy, and intuitive grouping of technical updates
  • Refined City department branding by updating "City Civil Registrar" to "City Civil Registry" across all components
  • Updated official contact details, physical addresses, and social media links for the City Civil Registry and City Health Office
  • Enhanced OG Image implementation with a JSON-driven configuration for easier management of page-specific descriptions
Fixed
  • Resolved broken internal navigation by synchronizing service slugs and fixing department-level links (e.g., MSWDO to CSWDO)
  • Fixed hydration mismatch errors in service detail layouts and deterministic state management
  • Corrected changelog rendering logic to prevent empty sections or the "Unreleased" header from displaying when no updates are present
  • Improved search result UI by adjusting info badge icon alignment and increasing size to 12px
Technical Details
Infrastructure
  • AddedProject governance and environment files including `CODEOWNERS` and `.nvmrc` (Node 24)
  • UpdatedCore framework and development dependencies including `nuxt` 4.4.4 and `@vue/test-utils` 4.0.3
  • UpdatedSecurity architecture via `nuxt-security` module, including hardened CSP policies and Cloudflare-specific header optimizations
  • RemovedOutdated GitHub Actions deployment workflow (`cd.yml`)
Internal
  • RefactoredStandardized service routing by migrating `municipal-*` slugs to `city-*` to align with the city's official status
  • RefactoredOptimized internal link routing logic in `categoriesContent.ts` and `serviceDetailsContent.ts`
Technical
  • RemovedRedundant security header definitions from `nuxt.config.ts` to eliminate conflicts with the new security module
  • CleanedRemoved unused issue link logic from prerendering configuration to improve build stability

v1.1.0

2026-04-06
Compare on GitHub
Added
  • Nuxt OG Image v6 has been added to generate social media preview images
  • Feature: Dynamic Changelog page with a premium alternating timeline, including footer links and dynamic parsing logic
  • App version display in the site footer for improved maintenance and support tracking
  • Friday opening information added to relevant LGU services
Changed
  • Improved SEO title generation for slug-based routes (News, Services, Details) and modularized SEO configuration files
  • Updated app version display formatting in site footer for better clarity
  • Updated hardcoded year and income data in city statistics
  • Updated office hours to remove lunch breaks and clarify continuous operation
  • Cleaned up sitemap to exclude hidden and draft pages from public search indexing
  • Barangay Chairmen have been updated to the latest as of Q1 2026
Fixed
  • Hydration mismatch issues in layout and statistics components by synchronizing non-deterministic states and structural placeholders
Technical Details
Infrastructure
  • AddedGitHub Actions deployment workflow (`cd.yml`) with support for tag-based releases
  • Removed`npm` package manager in favor of `pnpm` (updated `pnpm-lock.yaml`)
  • UpdatedCore dependencies and development tools (`nuxt` 4.4, `vue` 3.5, `tailwindcss` 4.2, `vitest` 4.1, `eslint` 10.2, etc.)
  • UpdatedMaintenance workflows and CI/CD pipelines (`ci.yml`, `codeql.yml`, `dependabot.yml`, etc.)
Technical
  • AddedProject maintenance strategy documentation (`CHANGELOG_STRATEGY.md`)
  • AddedCentralized `regexConstants.ts` for static regular expressions
  • UpdatedContribution guidelines and development standards (`CONTRIBUTING.md`) with instructions for finding tasks using the GitHub Project board
  • RefactoredModular search and changelog parsing logic with shared regex utilities
  • FixedUI rendering issues, TypeScript errors, and deployment script environment loading

v1.0.0

2026-03-06
Compare on GitHub
Added
  • Home page with hero section, quick stats, featured services, and emergency hotlines overview
  • Services page with fuzzy search, autocomplete, and category filters; includes `/services/certificates` sub-page
  • Service detail pages for individual LGU service entries
  • Government directory page with city officials and department listings
  • Statistics page with interactive Chart.js data visualizations
  • FAQ page with accordion-style question and answer layout
  • About page with mission, vision, and governance information
  • Contact page with form and LGU contact details
  • Accessibility statement page (WCAG 2.1 compliant)
  • Privacy policy and terms of use pages
  • Join Us page for volunteer and community involvement
  • Sitemap page for full site navigation overview
Deprecated
  • News listing and detail pages (`/news`) — built but not yet linked in navigation
  • History page (`/history`) — built but not yet linked in navigation
  • Tourism page (`/tourism`) — built but hidden from navigation pending content review
  • Legislative framework page (`/legislative`) — built but hidden from navigation pending content review
  • Budget transparency page (`/budget`) — built but hidden from navigation pending content review
  • Service category sub-pages (`/services/business`, `/services/health`, `/services/tax-payments`, and others) — built but hidden from navigation pending content review
Technical Details
Infrastructure
  • Added`useConfig()` composable as the single source of truth for all site configuration
  • Added`useLanguage()` composable for English/Filipino multi-language support
  • Added`useSearch()` composable for Fuse.js-powered fuzzy search
  • Added`useClickOutside()` composable for interactive UI elements
  • AddedJSON-driven content architecture via 17 config files in `app/config/`
  • Added`UiBreadcrumbs` and `LanguageSelector` base components
  • AddedTailwind CSS v4 with custom CSS variable tokens
  • AddedResponsive mobile-first layout with WCAG 2.1 focus states
  • AddedInteractive maps via Leaflet and `@vue-leaflet/vue-leaflet`
  • AddedBootstrap Icons (CDN) and Lucide Vue Next
  • AddedStrict TypeScript configuration across the codebase
  • AddedESLint rules via `@antfu/eslint-config` and Husky hooks
  • AddedVitest test suite with `@vue/test-utils` and `happy-dom`
  • AddedGitHub Actions CI pipeline for quality gates
  • AddedDependabot configuration for dependency health
  • AddedPM2 process management via `ecosystem.config.cjs`
Technical
  • AddedOpen source governance: `README`, `CONTRIBUTING`, `LICENSE`, `CODE_OF_CONDUCT`