0b64d8086c
* apps/web: add generic privacy & offer pages * Update environment variables and enhance offer and privacy pages - Added `OFFER_URL` and `SUPPORT_TELEGRAM_URL` to environment variable configuration for better flexibility. - Updated the offer page to dynamically link to the offer URL and improved contact information presentation with a direct link to the support Telegram. - Revised the privacy policy page to reflect the service name and updated contact details, ensuring clarity and consistency in communication. * move offer & privacy -> (documents) sub directory * Update offer and privacy pages to include user consent for third-party data sharing - Added a clause in the offer page requiring users to ensure consent from third parties when adding their contact information. - Updated the privacy policy to clarify that users can share third-party data, emphasizing the need for consent for data processing within the service. * Add privacy agreement and update environment variables - Introduced `PRIVACY_URL` to the environment configuration for dynamic linking. - Updated localization files to include a user consent agreement for sharing phone numbers, linking to the offer and privacy URLs. - Enhanced welcome and contact addition messages to incorporate the new consent clause, improving user clarity on data handling. * Refactor phone agreement localization and enhance user consent messaging - Updated the Russian localization file to streamline the phone sharing agreement, improving clarity on user consent for data processing. - Modified the contact addition and welcome messages to incorporate the new agreement format, ensuring users are informed about their consent to share personal data. * Enhance Russian localization and update message formatting - Added a new payment agreement clause in the Russian localization file, clarifying user consent for payments. - Updated message formatting in the contact addition and subscription processes to support HTML parsing, improving message presentation and user experience. - Incorporated the new payment agreement into the subscription flow, ensuring users are informed about their consent to the terms. * Refactor Russian localization for contact agreements and enhance user consent messaging - Updated the Russian localization file to separate and clarify the phone sharing and contact sharing agreements, improving user understanding of consent requirements. - Modified the contact addition and welcome messages to utilize the new agreement format, ensuring users are informed about their consent to share personal data in a more structured manner. * Enhance Russian localization and add document handling features - Updated the Russian localization file to include new entries for privacy policy and public offer documents, improving user access to important information. - Added 'documents' command to the bot's command list, allowing users to easily access document-related features. - Integrated document handling in the main menu and handlers, enhancing user experience and navigation within the bot.
Turborepo starter
This is an official starter Turborepo.
Using this example
Run the following command:
npx create-turbo@latest
What's inside?
This Turborepo includes the following packages/apps:
Apps and Packages
docs: a Next.js appweb: another Next.js app@repo/ui: a stub React component library shared by bothwebanddocsapplications@repo/eslint-config:eslintconfigurations (includeseslint-config-nextandeslint-config-prettier)@repo/typescript-config:tsconfig.jsons used throughout the monorepo
Each package/app is 100% TypeScript.
Utilities
This Turborepo has some additional tools already setup for you:
- TypeScript for static type checking
- ESLint for code linting
- Prettier for code formatting
Build
To build all apps and packages, run the following command:
cd my-turborepo
pnpm build
Develop
To develop all apps and packages, run the following command:
cd my-turborepo
pnpm dev
Remote Caching
Turborepo can use a technique known as Remote Caching to share cache artifacts across machines, enabling you to share build caches with your team and CI/CD pipelines.
By default, Turborepo will cache locally. To enable Remote Caching you will need an account with Vercel. If you don't have an account you can create one, then enter the following commands:
cd my-turborepo
npx turbo login
This will authenticate the Turborepo CLI with your Vercel account.
Next, you can link your Turborepo to your Remote Cache by running the following command from the root of your Turborepo:
npx turbo link
Useful Links
Learn more about the power of Turborepo: