Public development record
The journey behind Motionly
Last updated
A chronological look at the research, product decisions, engineering progress, and milestones behind Motionly, from early exploration to active development.
The journey began with research into advanced scroll-driven interactions and how they could be made more accessible to WordPress creators. We explored the challenges of building precise, responsive animations while maintaining smooth scrolling and reliable page behavior.
We explored how animations could respond naturally to scrolling in both directions, allowing motion to follow user input rather than relying entirely on fixed playback sequences.
This early research helped establish the importance of precise interaction control and a consistent relationship between scrolling and animation progress.
The initial research evolved into a broader product concept: a visual system that would reduce the technical complexity of advanced web motion. Instead of focusing on individual effects, we began defining a unified experience for authoring, managing, and reusing animations.
We examined the repetitive work involved in creating sophisticated animations: selecting elements, coordinating triggers, managing timing, adapting behavior across devices, and maintaining consistency.
These challenges helped shape Motionly's central goal: making advanced motion easier to create, refine, and maintain through visual workflows.
A major product decision established Motionly as a standalone WordPress visual builder. Its essential page-building and animation workflows would not depend on Elementor, Bricks, Avada, or another third-party page builder.
Optional integrations remained part of the long-term direction, but independence became a foundational requirement.
We examined established visual builders and animation platforms, comparing their editing experiences, animation capabilities, and WordPress workflows.
The research helped identify opportunities to bring visual motion authoring, responsive control, and a performance-conscious approach into a more unified product.
We began defining how creators would interact with Motionly: selecting elements, configuring animation behavior, adjusting properties, and previewing results directly.
Ease of use for beginners and meaningful control for experienced designers became equally important design objectives.
Research expanded into scroll triggers, sequencing, timelines, reusable animations, and responsive behavior.
These capabilities were organized into a coherent product direction rather than treated as unrelated effects. The goal was a visual workflow that remained understandable as projects became more complex.
We evaluated the technologies needed to support sophisticated motion while maintaining control over performance and compatibility.
GSAP and ScrollTrigger became the foundation of the planned animation system, with optional smooth-scrolling capabilities considered for experiences that require them.
We defined the direction for a native WordPress content structure capable of supporting visual page creation and animation authoring within one system.
This decision laid the conceptual groundwork for a consistent relationship between page content, visual styling, and motion behavior.
Responsive behavior became a foundational design requirement rather than a feature to add after the editor was finished.
The intended experience would allow designers to adapt animation behavior for different device sizes while preserving a predictable editing workflow.
We explored how essential page content could remain accessible even when animations were unavailable, disabled, or interrupted.
This strengthened the product's content-first approach, connecting semantic rendering, reliable page delivery, and progressive enhancement to the broader motion architecture.
We established performance as a core engineering principle. The product direction emphasized avoiding unnecessary frontend resources, keeping page delivery efficient, and preventing animation systems from interfering with essential content.
These requirements began shaping the technical development plan.
We expanded the architecture requirements to include accessible motion, semantic page content, and predictable behavior when animations are unavailable or disabled.
The objective was to make motion an enhancement to the experience without making essential content dependent on it.
We outlined requirements for controlled editing, reliable validation, recoverable changes, and predictable animation execution.
Rather than allowing unrestricted code to define every behavior, the product would use structured, verifiable operations designed to remain manageable as its capabilities expanded.
We explored how a broad range of design options could coexist with a lightweight public-facing experience.
Research covered selective asset delivery, locally served fonts, and resource-loading strategies intended to keep creative flexibility from introducing unnecessary performance costs.
Further planning addressed typography, reusable styling, responsive presentation, and consistent visual controls.
A selective, locally delivered font strategy was chosen to support a broad creative experience without unnecessarily increasing frontend resource usage.
The earlier research and design decisions were consolidated into structured product and engineering documentation.
Core architecture, visual builder requirements, performance, accessibility, compatibility, security, and testing expectations were documented to guide implementation consistently.
Development practices were organized around focused implementation tasks, targeted codebase exploration, automated testing, and controlled changes.
The aim was to maintain consistency between the product vision and actual engineering work while minimizing unnecessary changes to unrelated systems.
The product identity was consolidated around Motionly: a performance-first visual motion builder for WordPress.
Its long-term direction brought together independent visual authoring, advanced motion workflows, responsive design, and a structured foundation for future AI-assisted capabilities.
Development advanced from architecture specifications into working software components.
The native document and validation foundations established a structured basis for representing page content and animation configuration. Automated checks were introduced to verify supported inputs and expected behavior.
Initial rendering components were implemented to turn supported Motionly content into semantic WordPress-compatible output.
This milestone advanced the objective of keeping meaningful page content accessible independently of animation execution.
The initial styling foundation introduced controlled style definitions and consistent CSS generation.
The work focused on predictable output, reusable styling behavior, and the groundwork for efficient page-specific delivery.
Work progressed on the animation runtime using GSAP and ScrollTrigger, with optional smooth-scrolling support.
Early capabilities included basic animation execution, lifecycle management, and controlled handling of unsupported or unavailable behaviors.
Development continued across rendering, styling delivery, and animation execution.
These foundations began forming a consistent technical pipeline, while the complete visual editing and publishing workflow remained under active development.
A unified responsive structure was formalized for the native system.
Implementation work advanced across responsive styling and validation, supported by automated tests. Responsive animation execution and visual editing controls remained separate upcoming milestones.
Automated checks covered native document validation, rendering, styling, asset delivery, animation execution, and runtime behavior.
The review confirmed meaningful progress in the underlying software while identifying the integration work still needed before Motionly could become a usable public product.
The roadmap was refined to include a Claude-first AI Motion Assistant and controlled developer/agent workflows.
The intended approach keeps users in control of AI-proposed changes, with validation and preview remaining central to the editing experience. These capabilities are part of the planned product evolution.
The official website went live, introducing Motionly's product vision, development direction, and planned capabilities.
The early-access system was deployed and successfully tested, establishing a working way for interested creators to register and follow the project's progress.
Motionly is progressing toward its first integrated WordPress visual authoring experience.
Upcoming development priorities include connecting the editor to the existing technical foundations, expanding responsive animation support, and advancing the AI-assisted and developer workflows described in the product roadmap.
Current status: Active pre-alpha development.