feat(website): migrate OpenBrowser website to a standalone Next.js application - #4
Open
MukarramBambot wants to merge 1 commit into
Open
feat(website): migrate OpenBrowser website to a standalone Next.js application#4MukarramBambot wants to merge 1 commit into
MukarramBambot wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Summary
This PR restructures the OpenBrowser website into a completely standalone Next.js application based on the feedback provided in the previous review.
The website is now independent from the OpenBrowser runtime and can be developed, built, and deployed without requiring the CLI, browser extension, backend, or the original monorepo.
✨ What's Changed
🏗 Standalone Website
📦 npm Migration
The project has been migrated to a standard npm workflow.
Supported commands:
No
pnpmworkspace or monorepo configuration is required.📚 Documentation
Added a dedicated README containing:
This allows contributors to get the project running without any additional setup.
🎨 Website Improvements
Implemented and refined multiple areas of the website, including:
⚡ Performance
Optimized the application by:
🏛 Architecture Documentation
Expanded the Architecture section with:
✅ Previous Review Feedback Addressed
1. pnpm Dependency
Resolved
The website is now an independent npm project.
2. Runtime / CLI Changes
Resolved
This repository no longer modifies or depends on:
3. Missing Documentation
Resolved
A dedicated README has been added with complete setup and development instructions.
4. Backend Dependency
Resolved
The website now runs entirely on its own.
No backend services are required.
No local bridge is required.
No browser extension is required.
No CLI is required.
Simply run:
🧪 Validation
Verified successfully:
npm installnpm run devnpm run buildnpm startThe website runs successfully as a standalone Next.js application.
📁 Scope
This PR only focuses on the website.
It does not introduce changes to:
💬 Notes
This PR is intended to make the website easier to maintain and contribute to independently from the core OpenBrowser project.
Thank you for the previous review and feedback—it helped shape this standalone version of the website.