wtf is japaneseonchain?

JapaneseOnchain is a small web project that the README pitches as a mix of Japanese culture and Web3 or blockchain content. The live site sits at japaneseonchain.xyz, with a mirror on GitHub Pages. The README describes the project at a high level as bridging traditional Japanese aesthetics with the world of decentralized applications, but it does not go into what specific pages, features, or onchain interactions the site actually offers. A reader looking for concrete details on tokens, NFTs, or any onchain mechanic would need to visit the live site. The repository itself is the deployed build output rather than the source. The tech stack listed is React, Vite, and Tailwind CSS, but only the bundled assets/index-.js and assets/index-.css ship in this repo, along with index.html, a favicon, and a CNAME file for the custom domain. That is why GitHub reports the primary language as HTML. The interesting piece in the repo is the GitHub Actions workflow at .github/workflows/sync.yml. Every six hours, the workflow fetches the latest built files from the Netlify-hosted live site, checks whether the JavaScript, CSS, or HTML changed, and commits and pushes any updates. There is also a manual Run workflow button in the Actions tab. This setup keeps the GitHub Pages mirror automatically in sync with the canonical Netlify deployment. The README provides DNS configuration for anyone who wants to point a custom domain at GitHub Pages: four A records to the GitHub Pages anycast addresses and a CNAME for the www subdomain. It also includes a long block of share-to-Twitter, share-to-Reddit, and share-to-Telegram badges, a star-this-repo prompt, and GitHub stats from the github-readme-stats service. In short, the repository is a deployment artifact and sync workflow for an externally hosted website. The README focuses on hosting, mirroring, and promotion rather than on explaining what the site does or how the Web3 element is wired up.