Docs Site: Improve Architecture Page Fallback Navigation#116
Docs Site: Improve Architecture Page Fallback Navigation#116kavitha-047 wants to merge 3 commits intoAndrewRedican:mainfrom
Conversation
Improved the fallback state for the root architecture page when documentation content is not yet available. This change adds a clearer message and a navigation link back to the main documentation so users are not left at a dead end.
|
@kavitha-047 is attempting to deploy a commit to the hyperfrontend Team on Vercel. A member of the Team first needs to authorize it. |
|
✅ All contributors have signed the CLA. Thank you! |
|
I have read the CLA Document and I hereby sign the CLA |
|
View your CI Pipeline Execution ↗ for commit f39bbea
☁️ Nx Cloud last updated this comment at |
|
Hi @kavitha-047 after some careful consideration, I won't be accepting this change. It's no longer needed, as all architecture details have been provided. When a link leads to a page that does not exist, there is a 404 page that helps a user get back on track. Alternatively, based on your experience instead, you could share with me how was your self-onboarding experience like, any particular paint points, and we can discuss how to improve and plan what changes can be done to the codebase. |
|
Hi @AndrewRedican, thanks for the clarification!
My onboarding experience was interesting, but I did face a few challenges:
-
It took me some time to understand the overall architecture and how
different parts of the project connect.
-
I wasn’t always sure where to start or which files were the right entry
points.
-
Some setup or flow explanations could be a bit clearer for new
contributors.
I think adding a simple “getting started flow” or visual overview of the
architecture could really help new contributors ramp up faster.
Happy to explore this further and contribute improvements if needed!
…On Tue, Apr 21, 2026 at 2:24 AM Andrew Redican ***@***.***> wrote:
*AndrewRedican* left a comment (AndrewRedican/hyperfrontend#116)
<#116?email_source=notifications&email_token=BOOJO3WBKL4MNOI5W6T33BL4W2E7LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRYGQZDCNJYHE2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4284215894>
Hi @kavitha-047 <https://github.com/kavitha-047> after some careful
consideration, I won't be accepting this change. It's no longer needed, as
all architecture details have been provided. When a link leads to a page
that does not exist, there is a 404 page that helps a user get back on
track.
Alternatively, based on your experience instead, you share with me how was
your self onboarding experience like, any particular paint points, and we
can discuss how to improve and plan what changes can be done to the
codebase.
—
Reply to this email directly, view it on GitHub
<#116?email_source=notifications&email_token=BOOJO3WBKL4MNOI5W6T33BL4W2E7LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRYGQZDCNJYHE2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4284215894>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOOJO3SEEKKD3NB7YMMRROL4W2E7LAVCNFSM6AAAAACXQZNVLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEOBUGIYTKOBZGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Improved the fallback state for the root architecture page when documentation content is not yet available.
This change adds a clearer message and a navigation link back to the main documentation so users are not left at a dead end.