Documenting code, one commit at a time.
This post discusses a recent update to our post generation process, shifting from hardcoded sections to a more adaptable, example-driven approach.
Previously, our post generation system rigidly enforced a predefined structure: Introduction, Development, Examples, and Conclusion. This inflexible format ignored the nuances and varied structures of different example posts,
Our landing page was primarily targeted towards individual developers. To broaden our reach, we've pivoted to include a stronger B2B narrative and activate our Enterprise plan.
The previous landing page lacked specific content and messaging to attract institutions such as academies, bootcamps, and universities.
This post addresses an issue where a billing system, specifically when using a service like Cashier, fails to correctly identify active subscriptions beyond the default type. We'll explore the problem and provide a solution to ensure all subscription types are properly recognized.
In many billing systems, especially those utilizing
Recent development efforts have focused on enriching the quoting module within our application. These enhancements streamline the user experience and improve overall functionality by introducing autocomplete capabilities, refined matching algorithms, and integrated conversation features.
The addition of autocomplete significantly
This post details an enhancement to our application's data aggregation process. We addressed an issue where total counts were inaccurate by switching from a local database to an external API for data retrieval, ensuring more reliable results.
Previously, our application relied on a local database table, populated with data from an events API,
Recently, we identified and resolved an issue in our LLMsController related to accessing tenant information. Additionally, we enhanced our job application management process by adding a missing relation manager.
The initial implementation of the LlmsController attempted to
Sometimes, maintaining a clean codebase involves removing outdated or redundant elements. This post details a recent cleanup effort focused on database tables and user interface text within our application.
Our investigation revealed that certain fields in the tenants table – specifically description and company_website – were no longer actively used.
We recently refined our post generation process to provide users with greater control over the final output, especially when incorporating creative or specific instructions. These enhancements focus on improving how user prompts are interpreted and applied during the content creation process.
Previously, user-provided
This update refines the language used in the developer portal to better resonate with individual developers. It involves reverting a B2B-focused hero section to its original developer-centric narrative and consistently using "developers" instead of "builders" across multiple language files.
The primary focus was on aligning the messaging with the target
To create a more engaging landing page experience by embedding a short, autoplaying promotional video.
A dedicated video project was created using Remotion v4 to produce a 20-second promotional video. The video highlights key features and provides a call to action.
The video was structured into five distinct scenes:
