Skip to content

writing blog post for statuslist server#127

Merged
Ngha-Boris merged 12 commits intomainfrom
442-write-a-blog-post-for-the-status-list-server
Dec 18, 2025
Merged

writing blog post for statuslist server#127
Ngha-Boris merged 12 commits intomainfrom
442-write-a-blog-post-for-the-status-list-server

Conversation

@ndefokou
Copy link
Copy Markdown
Collaborator

No description provided.

@ndefokou ndefokou self-assigned this Dec 11, 2025
@ndefokou ndefokou requested a review from Ngha-Boris December 12, 2025 11:47
Copy link
Copy Markdown
Collaborator

@Hermann-Core Hermann-Core left a comment

Choose a reason for hiding this comment

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

I’ve reviewed the implementation and have a few suggestions:

  • Could you consider using AsciiDoc instead of Markdown? AsciiDoc is generally more suitable for structured technical documentation and publishing.
  • Please make the blog more straightforward and accessible, especially for non-technical readers. This should start from the title, which should clearly express the intent of the blog, and be reinforced in the introduction.
  • Clearly expose the goal and scope of the blog from the beginning so readers immediately understand what they will learn.
  • Enrich the documentation with graphical visuals and diagrams to provide more context and make the interactions and overall flow easier to understand.

For reference, you can look at the following implementation as an example of structure and presentation:
keycloak/keycloak-web#682

Copy link
Copy Markdown
Collaborator

@Hermann-Core Hermann-Core left a comment

Choose a reason for hiding this comment

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

The blog looks good overall, I’ve left a few comments below. Could you please review and address them?

Additionally, could you find an appropriate place to include the following diagram flow from the specification?

Image

@ndefokou
Copy link
Copy Markdown
Collaborator Author

@Hermann-Core You can review back the ticket

@ndefokou
Copy link
Copy Markdown
Collaborator Author

image

@Hermann-Core Thanks for the comments i have resolve the comments

@Hermann-Core Hermann-Core self-requested a review December 17, 2025 14:26
@Hermann-Core Hermann-Core self-requested a review December 17, 2025 17:25
@Ngha-Boris Ngha-Boris merged commit a31abff into main Dec 18, 2025
6 checks passed
@Ngha-Boris Ngha-Boris deleted the 442-write-a-blog-post-for-the-status-list-server branch December 18, 2025 09:33
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.

Write a blog post for the status list server

3 participants