New Site Design Astro Migration & Modernization (V2)#38
New Site Design Astro Migration & Modernization (V2)#38shadstoneofficial wants to merge 12 commits into
Conversation
|
Tailwind isn’t a design system. Right now this just looks like generic output, no visual identity, no UX personality. Hard pass on the aesthetic. Pr for updates I’d be open to but not with this “redesign” attached. |
|
This proposal leans more into a code update than a formal modernization of the Handshake.org site itself. Essentially, what's being proposed in the moment is better than what currently exists. Therefore, implementing this proposal could act as a signal the Handshake protocol and community are alive and well. However, the proposal doesn't necessarily carry a long-term aesthetic. The vibe-coded feel could hurt the site's sense of authority in the long-run - so it would need to be updated eventually. It would also be nice to add additional features to the site that accentuate Handshake's capabilities and community contributions. |
|
I already said in my previous comment I was open to updated information. Your comment back neglects to point that out. You stated yourself the “vibe coded feel” could hurt the site’s authority long term. That alone makes attaching this redesign direction basically DOA. Modernization, redesign, and updated information are three different conversations that have no place being bundled together in a one shot all in one update. |
|
@taylormartens The posted comment wasn't in response to you. It was for @shadstoneofficial. While on the subject of your response though, "Modernization, redesign, and updated information" are indeed three different branches of consideration. This is coming from someone with extended experience with each. This proposal may not be comprehensive - but it's definitely timely considering where things are in the age of vibe-coding. As originally stated, the proposal doesn't necessarily carry a long-term aesthetic - but it would make the Handshake.org site current. Not captivating or competitive. Just current. In due time, there will be a need for more robust UI, UX and information updates. Considering the state of the protocol and community sentiment at the moment, those robust changes can't be a top priority where consensus is scattered. |
|
Its time to change |
|
https://handshakenew.skyinclude.com/files/handshake.txt |
|
Personally, I think that page [1] looks amazing. |
|
Added the requested whitepaper/design notes update across the site. Changes included
Updated locations
Also verified
Build cleanup
One non-blocking Vite warning remains because the Three.js chunk is still larger than the default warning threshold, but this does not affect functionality or deployment. |
|
I have some ideas can improve and update handshake's whitepaper this is first idea to add for example ' https://dx.doi.org/10.2139/ssrn.6757159 ' "its Punycode and Unicode" another will add soon... |
page 5 has problem could you please resolve it, thank you |
|
Respect for the initiative and the effort! 👏 I liked the minimalistic design of the old page better, and I think we should stick with it if possible. But I also salute the updates. I would agree with a mixed version keeping original design and only updating the content. |
|
This is an open source protocol. I think it needs to be updated every day, even if it's just 1%. |
|
How can we upgrade Handshake whitepaper?? |
|
@HellotoSinaa that is a big question to update a whitepaper.... I have been thinking about this PR for a while and I am not going to ruffle feathers trying to update this website. if you'd like I can make an account for you on https://learnhns.com as a community contributor there and you can make posts for an updated whitepaper, maybe you could make your own version updated and can cite it. but to change a whitepaper in my opinion is a big ask. |
6 participants
Overview
This Pull Request represents a comprehensive migration of the Handshake website from raw HTML/CSS to a modern Astro (v4) architecture with Tailwind CSS.
The goal of this migration is to significantly improve the developer experience, make the site easier for the community to maintain, enhance SEO, and modernize the visual aesthetic to reflect Handshake's role as serious, decentralized infrastructure (shifting away from the heavy "crypto/blockchain" purple aesthetics to a clean, professional monochromatic grey/black theme).
🔗 Live Preview
https://handshakenew.skyinclude.comKey Architectural Changes
.htmlfiles into modular.astropages and components (Layout.astro,Header.astro,Footer.astro). This prevents code duplication (like having to update the header 20 times).legacy/directory is kept intact in the repository to ensure no historical data is lost.@tailwindcss/typographyto ensure they render beautifully in the new layout.three.jsinteractive "interconnected network" background to the homepage hero to visually represent the peer-to-peer network.Feature Additions & Fixes
@astrojs/sitemapto auto-generatesitemap-index.xml. Added custom meta descriptions to all primary pages./skill.mdand/llms.txtendpoints configured to returntext/plainso AI agents can natively read Handshake rules and login instructions via headless SSO./discord,/telegram) into native server-side redirects viaastro.config.mjs..ioto.org.Testing Instructions for Reviewers
npm installnpm run devhttp://localhost:4321./faq,/grant-sponsors,/community, and/notice.Deployment
This project includes a
.github/workflows/deploy.ymlconfigured to use the officialwithastro/action. Upon merging tomaster, the Astro site will build and push statically to the GitHub Pages branch.