feat: redesigned publisher tools article #158
Open
Conversation
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
sidvishnoi
reviewed
Oct 24, 2025
Member
sidvishnoi
left a comment
sidvishnoi
left a comment
There was a problem hiding this comment.
I like the overall content in the technical article.
I think the order of content can be adjusted so the user has to know less things upfront, by using the flow only, and maybe moving the flow diagram towards the end to give readers a summary.
Also, maybe we should not link the repo structure too much with the article structure.
| 3. Script fetches configuration → `api` retrieves stored JSON and returns it | ||
| 4. Script renders the Tool → Instantiates Web Component from `components` with fetched configuration | ||
|
|
||
| This system cleanly separates responsibilities: publishers customize through the interface (the `frontend` module), and visitors consume the configuration at WebPage runtime. The `frontend` and visitor-facing flow never interact directly, they're connected only through stored configuration. |
Member
There was a problem hiding this comment.
Can also mention the components you see in preview are exactly same as what your users will see, as we use web components.
Member
There was a problem hiding this comment.
I see that's mentioned in a section below.
src/content/blog/2025-10-23-redesigned-publisher-tools-technical.md
Outdated
Show resolved
Hide resolved
src/content/blog/2025-10-23-redesigned-publisher-tools-technical.md
Outdated
Show resolved
Hide resolved
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.
No description provided.