v3 initial commit

[JonDevOps]

• I have read w3Develops contribution guidelines.
• My pull request has a descriptive title (not a vague title like Update index.md)
• My pull request targets the production branch of production.
• None of my changes are plagiarized from another source without proper attribution.
• All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
• My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

[gemini-code-assist]

Summary of Changes

Hello @JonDevOps, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request represents an 'initial commit' for what appears to be a new major version (v3) of the project. The primary focus is a comprehensive overhaul, marked by the removal of a substantial amount of legacy code and configuration, particularly from a previous Open Source Social Network (OSSN) implementation. This extensive cleanup aims to establish a fresh foundation, introducing new tools like Firebase and reorganizing repository metadata for a streamlined development environment.

Highlights

• Extensive File Removal: A large number of files, particularly those related to the Open Source Social Network (OSSN) framework, including core classes, actions, components (Ads, AutoPagination, Block, Chat, Comments, Embed, Groups), and their associated localization and plugin files, have been removed. This indicates a significant architectural shift or a complete rewrite.
• CSS and Configuration Cleanup: Multiple CSS files (e.g., agency.css, hero.css, w3develops.css) and various configuration/metadata files (Gemfile, LICENSE, _config.yml, browserconfig.xml, brave-rewards-verification.txt) have been removed, streamlining the project's dependencies and styling.
• GitHub Workflow Reorganization: All files within the .github/ directory, such as CHANGELOG.md, CODEOWNERS, CONTRIBUTING.md, and issue/PR templates, have been renamed to reside under a new .github/.github/ subdirectory, suggesting a restructuring of the repository's contribution guidelines and automation.
• New Core Files: A .firebaserc configuration file has been added, indicating the integration or preparation for Firebase services. A new .gitignore copy file has also been introduced, likely to manage version control exclusions for the new project structure.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request appears to be a major rewrite, migrating the project to a new technology stack, likely Next.js, and removing the previous PHP-based implementation. This is a significant change, and the pull request description should be updated to provide context and details about this migration. I've identified a few important issues that need to be addressed, including a hardcoded project ID, a potentially misnamed .gitignore file, and the removal of the project's LICENSE file, which is a critical issue for an open-source project.

I am having trouble creating individual review comments. Click here to see my feedback.

LICENSE (1-51)

The LICENSE file has been removed. Every open-source project must have a license to inform users of what they can and cannot do with the code. Removing the license file leaves the project in a legally ambiguous state. Please restore the LICENSE file or add a new one that reflects the project's licensing terms.

.firebaserc (3)

Hardcoding project-specific identifiers like this Firebase project ID is a security risk and makes it difficult to manage different environments (dev, staging, production). It's highly recommended to use environment variables for such configurations. This allows for greater flexibility and security, as sensitive information is not stored in the version control system.

.gitignore copy (1-44)

This file appears to be a .gitignore file but is named .gitignore copy. Please rename it to .gitignore so that Git can correctly ignore the specified files and directories. Without the correct name, these files might be accidentally committed to the repository.