Landing Page

[jrf0110]

There should be a splash page associated to each lunchroom/company. Since we're only launching at BazaarVoice initially, users should be able to visit https://lunchroom.goodybag.com/bazaarvoice to see the splash page. Initially, requests to / will be redirected to /bazaarvoice.

TODO

• [x] Implement lunchroom-specific splash page markup
• [x] Hook up signup form to user/lunchroom/menus updates
• [x] Skin the splash page with pretty CSS - John

For now, everything on this page will be static, aside from entering the user email data. Error/Success states will need to be put in there, but don't worry too much about making it super rigorous.

$feature https://github.com/goodybag/lunchroom/issues/1

[cadorn]

Sorry I did not get this up on friday as promised. I have a meeting today (Monday) at noon, other than that I hope to get the skin and install work finished today so you can focus on the skin and I can focus on payment and polish.

[cadorn]

The splash page now loads on the staging server and redirects as needed: http://lunchroom-stage.goodybag.com:8091/

The landing page css loads dynamically from github from https://github.com/goodybag/lunchroom-style/blob/clobber/landing.style.css

Now on to local install and continuous delivery via push to github branch.

Then tomorrow I'll hookup the newsletter and payment form.

[cadorn]

I cannot access this dependency of this project: https://github.com/goodybag/font-avenir

[cadorn]

The subscription is working: http://lunchroom-stage.goodybag.com:8091/

So once I get access to the dependency above I can port the landing page and ready the app for production deployment over the weekend ready for monday.

I then need to complete the menu/day management (1 day) and payment (1 day). And the we should review and tweak (1 to 2 days).

Lets discuss the skin over skype so we can figure out how to best do it.

I hope me being late on completion is not causing problems. I am confident we can polish things next week and have a solid backend you can experiment with in a very flexible way. I added a lot of pieces covering most use-cases at least once and it is now trivial to add new functionality and complexity if you follow the init flow of the backend and app which I will still document better and show you.

Launching the landing page and collecting subscribers starting monday is a good idea.

P.S. There is still work left to do on the system after I complete the project as I am hoping to refactor things a bit more and clean things up as I evolve some of the libraries and integrate an advanced security and logging system. This will then make you 100% compatible with the Cloud9 plugin and future of the tooling and provide complete decoupling on client side and backend to build your entire architecture and business logic out of components. I am hoping you are open to me staying involved for a few months to tweak and monitor what I have done and ensure it is all working well for you.

[jrf0110]

I've setup the avenir repo to allow access from the Lunchroom team. However, this will be problematic for wherever we deploy (unless we add ssh keys to access github - probably don't want to do that).

Lets discuss the skin over skype so we can figure out how to best do it.

I'm pretttty busy this weekend, maybe we can do that on Sunday or Monday?

I hope me being late on completion is not causing problems.

Well, we've had to continually push back the launch date. It's not necessarily causing problems, it's just a little frustrating. I feel like there should have been more diligence in balancing beauty and architecture with deadlines, but I'm excited to see how the codebase scales (in terms of both performance and feature).

I am hoping you are open to me staying involved for a few months to tweak and monitor what I have done and ensure it is all working well for you.

I'm sure this will be necessity, actually. There's a lot of non-idiomatic code in here related to your tooling. I'm not discounting the merits of your tooling or code. It will just be a lot of mental investment on our parts just to get hacking.

Anyhow, I understand, though, that the work you're doing is quality, and we appreciate that. We're going to make a killer product here. Just remember; this is an experiment. The code can be a little rough around the edges :)

[cadorn]

I've setup the avenir repo to allow access from the Lunchroom team. However, this will be problematic for wherever we deploy

It is only needed for dev and I will publish the assets for the landing page separately.

I'm pretttty busy this weekend, maybe we can do that on Sunday or Monday?

Let's do it Monday.

It's not necessarily causing problems, it's just a little frustrating. I feel like there should have been more diligence in balancing beauty and architecture with deadlines.

I want you to know that I have been very cognizant of the deadline and attempted to balance these aspects as best as I could with a future-proof approach. I could have been more diligent in communicating some challenges and taken some short-cuts and could have ensured that we were pulling in the complete skin from a separate project without building a semantic UI version first.

There's a lot of non-idiomatic code in here related to your tooling. It will just be a lot of mental investment on our parts just to get hacking.

There are some tooling-based conventions and there are some component-based and reactive architecture conventions and the whole thing is organized into a development system that always works and you break with feedback in containerized layers when you introduce bugs.

Most of the mental investment needs to go into understanding how the layers fit together which I will expose on a request basis using a powerful internal logging tool that can jump to the code screenshot from 5 year old tool that did some of it and I will have working within Cloud9 and own open source component. Then its a matter of adding to what is there. There should be no need to design something new as the foundational architecture is setup to handle any HTTP/Websockt call in a generic way. You simply hack and reload (if it does not auto-reload for you) and see your result.

Anyhow, I understand, though, that the work you're doing is quality, and we appreciate that. We're going to make a killer product here. Just remember; this is an experiment. The code can be a little rough around the edges :)

I appreciate that. I know you are on to something with the lunchroom and I have tried with what I have built to provide you with a transactional framework you can scale to any consumer group and event. I know Jay will not stop refining his approach until he finds the right formula and the system I have put in place can be adjusted until it fits and then scale with little effort. I venture to bet I can port most of your catering server to the lunchroom architecture within a couple of months after the cloud9 plugin is working and you would be completely detangled and ready for anything new.

Just as the lunchroom is an experiment for you, this is a proof for me to see how my approach and tooling works out in practice after the last cycle of refinement. I will pick up the slack where the tooling and docs are lacking until you and your team are comfortable with what I believe is the cutting edge of open source component-based software system development.

I am confident we will work out the rough edges over the next couple of months. By then you will have proven the lunchroom concept and will be ready to scale. Perfect timing :)

[cadorn]

Landing page is done: http://lunchroom-stage.goodybag.com:8091/

Will still tweak CSS for contact/terms/privacy for Monday and put on live domain.