Need a Landing Page

[farmbot]

Need a Landing Page

[ghislaineguerin]

Hi Rick,

I have some questions:

where do I add design elements for the dashboard
where do I add this landing page...
what's the repo I should be working on..

On Thu, Apr 10, 2014 at 9:35 AM, Rick Carlino [email protected]:

Everything is done with user management. Now we need a landing page that
allows users to:

• Log in
• Register
• Retrieve lost passwords
• Get an overview of the project

Let me know if you need any help, @ghislaineguerinhttps://github.com/ghislaineguerinotherwise I will get out of your way.

Reply to this email directly or view it on GitHubhttps://github.com//issues/32
.

[roryaronson]

Hi Ghislaine,

You can work out of the farmbot-farm-designer repo. That will be the place for the whole frontend: the dashboard, landing page, everything the user sees.

[RickCarlino]

Yes, that's right. I guess now that it is seperate I can just take @ghislaineguerin 's work and slice it into the Rails app afterwards. Going to leave this one open until I do that though.

[ghislaineguerin]

@RickCarlino @roryaronson I'm starting to work on this. What content do we have for this landing page ?

[ghislaineguerin]

I thought farm designer was going to be the repo for the farm designer
functionality. The view where you can plan the farm layout.

On Thu, Apr 10, 2014 at 1:47 PM, Rory Aronson [email protected]:

Hi Ghislaine,

You can work out of the farmbot-farm-designer repo. That will be the place
for the whole frontend: the dashboard, landing page, everything the user
sees.

Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-40115700
.

[roryaronson]

I already said this to Ghislaine in chat, but for the record here, this is what I think is going on:

This repo (farmbot-web-backend) is the backend. There will be no frontend elements in here.

The farmbot-farm-designer repo is the frontend. That has all of the "pages" that the user will see on their screen and interact with: The farm designer, any landing pages, any signup pages, settings pages, etc. You know, HTML and CSS stuff + assets.

The frontend will communicate and be closely integrated with the backend of course, So when a user does something in the frontend, like creates an account or moves some plants around in the designer, the data is saved in the backend.

The reason for having two repos is to allow new contributors to more easily jump into the project where they are comfortable. We stared with everything in one repo (the backend, frontend, and DSS) but that is just too many components for one repo, especially because folks usually contribute to only one based on their specialty.

Hopefully this clears things up. If splitting these two is a bad idea, we can always go back to one

[ghislaineguerin]

@roryaronson @RickCarlino should I then install foundation on that other repo?

[m3talsmith]

@roryaronson are you using backbone or angularjs for the front end then and communicating over ajax?

[roryaronson]

@m3talsmith I think Rick will let you know the answer to that one :)

[RickCarlino]

@m3talsmith Yeah, that's the plan. It will be mostly an SPA. WebSockets for the Skynet part, ofcourse, but otherwise just AJAX on a heavy frontend.

[m3talsmith]

I'm right now adding CoAP support into Skynet. That will give you a lightweight Restful way of communicating with Skynet as well. Also, big news, we're busy writing in some new security measures and permissions into the network that will make it super easy for FarmBot users to group their bots together for themselves and to share which ever ones you want with a broader group of people, giving you some granular control over access and API features.