feat: Update NutriSync to MealForge and change development server port to 4000 #29
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.
This PR updates the website to replace NutriSync with MealForge throughout all content and changes the development server port from 3000 to 4000 to avoid conflicts with other development projects. Key changes include: Updated all NutriSync references to MealForge in project descriptions, hero CTAs, and about page timeline. Updated project features to reflect MealForge's focus on recipe management. Changed language from 'launched' to 'started development' and 'delivering' to 'building' to accurately reflect development status. Updated Next.js configuration and package.json scripts to use port 4000. PM2 process now runs on port 4000, freeing up port 3000 for other development projects.