Viktor Shevchenko
Web developer from Kyiv
<html>
<head>
<!-- Scripts and styles-->
</head>
<body>
<!-- Page Content-->
</body>
</html>
<html>
<head>
<!-- Scripts and styles-->
</head>
<body>
<!-- Page Content-->
</body>
</html>
<html>
<head>
<!-- Scripts and styles-->
</head>
<body>
<!-- Page Content-->
</body>
</html>
ui/page1
ui/page2
ui/page3
<html>
<head>
<!-- Global Styles-->
<!-- App Styles-->
</head>
<body>
<!-- Framework scripts-->
<!-- Vendor scripts-->
<!-- App scripts-->
</body>
</html>
<html>
<head>
<!-- Global Styles-->
<!-- App Styles-->
</head>
<body>
<!-- Framework scripts-->
<!-- Vendor scripts-->
<!-- App scripts-->
</body>
</html>
modern-ui/page1
modern-ui/page2
var HelloMessage = React.createClass({
render: function() {
return <div>Hello {this.props.name}</div>;
}
});
ReactDOM.render(<HelloMessage name="John" />, mountNode);
We propose to select a stack based on React.js library
React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
React abstracts away the DOM from you, giving a simpler programming model and better performance
React implements one-way reactive data flow which reduces boilerplate and is easier to reason about than traditional data binding
Pros
Cons
Aspects
Redux
React
Babel
TypeScript
WebPack
You will say... we already have one.
Viktor
Dmytro
Vladlen
By Viktor Shevchenko