codeberry.js.org

[cramosmartinez]

• 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://codeberry-compressor.vercel.app

The site content is a developer tool for client-side image compression using WebAssembly and Next.js. It includes a documentation section demonstrating how to use the browser-image-compression library without a backend.

[indus]

@cramosmartinez You missed to fill in the requested information in the PR-Template...
So I had a look at your repos... Looks like this is just a minimal page arround https://www.npmjs.com/package/browser-image-compression
While the library is interesting I don't see how your page ads a lot to it that makes it more related to JavaScript...
Isn't it basically this with better looks?

@MattIPv4 What do you think of https://codeberry-compressor.vercel.app ?

[MattIPv4]

@MattIPv4 What do you think of https://codeberry-compressor.vercel.app ?

Just looks like a webpage that uses JS to me? If it's a demo of an NPM package, then it might be acceptable if the page were to have documentation on using the NPM package yourself, alongside a demo?

[cramosmartinez]

"Hi @indus and @MattIPv4, thank you for the feedback!

You are totally right. My intention is to make this an Open Source Demo/Starter Kit for developers who want to implement client-side image compression using Next.js + WebAssembly, showing that a backend isn't always necessary.

I will update the website today to include a "How it works" section with code snippets and documentation on how to use the package, as Matt suggested. I will also fix the unchecked boxes in the PR template immediately.

Please hold on a bit while I push the changes. Thanks!"

[cramosmartinez]

@indus @MattIPv4 Thank you for the feedback.

I have updated the PR description to fill the checklist as requested.

I have also updated the website deployment. It now includes a "How it works (For Developers)" section directly on the landing page, explaining the client-side implementation and linking to the open-source repository for educational purposes.

You can see the changes live here: https://codeberry-compressor.vercel.app/

Ready for review!

[indus]

Thanks for your understanding. I’m still a bit puzzled by the lack of connection between the subdomain and its content, and I’m simply trusting that this isn’t an attempt to obtain a subdomain for something entirely different.

Welcome http://codeberry.js.org

[cramosmartinez]

@indus Thank you very much for the opportunity and the trust!

I understand your concern. The site is currently under construction, but I assure you it will serve as a hub for my software development projects and technical portfolio. I will be pushing the relevant content (JavaScript/Web dev projects) in the next few hours to reflect the purpose of the domain.

Thanks again for the warm welcome to the community!

[MattIPv4]

it will serve as a hub for my software development projects and technical portfolio.

This goes against JS.org requirements for a subdomain. We do not accept subdomains that are for personal pages.

Your page needs to remain relevant to this specific project, or it will be removed.

[cramosmartinez]

@MattIPv4 Thanks for the concern. I understand that js.org is strictly for development tools and libraries, not personal pages.

I want to clarify that CodeBerry is simply the name I gave to this Open Source Image Compression Tool. It is not a personal portfolio, blog, or business page. It is a single-purpose utility for the developer community.

To prove this:

I have updated the GitHub Repository README to clearly document it as an open-source tool for client-side compression.

I have updated the website's metadata and landing page to focus solely on the technical functionality and the code implementation (as seen in the new "How it works" section).

The goal of this subdomain is to host this specific tool/demo for the community, showcasing privacy-focused client-side processing.

If "CodeBerry" is deemed too generic, I am happy to rename the subdomain to codeberry-compressor if that helps clarify the intent. Please let me know.

[indus]

I've marked this with the provisional content label to make sure to check back on it. A substantial shift towards "portfolio" may make me revoke this subdomain (with respect to ToS §3 3 )