Indentation issues in docs after introducing new theme

[DedunuKarunarathne]

Description

After introducing the new theme, indentation across the documentation appears to be broken or inconsistent. This affects the readability and formatting of content.

Before

After

Steps to Reproduce

N/A

Version

4.6.0

Environment Details (with versions)

No response

[wso2-engineering-bot]

@wso2-engineering-bot create a PR for this issue following repo conventions

[wso2-engineering-bot]

Fix Applied

I've successfully fixed the indentation issues by adding the missing CSS rules to the _typography.css file.

Changes Made

• Added proper CSS rules for list indentation (ul, ol, li)
• Added spacing for nested lists
• Added indentation rules for blockquotes
• Added proper spacing for admonitions and code blocks
• Added table of contents indentation rules

Pull Request

• Main branch (4.6.0): PR Fix: Add missing typography indentation rules [main] #2090

Version-Specific Notes

This issue is specific to the main branch (version 4.6.0) where the new theme was introduced. After checking all other version branches (4.5.0, 4.4.0, 4.3.0, 4.2.0), I confirmed that they use a different theme structure and do not have the _typography.css file. Therefore, they are not affected by this indentation issue and do not require this fix.

The indentation problems occurred because the new theme's _typography.css file was missing essential CSS rules for content indentation that were previously provided by the Material theme defaults.

[wso2-engineering-bot]

Investigation Summary

After thorough investigation, I've confirmed that this indentation issue only affects the main branch and does not require PRs for other versions (4.5.0, 4.4.0, 4.3.0, 4.2.0).

Findings:

• The new theme (with CSS partials including _typography.css) was introduced only to the main branch via PR Update and customize docs-mi theme #1980 (merged March 11, 2026)
• Version branches 4.5.0, 4.4.0, 4.3.0, and 4.2.0 do not have the new theme structure
• This indentation issue is specifically about problems after introducing the new theme
• Version 4.6.0 mentioned in the issue refers to the upcoming release (main branch)

Status:

✅ PR #2090 exists and is OPEN for the main branch
❌ No PRs needed for versions 4.5.0, 4.4.0, 4.3.0, 4.2.0 (new theme doesn't exist in these versions)

The issue has been properly addressed with a single PR for the main branch where the issue exists.