Add IBT Systems and ACTE Technology case studies - #557
Merged
vvlladd28 merged 6 commits intoJul 20, 2026
Conversation
- New data-driven pages at /case-studies/ibt-systems/ and /case-studies/acte-technology/, registered in caseStudyOrder. - Optional power.heading override on PowerSection for case studies whose 'how it works' section title deviates from the default template. - IBT Systems assets: hero photo, white logo, and four power-block images. - ACTE Technology hero/logo/power images are neutral placeholders until the customer provides real materials (the approved design ships placeholders).
- Swap the 'Comply with regulations' block image for the marketing-approved compliance visual (960px webp, 20 KB vs the previous 150 KB photo). - Remove the ACTE Technology page, data file, catalog entry, and its seven placeholder images until the customer provides real materials (the page can be restored from this branch's history).
The customer's imagery arrived (Nextcloud share): hero banner, logo, and one image per power block, replacing the earlier placeholders. Logo converted to transparent PNG (85x79 intrinsic); all images compressed webp under 27 KB.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds two new case-study entries (IBT Systems and ACTE Technology) to the ThingsBoard documentation site and introduces a small framework extension so the “Power/How it works” section can use a custom heading per case study.
Changes:
- Added new case-study data pages for
/case-studies/ibt-systems/and/case-studies/acte-technology/. - Added
power.headingtoCaseStudyDataand wired it through the case-study page intoPowerSection. - Updated case-study catalog ordering to surface the new entries first.
Reviewed changes
Copilot reviewed 6 out of 19 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| src/pages/case-studies/[slug].astro | Passes optional power.heading through to PowerSection for per-page heading overrides. |
| src/data/case-studies/types.ts | Extends CaseStudyData with optional power.heading field (typed + documented). |
| src/data/case-studies/index.ts | Adds the two new slugs to caseStudyOrder so they appear in the catalog. |
| src/data/case-studies/ibt-systems.ts | Introduces the IBT Systems case-study content and assets configuration. |
| src/data/case-studies/acte-technology.ts | Introduces the ACTE Technology case-study content and assets configuration. |
| src/components/CaseStudy/PowerSection.astro | Adds optional heading prop and renders it in the section <h2>. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The partner logo is dark-on-white and the detail-page hero renders logos unfiltered, so it vanished against the light banner photo. Bake a 45% dark overlay into the hero image and use a white transparent logo variant, matching the dimmed-photo + white-logo convention of the other case studies (catalog cards and the contact CTA white-filter logos anyway).
- PowerSection: nullish coalescing for the heading fallback. - Grammar fixes across both case studies: 'well-documented', 'allowed us to easily adapt', 'allows implementing … without the need for', 'Moreover, the reports show …', simple-present power heading, and help headings gain explicit subjects (researchers / datacenter operators).
Contributor
Author
|
Addressed all 8 Copilot comments in acd5574: switched the heading fallback to |
rusikv
marked this pull request as ready for review
July 17, 2026 13:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two new customer case-study pages built from the approved designs:
Both pages reuse the shared widget collages (
sensors-widget,entities-table,tables,bar-chart,line-chart,alarms-table,notification-widget,hierarchy-widget,roles-table) matching the design mockups. All new images are compressed (5–66 KB each).Framework change
PowerSectionnow accepts an optionalheadingoverride (power.headinginCaseStudyData) because both designs use custom section titles instead of the default "How ThingsBoard powers {companyName}?" template. Existing pages are unaffected.Copy edits vs. the design
Objective fixes only, customer voice kept (incl. British spellings): brand casing Thingboard/Thingsboard → ThingsBoard; "the variety supported protocols" → "the variety of supported protocols"; "…email and SMS was appreciated" → "were"; "rulechains blocks" → "rule chain blocks"; "Bacnet, SNMp" → "BACnet, SNMP"; "a metric deviate" → "deviates"; "How ACTE Uses ThingsBoard to powers Chaktomuk?" → "How ACTE uses ThingsBoard to power Chaktomuk?"; ACTE intro run-on split into two sentences; RBAC run-on fixed; "prevents multiple of alarms being notified" → "prevents alarm floods"; stat labels "Year of experience"/"Numbers of project" → plural forms.
Notes for review
Verification
astro check(0 errors), ESLint and Prettier clean on the new files; both pages and the catalog rendered via dev server and visually compared against the designs, and all image URLs verified 200 (fullpnpm buildnot run per repo build policy).