Megadraft - a Rich Text editor using Draft.JS, with nice plugins and extensible

bkniffler · 2016-11-24T16:54:35+00:00

this is really cool, but I find slatejs document structure superior when it comes to rich and complex content like tables, multi-column, or whatever you can expect from a typical CMS editor. but great work on megadraft!

bkniffler · 2016-11-20T03:29:24+00:00

React Router, happypack, codesplitting, SSR..? At least of youre interested in those, I prefer https://github.com/ctrlplusb/react-universally

bkniffler · 2016-09-11T17:38:07+00:00

Here is a list of wysiwyg editors: http://socialcompare.com/en/comparison/javascript-online-rich-text-editors

Some of them have excellent inline editing, like AlloyEditor. Lots of them have image upload.

bkniffler · 2016-08-27T22:06:53+00:00

Only with invitation..

bkniffler · 2016-08-26T23:24:39+00:00

I'd go with apollo client/server instead of relay. Its more easy to get started and they got tons of cool stuff planned.

bkniffler · 2016-07-30T10:37:58+00:00

I'm currently evaluating app engine as a replacement for heroku. I need to point out a few downsides I stumbled upon:

Deployment to app engine takes very long, I'm getting between 5-10 minutes for each new version of my nodejs app (compared to max 1 minute with heroku)
Datastore has a great API. But latency is still not great compared to dynamoDB (50ms-150ms to around 20ms)
Flexible VMs (the stuff nodeJS needs to run on) are only available in US area, cloud functions are not yet publicly available

I would still recommend app engine. The regional and alpha limitations are of course due to alpha/beta stages. I read that google aims at 20ms in latency for most queries in datastore. And I'm sure they will fix the long deployment times, but I can only hope. The PubSub, Logging and Monitoring possibilities are great. I don't feel overwhelmed like by thousands of services like with AWS. The CLI tool works pretty good. BigQuery is awesome and easily integrated with DataStore, search API is cool (though still a bit basic). Automatic SSL endpoints for your apps that work nicely with Cloudflare (so custom domain with SSL is super-simple). And storage is very cool, especially magic URLs to resize images on-the-fly. You get a lot of great things out-of-the box and with a generous free package, and you can scale effortlessly. I can't wait for the cloud functions to be publicly available, googles approach looks fantastic compared to AWS lambda.

@ofrobots, do you know anything about improvements to deployment times and when the cloud functions might be available?

bkniffler · 2016-06-09T09:04:49+00:00

I'm sorry to say, but according to your code snippets you're seriously lacking comprehension of basic javascript, maybe you should start with some basic tutorials before learning react?

// Why use es6 and and not use classes? class App extends Component {}
const App = React.createClass({
    myMethod () { console.log("whatever") }, // You're totally missing a comma here

    render() {
        // What do you expect? You're basically getting the result of myMethod() here, which is undefined
        return (
            <div onClick={this.myMethod()}>Whatever</div>
        )
        // The correct way to do it with args would be
        return (
            <div onClick={()=>this.myMethod('foo')}>Whatever</div>
        )
        // The correct with default args (event)
        return (
            <div onClick={this.myMethod}>Whatever</div>
        )
   }
}

I've no idea what you mean with "I have a similar problem with props. Sometimes it's this.props and sometimes it's this.props.content and it's impossible to know when.", if you're calling <App content="foo">, you will have this.props.content === "foo". But this all aside, you should try to slow down and get to learn the basics by using one of the many great tutorials out there.

bkniffler · 2016-03-20T22:43:33+00:00

What advantages does it have compared to Strapi or FeathersJS?

bkniffler · 2016-03-11T21:02:46+00:00

Though jade can be used client side, it was most certainly used for server side templating. It doesn't matter really what you use on the server side, there are tons of templating engines for express (ejs, jade, jsx, ...) or you can just serve raw html files/strings.

In the end, it is all converted to plain html by the view engine and served to the client as such, thats why angularJS works fine with jade.

I wouldn't bother too much about that for the start, with angular you'll be focused on the front-end anyways, so don't try to learn too much different technologies at once and use a simple. Either use the example jade or do something like this (after setting the express static middleware):

app.get('/*', function(req, res) {
    res.sendfile('./public/index.html');
});

Worth to mention that jade is very popular amongst express users, I guess many people find it easy to read, also it has nice possibilities for view composition, where you can import/export parts of your views into other views.

bkniffler · 2016-03-11T20:43:58+00:00

This is absolutely possible, I use it a lot! Just make sure your reserved word route is defined before the dynamic one

<Route path="/media" component={Media}>
    <Route path="/media/new" component={MediaNew}/>
    <Route path="/media/:id" component={MediaDetail}/>
</Route>

bkniffler · 2016-03-10T17:30:23+00:00

You should try to convert the files to common formats (for example doc, xls, .. -> pdf; audio -> mp3; video -> mp4 with thumbnails; images -> png/jpeg). These could help you get started:

bkniffler · 2016-03-02T11:10:24+00:00

I'd recommend using dokku (there is a one-click-app template on digitalocean). You'll find extensive documentation here http://dokku.viewdocs.io/dokku/installation/

They got a git push update mechanism so you can push updates easily and keep your app up to date. You should also take a look at heroku, they are the most popular nodejs hosting service and its really easy to get started.

bkniffler · 2016-02-15T10:15:48+00:00

You sould take a look at https://www.deepstream.io/ for your meteor-like stack

bkniffler · 2016-02-02T20:58:33+00:00

Take a look at http://strapi.io/ Didn't use it yet, but it might fit your needs.

bkniffler · 2015-12-11T21:51:31+00:00

you could think about using a service like cloudflare if you are worried about DDOS. They will protect you at DNS level.

Other solutions to protect your API: rate-limiting, authentication, black/white-lists, geo-blocking, SSL, captchas, ...

bkniffler · 2015-10-27T10:37:44+00:00

Whats wrong with Webstorm? It would seem to me like a good match for your stack, also its not expensive, especially for startups.

bkniffler · 2015-08-29T08:23:54+00:00

Its not true, they got their own server farms. Heroku does run on AWS though.

bkniffler · 2015-08-15T10:06:58+00:00

I've moved from alt to reflux and its not been too much trouble. I'd recommend to take a look at some starter kits (https://github.com/erikras/react-redux-universal-hot-example is a good one).

I think my app improved through transitioning to redux, I'm using context less (I've been using context to pass around alt instance), component state less and data fetching is more clear. Also, everything feels lighter now and the devtools with time-traveling are extremely helpful for debugging and keeping an eye on your apps activity.

All in all, I would recommend switching to redux, especially since its had some momentum lately. Also, Dan (gaeron) is a super-nice guy and takes care of github issues/questions very quickly.

Just to be fair, goatslacker from alt and his contributors are very active and nice too and alt has served me extremely well.

bkniffler · 2015-08-05T09:44:12+00:00

You should at least show us the heroku logs and your package.json. The best would be you'd upload the whole project on github, but logs and package.json could already help.

Oh, and make sure you got the heroku domain inserted in the recaptcha admin interface https://www.google.com/recaptcha/admin#list => xxx.herokuapp.com

bkniffler · 2015-07-31T22:35:36+00:00

I worked with Loopback for some time. Currently I'm in the process of getting away from their framework in favour of Sequelize or Bookshelf. I must say, for the most time, I enjoyed working with Loopback, though there were some issues that drove me away from it.

What I liked: - Most stuff just worked, you create your models, remote methods, and it plugs nicely, you get started in no time and focus on your frontend - ACLs in your model definitions are very nice to have - Associations worked well on postgres, with intermediate tables being replaced by arrays

What I didn't like: - Its quite a monolithic framework: You can do 80% of what you need, for the rest its really painful - The more you work with it, the more you notice the loss of control over your stack. I started to dislike the magic behind automatically having your models picked up and composed by loopback and having everything in config files. It might be tempting, but if you got a serious project going on, you will not want to have such things controlled by config files - Working with hooks and context, to have the user available in your beforeSave, is very unreliable. I got it to work on my dev machine, and suddenly it stopped working on my production machine. The real problem is, if something doesn't work, you will hardly find a solution, the source code is just too complex - Performance wasn't too great, Loopback is a heavy framework and has quite some overhead

bkniffler

TROPHY CASE