Skip to main content

Show HN: Onlook – Open-source, visual-first Cursor for designers

·497 words·3 mins
Hacker News Tech
Articoli Interessanti - This article is part of a series.
Part : Everything as Code: How We Manage Our Company In One Monorepo At Kasava, we've embraced the concept of "everything as code" to streamline our operations and ensure consistency across our projects. This approach allows us to manage our entire company within a single monorepo, providing a unified source of truth for all our configurations, infrastructure, and applications. **Why a Monorepo?** A monorepo offers several advantages: 1. **Unified Configuration**: All our settings, from development environments to production, are stored in one place. This makes it easier to maintain consistency and reduces the risk of configuration drift. 2. **Simplified Dependency Management**: With all our code in one repository, managing dependencies becomes more straightforward. We can easily track which versions of libraries and tools are being used across different projects. 3. **Enhanced Collaboration**: A single repository fosters better collaboration among team members. Everyone has access to the same codebase, making it easier to share knowledge and work together on projects. 4. **Consistent Build and Deployment Processes**: By standardizing our build and deployment processes, we ensure that all our applications follow the same best practices. This leads to more reliable and predictable deployments. **Our Monorepo Structure** Our monorepo is organized into several key directories: - **/config**: Contains all configuration files for various environments, including development, staging, and production. - **/infrastructure**: Houses the infrastructure as code (IaC) scripts for provisioning and managing our cloud resources. - **/apps**: Includes all our applications, both internal tools and customer-facing products. - **/lib**: Stores reusable libraries and modules that can be shared across different projects. - **/scripts**: Contains utility scripts for automating various tasks, such as data migrations and backups. **Tools and Technologies** To manage our monorepo effectively, we use a combination of tools and technologies: - **Version Control**: Git is our primary version control system, and we use GitHub for hosting our repositories. - **Continuous Integration/Continuous Deployment (CI/CD)**: We employ Jenkins for automating our build, test, and deployment processes. - **Infrastructure as Code (IaC)**: Terraform is our tool of choice for managing cloud infrastructure. - **Configuration Management**: Ansible is used for configuring and managing our servers and applications. - **Monitoring and Logging**: We use Prometheus and Grafana for monitoring,
Part : This Article
Featured image
#### Source

Type: Hacker News Discussion Original link: https://news.ycombinator.com/item?id=44127653 Publication date: 2025-05-29

Author: hoakiet98


Summary
#

WHAT
#

Onlook is an open-source, visual-first code editor that allows for the creation and modification of web applications in real-time using Next.js and TailwindCSS. It enables direct modifications in the browser’s DOM and supports integration with Figma and GitHub.

WHY
#

Onlook is relevant for AI business because it offers a visual development environment that can accelerate the prototyping and design of user interfaces, reducing development time and improving collaboration between designers and developers.

WHO
#

Key players include the open-source community, developers, and designers using Next.js and TailwindCSS. Competitors include Bolt.new, Lovable, V, Replit Agent, Figma Make, and Webflow.

WHERE
#

Onlook positions itself in the web development tools market, offering an open-source alternative to proprietary tools for creating and modifying web applications.

WHEN
#

Onlook is currently in active development, with a beta version available. The migration from Electron to a web application has been recently completed, indicating a growing maturity phase.

BUSINESS IMPACT
#

  • Opportunities: Integration with the existing stack to accelerate the development and prototyping process. Possibility of collaborating with the open-source community to improve the product.
  • Risks: Competition with established tools like Figma and Webflow. Need to attract and retain an active community of contributors.
  • Integration: Onlook can be integrated with existing Next.js and TailwindCSS projects, facilitating adoption by developers.

TECHNICAL SUMMARY
#

  • Core technology stack: Next.js, TailwindCSS, React, Electron (in migration phase).
  • Scalability: Good scalability thanks to the use of Next.js, but the migration from Electron has presented significant challenges.
  • Technical differentiators: Visual-first approach with real-time editing, integration with Figma and GitHub, and support for direct editing in the browser’s DOM.

HACKER NEWS DISCUSSION
#

The discussion on Hacker News mainly highlighted the potential of Onlook as a design and development tool. The community appreciated the visual-first approach and integration with established technologies like Next.js and TailwindCSS. The main themes that emerged include intuitive design, the tool’s utility for developers and designers, and the potential for integration with other APIs. The overall sentiment is positive, with recognition of the technical challenges faced and overcome during the migration from Electron to a web application.


Use Cases
#

  • Private AI Stack: Integration in proprietary pipelines
  • Client Solutions: Implementation for client projects
  • Strategic Intelligence: Input for technological roadmap
  • Competitive Analysis: Monitoring AI ecosystem

Third-Party Feedback
#

Community feedback: The HackerNews community commented with a focus on design, tool (20 comments).

Full discussion


Resources
#

Original Links #


Article suggested and selected by the Human Technology eXcellence team, processed through artificial intelligence (in this case with LLM HTX-EU-Mistral3.1Small) on 2025-09-06 10:49 Original source: https://news.ycombinator.com/item?id=44127653

Related Articles #

Articoli Interessanti - This article is part of a series.
Part : Everything as Code: How We Manage Our Company In One Monorepo At Kasava, we've embraced the concept of "everything as code" to streamline our operations and ensure consistency across our projects. This approach allows us to manage our entire company within a single monorepo, providing a unified source of truth for all our configurations, infrastructure, and applications. **Why a Monorepo?** A monorepo offers several advantages: 1. **Unified Configuration**: All our settings, from development environments to production, are stored in one place. This makes it easier to maintain consistency and reduces the risk of configuration drift. 2. **Simplified Dependency Management**: With all our code in one repository, managing dependencies becomes more straightforward. We can easily track which versions of libraries and tools are being used across different projects. 3. **Enhanced Collaboration**: A single repository fosters better collaboration among team members. Everyone has access to the same codebase, making it easier to share knowledge and work together on projects. 4. **Consistent Build and Deployment Processes**: By standardizing our build and deployment processes, we ensure that all our applications follow the same best practices. This leads to more reliable and predictable deployments. **Our Monorepo Structure** Our monorepo is organized into several key directories: - **/config**: Contains all configuration files for various environments, including development, staging, and production. - **/infrastructure**: Houses the infrastructure as code (IaC) scripts for provisioning and managing our cloud resources. - **/apps**: Includes all our applications, both internal tools and customer-facing products. - **/lib**: Stores reusable libraries and modules that can be shared across different projects. - **/scripts**: Contains utility scripts for automating various tasks, such as data migrations and backups. **Tools and Technologies** To manage our monorepo effectively, we use a combination of tools and technologies: - **Version Control**: Git is our primary version control system, and we use GitHub for hosting our repositories. - **Continuous Integration/Continuous Deployment (CI/CD)**: We employ Jenkins for automating our build, test, and deployment processes. - **Infrastructure as Code (IaC)**: Terraform is our tool of choice for managing cloud infrastructure. - **Configuration Management**: Ansible is used for configuring and managing our servers and applications. - **Monitoring and Logging**: We use Prometheus and Grafana for monitoring,
Part : This Article