Overview Create a web site using Django for nutrition information for people with kidney disease. The web site will mainly be a way to browse recipes and articles. 1. Browse recipes: By label: "low sodium", "low phosphorous", "low cholesterol" By condition: "diabetes", "CKD stage 3-5", "hypocalcitemia" (each condition would just be a set of labels) 2. Browse articles: By category (maybe 3-6 categories) Navigation: - A smaller, top menu with "About Us", "Contact Us" - A footer menu, with "Disclaimer", "Contact Us" - A tabbed menu bar that looks like the following: MENU: /--------\ /---------\ /----------\ | Home | | Recipes | | Articles | |-------------- ----------------------- | Filter By: | O Low Sodium O Low Phosphorous O Low cholesterol | O High phosphorous O Low potassium O High Potassium | | By condition or therapy: | O Diabetes O CKD Stage 3-5 O Hypocalcitemia ... -------------------------------------------------------------- /--------\ /---------\ /----------\ | Home | | Recipes | | Articles | |----------------------------- ---------------------- | Eating Well Staying Fit -------------------------------------------------------------- - The section that a user is on at any given time should be in bold. There should be a big photo of Tiffany, the nutritionist, in the top right. The web site should be called "[login to view URL]"
## Deliverables
IMPLEMENTATION:
Requirements:
1. The site should be built on Django, a python-based web framework (or another open-source web application framework that you like better, we're open to that, too)
2. All HTML sent to a browser longer than a line should be in a template (header, footer, everything)
3. This web site must function with all features in Internet Explorer 6+ and Mozilla Firefox's latest version.
4. The tabbed menu on the site should be built using a well-known javascript tab infrastructure.
The administration of this site is mainly managing the general content, articles, and recipes.
Articles, we would like to be just part of the general content.
RECIPES:
There is *not* a requirement to manage foods associated with a recipe as foods, although eventually, we're looking to move toward that. For now, we're thinking of recipes as:
----------------- --------------
| RECIPES | | LABELS |
----------------- --------------
| name | | name |
| ingredients | | |
| instructions | | |
----------------- --------------
| |
-----------------
| recipe_labels |
-----------------
Please note that recipes can have multiple labels.
Administration:
Manage Recipes
Add or edit a recipe
Manage which labels are associated with the recipe. (add, remove)
Manage Labels
- Add a label
- Edit a label
- Delete a label if and only if there are no recipes associated with it.
The design should be signed off on, before moving onto the implementation.
The final design files will be
(a) homepage
(b) Recipe search results page
(c) individual recipe page
(d) Article category page
(e) individual article page
The final project deliverable will be the sourcefiles to be installed on another web server.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
## Platform
Linux, apache, Django, mysql (or postgres)