Styled Page (Discontinued)

Visual builder for React apps and websites.

Visit Website
May 10, 2020 Upgraded the editor to load a large app

Phew - SP can now load larger Gatsby apps such as the Reactjs.org website.
It's definitely not perfect yet (e.g. the CSS prop on the right shouldn't have to be edited manually, but through the visual interfaces below) but I feel great about the potential for designers and developers to collaborate on production apps.

Here's a screenshot:
react.js org in styledpage

Comment

May 9, 2020 Integrated Stripe's self-serve portal

Man, creating this dashboard where customers can change their plan myself was such a pain. So I'm happy to switch to Stripe's managed dashboard. It wasn't a lot of work to switch, but then by now I'm very familiar with Stripe and their API's.

This is what the flow looks like now:
stripe flow

3 Comments

  1. 2

    This is great. Definitely thinking about porting over my custom-rolled billing tool for Lensant to this. (When I rolled my own billing page, I was too lazy to add a way for customers to change their billing method...instead, I told them to cancel their subscription and resubscribe with the new payment method.)

  2. 1

    Outseta is a Stripe Verified Partner and offers very similar functionality via a Javascript Widget that can be implemented in 2-3 minutes. https://go.outseta.com/support/kb#/articles/ngWKv9pr/how-to-integrate-outseta-s-profile-widget-with-your-website

May 6, 2020 Two-way WYSIWYG editing working!

You can now WYSIWYG-style edit text and properties, while editing code at any time for maximum flexibility.

This is a big deal because over time it further narrows down the gap between designers, non-technical persons and programmers.

two-way WYSIWYG editing

Comment

May 1, 2020 Landing page live, built using our own platform!

I've uploaded the first version of the new landing page! I'm happy this finally got done, as I have some incoming links to the site. Visitors used to see a server error message before, because I have been busy migrating the old landing page. So SEO juice should now start flowing in again.

The page is built using Styled Page itself. I started from a GatsbyJS template, uploaded ("pushed") it to the platform and then gradually changed styles and the layout using the visual editor. I do switch to code mode from time to time as that's sometimes faster. (The editor reads and writes code.)

Here's a screenshot of the editor:
styledpage.com built using the editor

Peace out,
Nick

Comment

April 28, 2020 Support for GatsbyJS!

Styled Page now supports GatsbyJS! This means you can now build static sites and edit them visually online. I scratched my own itch here as I was in need for a static site but still wanted to build it visually, and using React.

You can see a first site built with the tool on https://laska.io/
It's really neat as I can push/pull code as I want, use any NPM component and have it visually rendered online, all while being able to use GatsbyJS without any downsides.

Here's a screenshot of the editor:
laska.io built with styledpage.com

The actual landing page for Styled Page is still underway, stay tuned!

Comment

March 17, 2020 Pivot towards React developers

Until now, the editor was tailored towards people that are new to building web applications. This can work, but I've found that I have to create a ton of tutorials and help content in order to make this work.

Based on feedback from React developers, I'm trying an experiment to cater towards React developers: the ability to visually edit (WYSIWYG-style) new and existing React apps and websites, while maintaining the ability to edit code at any time. I haven't seen this in other editors (others only provide exporting code) and while hard to pull off, this can actually work.

MVP Demo

The goal is for React developers to shave off valuable development time by 20-50%. Companies can thus potentially save thousands of dollars of engineering time using this tool.

The engineers themselves save time by

  • instantly seeing what they are building
  • not having to write imports
  • not having to write JSX code
  • not having to look up which props are available for every component
  • not having to guess what data structure the props are
  • not having to write styling code themselves

Engineers don't lose any abilities. There's no "catch". They can always continue coding if they prefer. In other tools, they'd be stuck at this point since the export function is one-way only. As an additional bonus, non-technical people can collaborate with engineers.

As a first test I'll be focusing on the Semantic UI framework as I have some experience with it.

Comment

February 17, 2020 Finished MVP

It took forever, but the web version is out! My partner and I think it's really cool and use it internally, but it still needs a lot of feedback to make the product better.

Next, I will be focusing 50% of my time on traction/customer development and the other 50% on development/support/bugs.

Comment

About

Spin-off from already existing React Native builder (Laska), which shares the same engine.