opencc.js.org

[frankslin]

This website is a landing page for NPM package opencc-wasm, a WASM library based on OpenCC, an open-sourced Chinese conversion tool.

Website code is available from https://github.com/frankslin/opencc-wasm-demo-site/ and deployed to a CloudFlare Page.

The WASM library code is available from https://github.com/frankslin/OpenCC/tree/master/wasm-lib.

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions
• The site content can be seen at https://github.com/frankslin/opencc-wasm-demo-site/ (hosted on https://opencc-wasm.pages.dev/ )

The site content is a landing page showcasing how to use the opencc-wasm library available at https://www.npmjs.com/package/opencc-wasm. It doubles as a web-based Chinese (Simplified/Traditional) converter using OpenCC WASM library inside user's browser.

[MattIPv4]

👋 While I appreicate that the page is a demo of the NPM package, at present unless I'm missing something, it is just that, only a demo -- just a webpage that happens to be built with JavaScript as is every other page on the web, with nothing about it being specifically useful to other JavaScript developers.

Could I suggest updating the page to include explicit documentation for the NPM package, to guide other JavaScript developers on how they could use it for their own projects?

[frankslin]

Thank you for the feedback! That makes total sense.

I’ve updated the homepage so that it now serves as the landing page for the OpenCC WASM library, rather than just a standalone demo. It currently includes:

• An explicit description of the library’s purpose
• JavaScript-facing API usage examples
• Guidance on how this NPM package can be integrated into other frontend projects
• An explanation of what differentiates it from existing ports (for example, opencc-js and wasm-opencc)

I plan to continue expanding the documentation on both the homepage and the GitHub repository as the API stabilizes and additional usage scenarios are documented.

The page should now more clearly reflect how the library is intended to be used by JavaScript developers.

[indus]

I've already added your requested subdomain to JS.ORGs zonefile. You may have to configure your host to accept the custom domain. FYI: https://github.com/js-org/js.org/wiki/3rd-party-hosts

For Cloudflare Pages, you will need to add the JS.ORG subdomain to your project as a custom domain via the API: https://developers.cloudflare.com/api/operations/pages-domains-add-domain -- it is not possible to add the JS.ORG subdomain as a custom domain through the Cloudflare dashboard.

I'll merge after we have "contact". Please keep this PR open.

[frankslin]

The Attach To Domain API on Workers has a zone_id field which I don't have. As it turns out, unlike CloudFlare pages, using CloudFlare worker is explicitly not supported with a custom domain from a different account. I suggest adding this limitation to the Wiki so the next users don't have to try setting it up on CF Workers. :)

Error 1014 CNAME Cross-User Banned
What happened?
You've requested a page on a website that is part of the Cloudflare network. The host is configured as a CNAME across accounts on Cloudflare, which is not allowed by Cloudflare's security policy.

Please see https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/ for more details.

I'll move the site to a CF Pages.

[indus]

You have to update the target in the cname list to match you new hosting.

[frankslin]

The branch is updated and rebased.

[indus]

@frankslin I've just made the change in JS.ORGs zonefile but still get the Error 1014. Maybe it needs time to propagate or you need to re-set the CNAME via the api endpoint.

[frankslin]

It works now! https://opencc.js.org/

[indus]

Welcome https://opencc.js.org