Hacker News Reader

Hacker News

Comment by johndamaia | Hacker News Reader

Parent Full thread

johndamaia

Great questions. And I also understand your skepticism. You're not the first and don't expect you to be the last :)

Trying to answer all your questions:

- Our models learnt website's components visually (e.g. what is a navbar, an input, a button, etc)

- The output is a .zip file with the .html files and directories for css, js and img

- All Vue components can be found in main.js inside the js directory

- Vue components are built when 'duplication' is recognized (e.g. a sequence of cards or several links for a navbar). Nothing fancy

- CSS is vanilla, trying to ditch as many inline style as possible (working on it as we speak :) )

- All SVGs are imported with the img element.

Let me know if you have more great questions.

View on HN

Cool, thanks for the reply. For me making components is the hard work, anything that helps automate organizing / naming / and synchronizing a component library with sketch sounds intriguing to me. Is the output intended to be code-edited by a developer to add hrefs, interactivity? Is it intended to generate pseudo components for later finessing or is it intended to produce the final outcome of a site directly from sketch (making Sketch the new dreamweaver?)

It's intended to be code-edited by a developer. The goal is to have an advance starting point. You'll start with "everything" ready to work on the fun stuff. If you curious enough to see the output I'm happy to share the code from our demo. If it makes sense drop me a line at john [@] zecoda.com

Hi. I would like to have an option of using just the automated part of the service and do the developer part myself. If hypothetically you would include that option, how cheaper do you think it wold be compared to the current price ? Also one more option: convert design to just HTML and CSS, without javascript or framework of any kind. Would that make sense ?

Interesting feedback. Our main goal is to ditch the human verification, we want to be confident enough to provide great code automatically. Not there yet.

Regarding the output, it's great to know your thoughts on the frameworks. We actually went for a framework to make it simple for our users. In the future we want to allow our users to chose what output they want. So, it makes total sense.

Sounds good. Regarding the no-framework output, I'm not against frameworks, I was just thinking for a moment from the perspective of a more traditional web designer who only incorporates bits of pre-made JS code in their design. Such a person might not even know what Vue.js is but may still greatly benefit from your service if it allowed them to convert their designs to just html/css.

how is this different than working with a really good starter kit? I guess if you already have sketch designs this will give you a better starting point.

Reply on news.ycombinator.com