Website and Public Information Bulletin on the gov.pl platform for WUOZ Wrocław
For the Regional Office for the Protection of Monuments in Wrocław we moved the website and the Public Information Bulletin (BIP) from a system running since 2003 to the government platform GovPress (gov.pl). In 40 working days we inventoried the old BIP, configured the site, migrated 807 pages and 2,465 files with publication metadata, rewrote key content in plain language, brought the site to WCAG 2.2 AA compliance confirmed by a report, trained the editors and handed over a complete set of documentation. Final acceptance was signed without reservations and the office now runs the site on its own.
Client and context
The Regional Office for the Protection of Monuments in Wrocław (Wojewódzki Urząd Ochrony Zabytków) serves the Lower Silesian Regional Conservator of Monuments, the authority responsible for heritage protection in the Lower Silesia region. The office keeps the register of monuments, issues permits and certificates, grants funding for conservation works, runs proceedings and recruitments, and all of this is subject to the disclosure duties of the Polish act on access to public information.
The previous Public Information Bulletin had been running since 29 July 2003 in a separate system and over more than twenty years had grown to 846 pages and 2,605 files: ordinances, procurement and recruitment notices, inspection reports, grant lists, petitions and service cards. The content was of uneven technical quality, created over several generations of editors, with pastes from office documents, rigid tables and colours that no longer met accessibility requirements.
The office decided to move its website and bulletin to GovPress, the platform of the gov.pl portal run by the Ministry of Digital Affairs, which already hosts other regional monument protection offices. The contract was awarded through a request for quotations outside the Public Procurement Law, on the basis of a six-stage description of the subject of the contract. Contract no. 47/2026 was signed on 28 July 2026 with a deadline of 40 working days and 36 months of warranty and technical support.
Challenge
A migration to GovPress differs from a regular website rebuild: the contractor writes no code, chooses no theme and has no influence on the template, stylesheet or portal header. It works in the editorial panel and through the platform API, on nine content templates imposed by the description of the subject of the contract, and the site itself is published by the gov.pl editorial team. The whole quality of the delivery therefore lies in content, structure, metadata and the reliability of the transfer, not in a technical layer that cannot be touched.
The second challenge was scale and legal responsibility. A bulletin consists of documents whose wording must not change: ordinances, notices, reports, petitions. Every page had to keep its content, attachments and publication metadata, that is the person who produced the information and the dates of creation and publication. Moving 846 pages and thousands of files by eye was out of the question; what was needed was a balance that closes in both directions and can be presented to the client as evidence.
The third challenge was time and dependencies: 40 working days from signing, including the office acceptances at each stage, publication of the site by the gov.pl editorial team, activation of editor accounts by the Central IT Centre and on-site training in Wrocław. On top of that, the platform can report success without saving a change and serves pages from cache longer than it declares, so every measurement had to be taken on the public site, not in the panel.
Requirements from the description of the subject of the contract
- Six stages: inventory of the existing BIP, site configuration, migration of content and attachments with metadata, plain language and WCAG 2.2 AA, editor training, tests and final acceptance
- Nine GovPress content templates: article, document with attachments, public procurement, universal list, service card, biography, accordion list, site map and procurement search
- Mandatory bulletin elements: content map, public procurement search and publication metadata with change history
- WCAG 2.2 level AA compliance confirmed by an accessibility test report
- Plain language: FOG-PL index between 8 and 12 for key service content
- On-site training of at least three editors, an editor manual and training materials
- Reports for final acceptance: migration completeness, WCAG 2.2 AA compliance, functional tests
- Data processing agreement, record of processing activities and deletion of data copies after acceptance
- Deadline of 40 working days, warranty and technical support for 36 months
Delivery process in 40 working days
We divided the scope according to the six stages of the description of the subject of the contract. Each stage ended with a document handed to the office for acceptance, and work on consecutive stages partly overlapped. The durations below are indicative.
Stage I: inventory of the existing bulletin
2 weeksFull download of the old BIP: 846 pages and 2,605 files with dates, authors and section structure. Classification of pages into the nine GovPress templates, detection of duplicates, empty pages and pages without content, design of the new site structure and a list of target addresses. The office accepted the stage documentation on 24 August and the list of 807 addresses a day later; from that moment the addresses were frozen.
Stage II: site configuration in GovPress
2 weeksBuilding the page tree, tabs and side menus, universal and accordion lists, service cards, the contact page, bulletin editorial page, BIP usage instructions and the accessibility statement. Configuration of the content map and the public procurement search, file and logo repositories. Agreeing with the office the publication metadata pattern and the rules for marking pages as belonging to the bulletin.
Stage III: migration of content, attachments and metadata
3 weeksTransfer of content through the platform API with our own scripts, saving each page, reading it back and publishing. Files were placed in the Materials section according to the gov.pl layout, keeping file names and document titles. Content cut-off date of 28 August, followed by one differential pass covering new and changed pages and additional attachments. Publication of the site by the gov.pl editorial team on 14 September.
Stage IV: plain language and WCAG 2.2 AA accessibility
2 weeks, in parallelDefining the service layer of the site (69 pages a citizen reads to get something done), measuring the FOG-PL index and rewriting 13 pages in plain language. Accessibility testing on the public site in three browsers, fixing the defects found in content and re-measuring the whole site. Deviations described and justified, findings about the platform layer prepared for reporting to the gov.pl editorial team.
Stage V: editor training
1 day, 21 SeptemberOn-site training in Wrocław: three hours, six modules from logging in through the National Node, through templates, file repositories and marking BIP content with metadata, to accessibility, plain language and the publication workflow from editor to publisher. Exercises in the panel on prepared materials, a knowledge test and a training protocol. Editor manual, training materials and a pre-publication checklist handed over electronically.
Stage VI: tests, reports and final acceptance
1 weekFunctional tests on the public site (84 tests in eight groups, all passed), a WCAG 2.2 AA compliance report and a migration completeness report with a balance of pages, content, attachments, photos and metadata. Notification of readiness for final acceptance within the contractual deadline. Stage protocols and the final protocol without reservations signed by the office with qualified signatures on 7 October 2026.
Solution
The core of the project was our own set of migration tools that talk to the GovPress API: they create pages in the right templates, save content and metadata, upload files to repositories, publish and immediately read the result back from the server. Because the platform can report success without saving a change, no step was considered done without a control read and a check on the live domain.
We counted migration completeness as a balance that closes in both directions: every source item is in the site or has a recorded reason for its absence, and every item in the site has a source or an explained origin. Content was compared by word coverage rather than text length, and an attachment was considered migrated only once it could be downloaded from the public site. The decision register was kept during the work, not afterwards, so the final report could point to evidence for every number.
We treated accessibility and plain language as measurements, not declarations. The WCAG 2.2 AA audit covered a stratified sample of 103 pages in Chromium and 24 pages each in Firefox and Edge, 69 axe-core rules, manual keyboard, zoom and text-spacing tests, and full-site scans for contrast and target size. We fixed the defects found in content and re-measured the whole site. The FOG-PL index was measured on published text, not on drafts.
Why was the address list accepted before publication and frozen?
Page addresses in GovPress are flat and unique across the whole site, and a collision only shows up at publication. We handed the list of 807 addresses to the office for acceptance before the migration, and after the acceptance on 25 August not a single address changed. Thanks to that, the completeness report could compare the plan with the live site one to one, and the office received stable addresses for redirects and correspondence.
Why files in the Materials section rather than in the text?
The old bulletin added sentences such as "a scan of the document will open after clicking" next to links. On gov.pl attachments have their place in the Materials section below the content, with the document title and file size. We moved them there, keeping names and titles, and removed the click announcements as misleading. The completeness report explains this difference separately for the 302 pages where it was the only change.
Why plain language only for the service layer?
The description of the subject of the contract requires a FOG-PL index of 8 to 12 for key content, not for the whole site. Ordinances, recruitment notices, reports and petitions must not be rewritten, because their wording is fixed by law or by the words of the applicant. We therefore defined the scope as the 69 pages a citizen reads to get something done, measured the index before and after, and rewrote 13 pages, for example the page on access to public information from 20.1 to 10.3.
Why measure on the public site and not in the panel?
In this platform saving in the system and showing to the reader are two different things: a change may be saved while the page is still served from cache. That is why functional tests, the accessibility audit and the migration balance were run on the same resource citizens use, with a fresh copy forced before each measurement. The result concerns what people really see.
What the office received
The site runs at gov.pl/web/wuoz-wroclaw as a single GovPress site combining the information part with the Public Information Bulletin. On the day of testing it had 856 published pages, and the office adds more on its own.
Information website on gov.pl
Five tabs with side menus, a home page with news, information about the office and its management, service cards for citizens, contact, accessibility statement and bulletin editorial page. The layout and components of the gov.pl portal, so citizens navigate the site the same way as other government websites.
Public Information Bulletin with mandatory elements
The "Belongs to BIP" flag on 855 pages, a bulletin content map with a BIP page filter, a public procurement search with 13 fields and publication metadata with change history on every content page. The entity card in the central BIP points to the new address.
Content migrated without changing its wording
807 addresses from the accepted plan, 796 live pages and 11 absent with a recorded reason, 39 pages excluded with documented justification. Word coverage checked for every page, with no page left with an unexplained difference.
Repository of 2,465 attachments and 121 photos
Ordinances, notices, reports and lists as attachments in the Materials section, with file names and titles preserved. All 2,465 referenced files download from the public site, 1.2 GB in total. Illustrations in the photo repository in the crops required by the platform.
Publication metadata on 855 pages
The person who produced the information and the dates of creation and publication according to a pattern agreed with the office, transferred from the dictionary of the old bulletin. Change history kept by the platform from the first publication.
Plain language in the service layer
69 service pages measured with the FOG-PL index, 13 rewritten into the 8-12 range, including information on petitions, register entries, access to public information and certificates. Official documents left in their original wording.
WCAG 2.2 AA accessibility with a report
Testing in three browsers with 69 axe-core rules, manual tests and full-site scans. 39 pages fixed: contrast, content reflow on narrow screens, list structure, target size, attachment labels. After the fixes zero violations in editorial content, with platform-layer findings documented for the gov.pl editorial team.
Functional tests 84 of 84
Nine templates, navigation, search engines, attachment downloads, metadata, content map and the view at 375 pixels. Tests written in code as triples of name, expected and actual value, repeatable at any time.
Editor manual, materials and checklist
An electronic editor manual, training materials with exercises, a training scenario and a pre-publication checklist, so that every new page of the office follows the same rules as the migrated content.
Training, protocols and data protection
On-site training with a protocol, protocols for six stages and the final acceptance protocol, a data processing agreement signed by the Conservator, a record of processing activities and a commitment to delete copies of the office data after acceptance.
Tools and method
No site code is written on the GovPress platform, so our stack consists of migration, measurement and documentation tools rather than a framework.
Results
The site gov.pl/web/wuoz-wroclaw was published on 14 September 2026, and the notification of readiness for final acceptance with the full set of reports and protocols reached the office on 21 September, within the contractual deadline. The office signed the stage protocols and the final acceptance protocol without reservations on 7 October 2026.
From the client perspective three things matter: the bulletin lost no content and no file, which the two-way balance confirms; the site meets WCAG 2.2 AA in the area the office is responsible for, which the before-and-after measurement report confirms; and the editorial team works independently, as shown by pages the office published after acceptance, including the grants section rebuilt by year at its request.
The whole delivery is covered by warranty and technical support for 36 months from acceptance. The office received a site on a platform maintained by the state, with no hosting or licence costs, and documentation that allows it to run the bulletin without the contractor.
What comes next
The office runs the site on its own in the GovPress panel, using the editor manual and the pre-publication checklist, and has our technical support for 36 months with response times defined in the contract. Training of further editors takes place on dates agreed by the parties.
We use the experience from this delivery, from the migration balance to accessibility measurement on a platform with no access to code, in further projects for institutions moving their Public Information Bulletins to gov.pl. We describe the requirements for public office websites in our article on office websites and BIP, and how to prepare a request for quotations in the article on the description of the subject of the contract for an institution website.