Need To
1. Developed in Sinatra for a Heroku deployment.
2. I prefer using DataMapper due to my own knowledge in it but if you recommend or would like to use another ORM, just let me know what and why and it should be fine.
3. The data saved needs to support categories, sub-categories (just the one level, not unlimited levels) and items. If you can code it in a way that it can be reduced to to items, categories (which may or may not have a parent category) and items, that is ideal but not required.
- Categories: Top level object, needs only id and name fields.
- Sub-categories: Needs an id, name and parent_category object
- Items: Items belong to a sub-category (never a main category and never without a category). They will have about 10 fields to start and may have additional fields add later. You don't need to do anything about possible later additions but keep that in mind when coding.
4. Admin: HTTP auth is fine. I should be able to sign in, view a list of categories, sub-categories and items, created, edit and delete each of them. No design or CSS is needed, just bare interfaces that I can then go in and style.
5. Response: The response will be in JSON unless a callback parameter is specified in which case the response should be in JSONP.
6. Endpoints: Here are some actions you should be able to request with a GET request.
- List of all categories
- List of all sub-categories
- List of sub-categories of a specific category ID
- List of all items
- List of all items belonging to a specific sub-category ID
- Get a single item by ID
Thanks for taking the time to take a look, if you have any questions or suggestions to improve the project, I'd love to hear them.
Cheers,
Anders
1. Developed in Sinatra for a Heroku deployment.
2. I prefer using DataMapper due to my own knowledge in it but if you recommend or would like to use another ORM, just let me know what and why and it should be fine.
3. The data saved needs to support categories, sub-categories (just the one level, not unlimited levels) and items. If you can code it in a way that it can be reduced to to items, categories (which may or may not have a parent category) and items, that is ideal but not required.
- Categories: Top level object, needs only id and name fields.
- Sub-categories: Needs an id, name and parent_category object
- Items: Items belong to a sub-category (never a main category and never without a category). They will have about 10 fields to start and may have additional fields add later. You don't need to do anything about possible later additions but keep that in mind when coding.
4. Admin: HTTP auth is fine. I should be able to sign in, view a list of categories, sub-categories and items, created, edit and delete each of them. No design or CSS is needed, just bare interfaces that I can then go in and style.
5. Response: The response will be in JSON unless a callback parameter is specified in which case the response should be in JSONP.
6. Endpoints: Here are some actions you should be able to request with a GET request.
- List of all categories
- List of all sub-categories
- List of sub-categories of a specific category ID
- List of all items
- List of all items belonging to a specific sub-category ID
- Get a single item by ID
Thanks for taking the time to take a look, if you have any questions or suggestions to improve the project, I'd love to hear them.
Cheers,
Anders
Earn : Fair Suggestion | Project Deadline: Please Estimate
Posted in: Freelance Work,Projects for Freelancers,Web development
