jedireza

Even better C3.js + react-c3js

http://c3js.org/examples.html

https://github.com/bcbcarl/react-c3js

A website and user system starter. Server side is built with hapi.js. The front-end is built with React. Redux as the state container. Client side routing with React Router.

https://jedireza.github.io/aqua/

https://github.com/jedireza/aqua

Yeah, I'm getting Cantarell rendering on Gnome, it's no San Francisco.

I love the hiding feature, thank you. I did noticed I can't hide YC company "hiring" posts.

Ex: "GitLab is hiring a security engineer (gitlab.com)"

Thanks! I'd like to dismiss and/or mark as read for stories I'm not interested in.

Some personal projects:

- https://github.com/jedireza/drywall - https://github.com/jedireza/frame - https://github.com/jedireza/aqua

I actually think it's a good to understand Flux in it's purest sense before using a framework. As a learning experiment I created Aqua [https://github.com/jedireza/aqua]. It was published last week and there's a good Q&A thread going on [https://github.com/jedireza/aqua/issues/2].

It's a starter/boilerplate.

Yes. It's more like a few single page apps. The account and admin areas feel much faster.

Thanks for sharing that. I jumped the gun before commenting.

I'm curious why NeDB wouldn't suffice.

https://github.com/louischatriot/nedb

I've iterated twice on these kinds of projects. First was Drywall and the latest is Frame. Drywall includes a front-end and Frame is just an API. Finding a happy medium of features is tricky. Some choices limit your audience quite a bit.

Drywall [https://github.com/jedireza/drywall] Drywall is limited to people who're ok using Grunt instead of Gulp or Backbone instead of _______, etc...

Frame [https://github.com/jedireza/frame] I created Frame to appeal to a larger audience. And because all the front-end opinions were removed it plays nicer since you "bring your own front-end". Interestingly enough, now I'd like to provide Postgres as well as Mongo db connections.

In general these projects are interesting and I think serve best as examples of apps beyond the absolute basics. Once you make an app yours, it'll probably go in it's own direction quickly.

Hey HN. Developer here.

This is the second iteration of creating a user system boilerplate/kit. The first was Drywall which you can find on my GitHub page. I'd love to know what you like and what sucks.

I find it interesting that there is little to no conversation about the integration with git. In one of the the screenshots I saw a branch name and icon in the bottom status bar. I assume this is an important motivation for GitHub.

Wow. nodestreams.com is great. It's really helpful to see the results of different chained combinations instantly. Thanks for making this John.

This is exactly what Drywall was designed for. It's a website and user system for Node.js

Feedback is welcomed.

http://jedireza.github.io/drywall/

Edit: more so for a functional side project, not a static website.

Drywall - A website and user system for Node.js http://jedireza.github.io/drywall/

Recent cool news: got word from the hosts of Node Knockout that submissions are allowed to use it in the competition.

Thanks for your open source contribution, it's been a big help.

I'm happy to hear this. It was nice of Bjørn to build the node API in the first place. It's great that this became the official API, congrats all around.

Hey Jason, thanks for taking a look. Right now it's just an open source project of mine, not a business or anything. If something isn't clear after reading the GitHub page, please open an issue or send me an email. I've started breaking out wiki pages from questions I've received. My main focus right now is getting more eyes on the project and gathering feedback.

This is the same stack that Drywall is built with. When you're ready to get past a simple hello world app, please take some time to checkout the project.

http://jedireza.github.io/drywall/

Since I've built user/admin systems for the majority of my career, this is really interesting to me. The site looks great and the Family Guy stuff is funny ("No,n0_p4ssword!") Hah.

I agree with the lion share of what WA said.

The MVP/prototype argument is a valid one, but remembering that nothing lasts forever, it's probably wise to think of these services as temporary tools and not permanent solutions.

I believe that user management is such an important (and basic) thing, that you should own it. For the hackers out there, feel free to checkout my Drywall project, which is a website user system build for node. https://news.ycombinator.com/item?id=4951605

So Dan Grossman was nice enough to correct me on this. http://www.networksolutions.com/blog/2011/10/network-solutio...

The source of my information was an email I got this morning from Network Solutions saying they are now a Web.com company. Must just be a excuse to market to customers.