Hi @zorbash . Thanks for getting Kitto going, I think it is a really good initiative. While I usually don’t love the “it’s this project rewritten in this technology”, I think Kitto could be a nice exception 
Especially if you have plans to make it diverge from Dashing/Smashing and make it more uniquely Elixir-fied.
I did have a question about the data returned from a block job.
For example, there is the text widget:
import React from 'react';
import Widget from '../../assets/javascripts/widget';
import './text.scss';
Widget.mount(class Text extends Widget {
render() {
return (
<div className={this.props.className}>
<h1 className="title">{this.props.title}</h1>
<h3>{this.state.text || this.props.text}</h3>
<p className="more-info">{this.props.moreinfo}</p>
</div>
);
}
});
This seems to imply that the only dynamic text I can put in my text widget is the <h3> text with this.state.text . Am I reading that correctly?
Since text is a core, built-in widget, would it be more useful if there was less hard-coded text and more dynamic text? Or is the intention for users to always extend the widgets and the ones in the kitto.new are just examples?
Thanks again
)
