airajena opened a new pull request, #13:
URL: https://github.com/apache/fineract-chat-archive/pull/13
## Summary
This PR switches archive generation from Markdown output to direct HTML
output, so GitHub Pages can serve the site as static files without a Jekyll
build step.
It also improves thread/reaction rendering and keeps styling external via a
static stylesheet path.
## Changes
- Replaced Markdown rendering with HTML rendering:
- Added `HtmlRenderer`
- Removed `MarkdownRenderer`
- Updated archive generation flow in `ChatArchiveApp` to:
- write daily pages as `index.html` under date folders
- write channel index pages as `index.html`
- write global index as `docs/index.html`
- keep clean extensionless URLs in published Pages
- Kept metadata generation:
- `robots.txt` always generated
- `sitemap.xml` generated when `SITE_BASE_URL` is set
- Improved message rendering:
- clearer thread reply grouping
- inline formatting support (`*bold*`, `_italic_`, `~strike~`)
- bullet/numbered list support in message bodies
- reaction badge rendering
- Fixed emoji handling in formatter to avoid broken output.
- Updated/added tests:
- `HtmlRendererTest`
- `IndexRendererTest`
- updated formatter/site metadata tests
- removed markdown-specific tests
- Updated `Readme.md` to document HTML output paths and static stylesheet
usage.
## Testing
- Ran: `./gradlew clean test --console=plain`
- Result: pass
## Notes
- This PR expects stylesheet to be provided as a static file in the
publishing repo (`docs/assets/chat-archive.css`) rather than generated by Java.
## Current HTML Index Content
<img width="1205" height="898" alt="Screenshot 2026-02-13 221910"
src="https://github.com/user-attachments/assets/41ee5826-e0cf-40a4-875f-acf116e87c0c";
/>
<img width="1186" height="899" alt="Screenshot 2026-02-13 221934"
src="https://github.com/user-attachments/assets/bd8febec-0cc0-4e72-a335-99fef6125f84";
/>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
