Migration to Turbo Repo and TypeScript Support with Shadcn-UI Integration #131
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
…n-UI support, remove unused files and configurations. Fix: Correct main domain redirect to 2023. issue: #129
❌ Deploy Preview for pyconug failed.
|
This commit fixes a bug in the `next.config.js` file related to rewrites. The rewrites for the `/2024` route were missing, causing incorrect redirection. This commit adds the missing rewrites for the `/2024` route, ensuring proper redirection.
This commit adds the `Head` component from the `next/head` package to the layout components in the `2023` and `2024` apps. The `Head` component is used to add a `link` tag that preconnects to the Google Fonts API, improving the performance of font loading. Additionally, the commit updates the `next.config.js` file to fix a bug related to rewrites for the `/2024` route. The missing rewrites were causing incorrect redirection, and this commit adds the necessary rewrites to ensure proper redirection. Fixes #129
Merged
…onUg/ug.pycon.org into ch-migrate-repo-to-turborepo
This commit updates the redirects in the `netlify.toml` file for the `2023` and `2024` apps. The redirects now point to the correct URLs for the respective apps. This ensures proper redirection for the users. Fixes #129
…mages This commit updates the .gitignore file to include the "public" directory, ensuring that it is ignored by Git. It also updates the netlify.toml file to change the "publish" value to "public" for the build command. Additionally, it adds lazy loading for images in the layout components of the 2023 and 2024 apps, improving the page load performance. Fixes #129
…igure build settings This commit adds the "@netlify/plugin-nextjs" package to the list of plugins in the "netlify.toml" file. It also updates the build settings by specifying the build command as "npm run build" and the publish directory as "public". These changes are made to improve the build process and ensure the correct deployment of the Next.js application. Fixes #129
…igure build settings
… package.json for 2023 and 2024 apps - migrate the app to turborepo - create shared packages for the apps - rewrites for 2023 app
…onUg/ug.pycon.org into ch-migrate-repo-to-turborepo
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.
This PR includes several major changes to improve our codebase and fix a critical bug:
Migration to Turbo Repo: The application has been migrated to Turbo Repo to streamline our monorepo management and improve build times.
TypeScript Support: TypeScript has been added to the project. This will help us catch errors early in the development process and make our code more maintainable and scalable.
Shadcn-UI Integration: We've integrated Shadcn-UI into our project to improve our UI development process and ensure consistency across our application.
Removal of Unused Files and Configurations: To keep our codebase clean and efficient, we've removed unused files and configurations.
Pending Bug Fix: We've fixed a bug where the main domain was incorrectly redirecting to 2023.
The changes in this PR touch on several parts of our codebase. Please review carefully to ensure that everything is in order.
Related Issue: # (If applicable)
Changes Made:
issue: #129