konradhy / build-jotion

Convex Build Bounty Submission - Build with Jotion

Hi 👋, I'm Konrad.

I'm a fullstack developer. I'm pretty lucky to have found a career that I love.

• 🔭 I’m currently focusing on Casefold. An app that helps attorneys read cases and legislation faster

• 💭 Specializing in generative AI, automation and solutions for small and mid-sized businesses

Portfolio Repositories:

• 💻 LaunchPie - https://github.com/konradhy/launchpie-public

• 💻 BattleArena - https://github.com/konradhy/battlearena

• 💻 Jotion - https://github.com/konradhy/build-jotion

Languages and Tools:

build-jotion's Issues

Fix Unexpected Query Trigger Behavior in Application

Context
There are currently unexpected triggers of functions like getById due to the current provider setup, leading to potentially unwanted behaviors.

Objective

• Identify and resolve the causes of unexpected query triggers.
• Streamline the provider setup to prevent similar issues.

Action Items

1. Analyze Current Provider Setup: Thoroughly review the setup to identify the cause of the issue.
2. Implement Necessary Changes: Make adjustments to prevent unwanted query triggers.
3. Test for Stability: Ensure the modifications resolve the issue without introducing new problems.
4. Document Changes: Update technical documentation with the new configuration.

Implement Integrated Communication Tools

Context
As part of enhancing collaboration tools, I plan to integrate chat and commenting features within the platform. This will enable dynamic collaboration and streamline communication between users.

Objective

• Develop and integrate a chat system within the application.
• Implement a commenting feature for documents.

Action Items

1. Design the Chat Interface: Conceptualize and design the chat interface, ensuring it aligns with the current UI/UX.
2. Develop Chat Functionality: Implement real-time chat capabilities.
3. Create Commenting System: Develop a system for users to comment on documents.
4. Test Features: Rigorously test for usability and reliability.
5. Document Functionality: Update project documentation to include these new features.

Refactor OpenAI-Edge API Calls to Use Actions

Context
Currently, API interactions with OpenAI-Edge are handled via Axios. I plan on refactoring these to use Actions.

Objective

• Replace Axios calls with Actions for configuring GPT-3.5 Turbo in the AI tools.
• Maintain performance and reliability of AI features in the text editor.

Action Items

1. Identify Axios Calls: List all Axios calls to OpenAI-Edge.
2. Develop Action Replacements: Create corresponding Actions for each Axios call.
   2.5Consider other function types and improved functionality: Such as internal actions and more useful prompts
3. Test New Implementations: Ensure each Action works correctly with the text editor's AI tools.
4. Remove Axios Implementation: Clean up the codebase post-migration.
5. Document Changes: Update technical documentation to reflect the new approach.

Additional Notes

• Observe the performance implications of the change.
• Implement fallback strategies during the initial deployment phase for added reliability.

Transition Image Storage from Edgestore to Convex File Storage

Context
I am planning to migrate the image storage from Edgestore to Convex File Storage. This shift aligns with the project's long-term goals for better performance, integration, and ease of maintenance.

Objective

• Transition image handling from Edgestore to Convex File Storage.
• Ensure minimal impact on existing functionalities.

Action Items

1. Plan for Convex File Storage Integration: Outline the steps for integrating Convex File Storage.
2. Develop and Implement Changes: Code the necessary changes for the transition.
3. Test the New Setup: Ensure the new implementation functions correctly.
4. Update Project Documentation: Document the changes and any new procedures.

Benefits

• Improved performance and scalability.
• Better synergy with the current tech stack.
• Easier maintenance.