oalexdoda / webflow-react Goto Github PK

View Code? Open in Web Editor NEW

86.0 86.0 6.0 1.08 MB

A CLI tool used to convert a Webflow project to React JS.

Home Page: https://npmjs.com/package/webflow-react

License: Apache License 2.0

JavaScript 100.00%

react reactjs webflow webflow-sdk

webflow-react's Introduction

Serial Tech Entrepreneur

webflow-react's People

Contributors

Stargazers

Watchers

Forkers

thedemodev techkayacodes mukundarizon 0xjinbe taneron rocklandceo

webflow-react's Issues

Generate default controllers for components with sockets

Let's say you have a component called "menu". And Then you have multiple "menuItem" components inside that menu. A default controller (or meta?) could be generated by the script under "default.js" where it would work like this:

If there's multiple "menuItem" components inside "menu", it would create a content map using the "wfr-d" data points in each menu item. Rather than having to define data points for each "menuItem" component, it would try to identify the children of each menuItem (by class) and map those out.

Clean up duplicate attributes when using "wfr-a" to assign dynamic attributes

Views do not get overwritten by controllers properly.

Iframes (and maybe embeds too?) get an additional "/" and do not render properly

Do not create views if the <body> has "wfr-ignore" on a Webflow page

Pages with dashes in their name are not routed properly

Allow the config to be declared via package.json instead of just wfr.config.js.

Scripts in "/scripts" do not automatically include the main Webflow JS script

Upgrade all dependencies and fix babel errors.

Remove the es-lint disable / enable tags

Is this appfairy?

Just quickly looking on readme this feels like an exact copy of this https://github.com/DAB0mB/Appfairy

Replace all <a href="#"> with <button>

Inputs without a data socket are not rendered properly

Could it be because they render as open-close elements rather than self-closing?

Adding props to the component won't render properly

If we create default controllers, we could add a wfr attribute that generates a starter API structure

If we create default controllers #13 , we could add a wfr attribute that generates a starter API structure. For example if a component defined with "wfr-c" also has the "wfr-api" attribute and a value of "/api/v1/content.json", the default controller could have an Axios starter blueprint to easily fill that component with data from an API.

Run "Prettier" or a beautifier before saving components, views, etc.

Prevent exporting empty stylesheets to /styles

Move helpers.js into a dependency library

Instead of exporting helpers.js, this could be a node module:

import { helpers } from 'webflow-react'

If components get restructured, controllers could be part of each component's folder

If issue #4 gets solved, each controller could go under each component's folder:

e.g.

components/
    header/
        controller.js
        index.js

Not sure if it's the best structure, but rather than storing them separately, this would also help with nested folders for issue #4

components/
    menu/
        index.js
    widget/
        components/
            account/
                index.js
            feedback/
                index.js
            upgrade/
                index.js
        index.js

Note: They would have to identify their controllers properly considering the structure change.