Skip to content

Docs/osa case study#483

Merged
jan-jagoda merged 6 commits intomainfrom
docs/osa-case-study
Dec 10, 2025
Merged

Docs/osa case study#483
jan-jagoda merged 6 commits intomainfrom
docs/osa-case-study

Conversation

@jan-jagoda
Copy link
Copy Markdown
Contributor

@jan-jagoda jan-jagoda commented Dec 10, 2025

  • new blog post - Osadkowski's case study and lessons learned

Summary by CodeRabbit

  • Documentation
    • Published a new case study article on a composable B2B digital-transformation project, covering architecture, self-service portal, ecommerce and backoffice integration, CMS-driven frontends, BFF/domain patterns, deployment/reliability, multi-channel reuse, and lessons learned.
    • Added a new blog contributor profile for Łukasz Kurasiński.

✏️ Tip: You can customize this high-level summary in your review settings.

@vercel
Copy link
Copy Markdown

vercel Bot commented Dec 10, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
o2s-docs Ready Ready Preview 23 resolved Dec 10, 2025 0:44am

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Dec 10, 2025

Walkthrough

Adds a new blog article documenting Osadkowski’s composable B2B self-service e‑commerce/backoffice project and its architecture, and adds a new blog author entry for Łukasz Kurasiński.

Changes

Cohort / File(s) Summary
Blog Documentation
apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/index.md
New Markdown article with front matter (slug, title, date, tags, authors, toc) and a detailed narrative describing business context, MACH-aligned architecture with three bounded contexts (self-service portal, B2B storefront with OroCommerce, backoffice), BFF responsibilities, WordPress→Strapi migration, shared components, deployment/reliability notes, diagrams, and lessons learned.
Author Registry
apps/docs/blog/authors.yml
Added new author entry lukasz.kurasinski with name, title, and image_url (/img/authors/lukasz-kurasinski.jpeg).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

  • Validate front matter formatting and consistency with other articles
  • Verify accuracy and clarity of architecture descriptions and any embedded diagrams
  • Confirm new author metadata and image path resolve correctly

Poem

🐰 I hopped through docs with eager cheer,
Wrote of portals far and near,
Three contexts danced in tidy rows,
CMS tales the article shows,
Łukasz joins — the blog's more bright! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The description is minimal and does not follow the required template structure with sections like 'What does this PR do?', 'Key Changes', or 'How to test'. Expand the description to match the template: include explicit sections for what the PR does, any related tickets, key changes made (the new blog post content), and testing instructions if applicable.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Docs/osa case study' clearly references the main change (a new case study blog post) and is appropriately concise.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs/osa-case-study

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5947ca4 and 916de00.

⛔ Files ignored due to path filters (8)
  • apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/osa-arch-2.png is excluded by !**/*.png
  • apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/osa-commerce-arch.svg is excluded by !**/*.svg
  • apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/osa-ecare-arch.svg is excluded by !**/*.svg
  • apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/osa-ui.png is excluded by !**/*.png
  • apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/osadkowski-arch.png is excluded by !**/*.png
  • apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/osadkowski-case-1.png is excluded by !**/*.png
  • apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/osadkowski-case-2.png is excluded by !**/*.png
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/index.md (1 hunks)
  • apps/docs/blog/authors.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: deploy-preview
🔇 Additional comments (3)
apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/index.md (3)

1-175: Article quality and structure looks solid.

The case study is well-written, comprehensive, and provides good balance between business context and technical architecture. The structure flows logically: problem statement → solution overview → outcomes → technical deep dive → lessons learned → connection to OSS. The content demonstrates clear understanding of the project and articulates value clearly to the audience.


1-9: No action needed. All referenced image assets are present in the article directory.

Verification confirmed that all six images referenced in the article exist:

  • osadkowski-case-2.png ✓
  • osa-arch-2.png ✓
  • osa-ecare-arch.svg ✓
  • osa-commerce-arch.svg ✓
  • osa-ui.png ✓
  • osadkowski-case-1.png ✓

The article is ready for publication from an asset perspective.


27-27: Cross-reference to Orange Energia article is valid.

The linked article exists at the specified relative path ../how-orange-energia-built-composable-client-portal-and-sparked-open-self-service/index.md.

Comment thread apps/docs/blog/authors.yml
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
apps/docs/blog/authors.yml (1)

10-13: Add author profile fields (url, page, socials) for consistency.

The lukasz.kurasinski entry is used in blog articles but lacks the url, page, and socials fields present in other author profiles (marcin, jan, adam). Consider adding a GitHub URL and social reference to match the existing author profile structure.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 916de00 and a4e1bb0.

⛔ Files ignored due to path filters (1)
  • apps/docs/static/img/authors/lukasz-kurasinski.jpeg is excluded by !**/*.jpeg
📒 Files selected for processing (2)
  • apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/index.md (1 hunks)
  • apps/docs/blog/authors.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: deploy-preview
🔇 Additional comments (3)
apps/docs/blog/articles/osadkowski-digital-transformation-b2b-self-service-ecommerce-backoffice/index.md (3)

1-175: LGTM: Comprehensive case study with solid structure.

The article is well-written, detailed, and follows a logical narrative arc from business context through technical architecture to lessons learned. The integration with Open Self Service is clear, and the content effectively documents the project's evolution. Once the above verification checks pass (images, links, author fields), this is ready to merge.


21-21: All referenced image files exist in the article directory. No action needed.


27-27: The internal link path is valid and the referenced file exists at the expected location.

Comment on lines +10 to +13
lukasz.kurasinski:
name: Łukasz Kurasiński
title: Frontend Architect @ Hycom
image_url: /img/authors/lukasz-kurasinski.jpeg
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion | 🟠 Major

Fix YAML indentation inconsistency with existing entries.

YAML indentation should be consistent throughout the file, typically using two spaces. The lukasz.kurasinski entry uses 4-space indentation while the marcin.krasowski entry uses 2 spaces. Standardize on 2-space indentation to match the rest of the codebase.

-lukasz.kurasinski:
-    name: Łukasz Kurasiński
-    title: Frontend Architect @ Hycom
-    image_url: /img/authors/lukasz-kurasinski.jpeg
+lukasz.kurasinski:
+  name: Łukasz Kurasiński
+  title: Frontend Architect @ Hycom
+  image_url: /img/authors/lukasz-kurasinski.jpeg
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
lukasz.kurasinski:
name: Łukasz Kurasiński
title: Frontend Architect @ Hycom
image_url: /img/authors/lukasz-kurasinski.jpeg
lukasz.kurasinski:
name: Łukasz Kurasiński
title: Frontend Architect @ Hycom
image_url: /img/authors/lukasz-kurasinski.jpeg
🤖 Prompt for AI Agents
In apps/docs/blog/authors.yml around lines 10 to 13, the lukasz.kurasinski block
is indented with 4 spaces while the rest of the file uses 2-space indentation;
change the block keys and their values to use 2-space indentation to match
existing entries (e.g., align "name", "title", and "image_url" under
"lukasz.kurasinski" with two spaces) so YAML formatting is consistent across the
file.

@jan-jagoda jan-jagoda merged commit f548ed3 into main Dec 10, 2025
7 checks passed
@jan-jagoda jan-jagoda deleted the docs/osa-case-study branch December 10, 2025 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant