Website, Public Information Bulletin and Rescuer Zone for CSRG S.A.
For Centralna Stacja Ratownictwa Górniczego S.A. in Bytom we built a set of three connected WordPress services: an **informational website**, a **Public Information Bulletin (BIP)** and a restricted-access **Rescuer Zone** for employees. The whole meets the requirements placed on a public institution: a legally compliant BIP, WCAG 2.1 AA digital accessibility confirmed by audit, PL/EN bilingualism and elevated security standards. The project was accepted without reservations on 10 July 2026, with a 36-month warranty.
Client and institutional context
Centralna Stacja Ratownictwa Górniczego S.A., based at ul. Chorzowska 25 in Bytom, is a company whose sole shareholder is the State Treasury. It has been recognised as a company of special economic and defence significance. Its origins date back to a decision of 1906, and the station was commissioned in 1908, giving it more than a century of uninterrupted operation.
CSRG’s activity is mine rescue. The company operates as a public institution under the provisions of the Geological and Mining Law. This status imposes specific obligations on the website, including maintaining a Public Information Bulletin, ensuring digital accessibility and GDPR compliance.
The institution communicates in an official, matter-of-fact tone. The site had to inform clearly and credibly, without marketing rhetoric, while organising three distinct areas: public information on the website, legally required content in the BIP, and internal materials available only to authorised employees in the Rescuer Zone.
The challenge
A public institution’s website is not a single page but several systems with different legal requirements and different audiences. One deployment had to reconcile a representative informational site, a Public Information Bulletin governed by separate rules, and a closed Rescuer Zone. Each of these areas follows its own logic of access, layout and publishing.
The second pillar of the challenge was digital accessibility at the WCAG 2.1 AA level, not merely declared but confirmed by a test report. This required a high-contrast mode, smooth font-size adjustment, correct semantics and full responsiveness on mobile, desktop and touch devices. Accessibility had to cover both the website and the BIP.
The third area was security appropriate to the entity’s standing. The website of a company of special economic and defence significance required protection of the admin panel, resistance to known intrusion methods and database query manipulation (SQL injection), protection of forms and contact details against bots, downloadable backups, and two-factor login. All of it was subject to a separate security audit.
Specific requirements
- Three connected services: website (csrg.bytom.pl), BIP (bip.csrg.bytom.pl) and a restricted-access Rescuer Zone (ratownik.csrg.bytom.pl)
- BIP compliant with requirements: entity, subject and editorial menus, public page versioning, metadata tagging, print option
- WCAG 2.1 AA accessibility with a test report, high-contrast mode, font-size adjustment
- Two language versions, Polish and English, on the website
- Full responsiveness: mobile, desktop and touch screens
- Occasional layouts: festive version, Miner’s Day version and mourning version
- Simple and advanced search, separately for the website and the BIP
- Security: SSL certificate, admin panel protection, lockout after failed login attempts, resistance to SQL injection
- Protection of forms and of email addresses and phone numbers against bots
- Two-factor login (2FA), change history and login history
- GDPR compliance: information clauses, GDPR/DPO section, cookie notice
- Backups downloadable by the ordering party
- Handover of source code, as-built documentation and a 36-month warranty
2-month implementation process
The scope covered three services, two dedicated themes, WCAG accessibility, legal compliance and elevated security, so we split the work into five ordered phases. The time breakdown below is approximate and adds up to the two months of delivery.
Requirements and legal compliance analysis
1 weekDefining the scope for a public institution: BIP structure (entity, subject and editorial menus, versioning, metadata, printing), the extent of WCAG 2.1 AA accessibility, security and GDPR requirements, and bilingual rules. Mapping the three services and their dependencies.
UX/UI design and accessibility architecture
2 weeksDesign of two separate themes: a matter-of-fact, official informational website and a BIP layout compliant with its requirements. High-contrast mode, font scaling and responsiveness for mobile, desktop and touch devices. Concept for the Rescuer Zone.
Development: WordPress, two themes, CPT and ACF
3 weeksBuilding a dedicated website theme and a separate BIP theme on WordPress. Custom Post Types, ACF and Gutenberg blocks for editorial content. News, multimedia gallery, contact section with form and interactive route map, training section, simple and advanced search. Custom plugins, including the occasional-layouts plugin. A CMS with a Polish-language WYSIWYG editor, change and login history, and 2FA.
Security, WCAG, GDPR and audits
1 weekImplementation of an SSL certificate, admin panel protection (lockout after failed login attempts, resistance to SQL injection and known intrusion methods), protection of forms and contact details against bots, downloadable backups. An accessibility audit concluded with a WCAG 2.1 AA report and a security audit. GDPR clauses, GDPR/DPO section, cookie notice, SEO, XML sitemap, friendly URLs and content archiving.
Deployment, photo session, training and handover
1 weekServer installation and production launch, hosting for the warranty period, FTP accounts for the editorial team. A photo session covering employees, equipment and buildings. Editorial training, handover of the site copy, source code and as-built documentation. Acceptance without reservations.
Technical solution
Stack: WordPress as an open-source CMS, two dedicated themes (a separate one for the website and for the BIP), Custom Post Types, ACF, Gutenberg blocks, custom plugins, PHP and JavaScript. Separating the themes was a deliberate decision, because the informational site and the Public Information Bulletin have different requirements for layout, publishing and compliance.
We built the BIP around its required elements: entity, subject and editorial menus, publicly visible page versioning and metadata tagging, plus a print option and a separate search. This lets the editorial team run the Bulletin by the rules, while the audience has access to the full change history of every page.
We tailored the security layer to the entity’s standing. The admin panel is protected by lockout after failed login attempts and resistance to SQL injection and known intrusion methods, while access is secured by two-factor login (2FA). Editors work on accounts with change history and login history, and the ordering party receives backups they can download themselves. The correctness of these safeguards was confirmed by a security audit.
Why two separate themes for the website and the BIP?
The informational site and the Public Information Bulletin follow different rules. The BIP requires entity, subject and editorial menus, public page versioning and metadata that the website does not need. Separating the themes lets both areas evolve and be maintained independently, without the risk that a change in one breaks the compliance of the other.
Why WordPress in an open-source model?
An open CMS means no licence costs for a public institution and no dependence on a single vendor. The source code and as-built documentation were handed over to the ordering party, so the company retains full control of the site. WordPress’s mature ecosystem also eases editorial training and long-term maintenance.
Why 2FA and extended panel protection?
The website of a company of special economic and defence significance calls for elevated standards. We secured the panel with lockout after failed login attempts and resistance to SQL injection and known intrusion methods, and supplemented login with a second authentication factor and login history. The scope of protection was verified by a separate security audit.
Why a dedicated occasional-layouts plugin?
The institution communicates in different contexts, from holidays and Miner’s Day to periods of mourning. A dedicated plugin lets the editorial team switch the site’s visual styling without touching the code, while preserving accessibility and layout consistency.
Key features
The deployment covered three services and a shared CMS: from the public informational site, through the Public Information Bulletin, to the closed Rescuer Zone and the editorial back office.
Informational website
Home page, news section, multimedia gallery with photos and films, contact section with a form and an interactive route map, and a training section with a form. Polish and English versions, full responsiveness on mobile, desktop and touch screens.
Public Information Bulletin (BIP)
A separate theme with entity, subject and editorial menus, publicly visible page versioning and metadata tagging. The option to print BIP pages, plus simple and advanced search.
Rescuer Zone (restricted access)
A dedicated restricted-access section intended for employees. Internal materials kept outside the public site, available only to authorised users.
WCAG 2.1 AA digital accessibility
Compliance confirmed by a test report. High-contrast mode and smooth font-size adjustment, correct semantics and responsiveness covering both the website and the BIP.
PL/EN bilingualism
The website in Polish and English versions, keeping a consistent content structure and navigation in both languages.
Occasional layouts
A dedicated plugin lets the editorial team enable festive styling, a Miner’s Day version and a mourning version, without touching the code and while preserving accessibility.
CMS with a Polish WYSIWYG editor
Content and layout management: sections, subpages, menu order, hiding sections. Adding files (pdf, doc, docx, xls, xlsx, ppt, zip) and multimedia (mp4, mov, mp3) and YouTube materials. Page preview at the editing stage and guides for the editorial team.
Panel security and 2FA
Admin panel protection through lockout after failed login attempts and resistance to SQL injection and known intrusion methods. Two-factor login (2FA), change history, login history and user management.
Bot protection and backups
Protection of forms and of email addresses and phone numbers against bots. Site backups that the ordering party can download themselves.
Simple and advanced search
Content search available separately in the website and in the Public Information Bulletin, in a simple and an advanced variant.
GDPR and legal compliance
Information clauses, a GDPR/DPO section and a cookie notice. Copyright compliance, friendly URLs and editable metadata.
SEO, performance and archiving
SEO optimisation, an XML sitemap, load-time optimisation and correct display across browsers. A content-archiving function for materials withdrawn from current publication.
Tech stack
We based the solution on the open-source WordPress CMS with two dedicated themes and a set of custom extensions matched to the needs of a public institution.
Results
All three services, the website at csrg.bytom.pl, the BIP at bip.csrg.bytom.pl and the Rescuer Zone at ratownik.csrg.bytom.pl, went into production and were handed over to the company. Acceptance took place on 10 July 2026 without reservations.
From the institution’s perspective, four outcomes matter most: the Public Information Bulletin’s compliance with its requirements, WCAG 2.1 AA digital accessibility confirmed by an audit report, elevated security verified by a separate audit, and two-factor login to the panel. The company received the source code and as-built documentation, which ensures its independence from any single vendor.
The deployment also prepared the ground for the editorial team’s ongoing work: FTP accounts, training, guides and a photo session covering employees, equipment and buildings. Hosting was provided for the warranty period, and the whole was covered by a 36-month warranty.
What’s next
Throughout the warranty period the services remain on the hosting provided as part of the deployment, and the editorial team runs content itself in the CMS with its WYSIWYG editor, using the guides and FTP accounts. Change history and login history make it easier to oversee publications.
Handing over the source code and as-built documentation means the company is not tied to a single vendor and can extend the site in the future, for example with further modules in the Rescuer Zone or additional content types. The delivered foundation, WordPress with two themes and custom plugins, is prepared for that.