Smart JSON Editor with Autocomplete + CMS (using Ace editor)

Notes: - Expert javascript developer is required - Developer needs familiarity with **Ace editor** (if you believe there is a better technical solution than Ace, let me know) - Familiarity with React.js is needed for integration with CMS system (Milestone 2). Schedule: Each Milestone must be completed in 7 days (plus 3 days for minor bug fixes and clarifications). That's a total of 30 days for entire project. Failure to meet the schedule may result in project cancellation and negative feedback rating. Milestone 1 (35% of total payment): In this first phase, the goal is to create a very smart json editor, with 2 main features: 1. Overriding the way TAB key normally works within Ace editor 2. Autocompletion and validation based on a JSON "schema" or "class" Milestone 2 (35% of total payment): 3. Integrate Editor into CMS UI, save objects using PouchDB 4. Meta-class schema: autocompletion and validation when you create a new class Milestone 3 (30% of total payment): 5. Add new fields types, implement new ref type, implement custom fields type editors **The most important functionality of Milestone 1 is described below. Please read "JSON Editor + CMS Full Specification" PDF document** ##1. TAB key behavior TAB key works completely different than in other editors, it **does not** insert a tab or spaces! TAB selects/highlights the next token. SHIFT-TAB selects previous token. A token means the next value OR key in an object, or the next value in an array. This should work with nested objects and array. Here's an example: { "car": "Toyota Camry", "options": { "colors": ["red", "black", "silver"] } } In this case starting at "car", pressing tab will select tokens in this sequence: "car" -> "Toyota Camry" -> "options" -> "red" -> "black" -> "silver" **SHIFT-TAB works the same but in reverse order.** ##2. Autocompletion + validation based on a JSON class schema Autocompletion is based on a few rules: - Autocomplete keys based on "fields" in schema - Once a key is already exists in object, we don't offer it as a suggestion anymore. - Autocomplete "select" type based on list in "options" attribute. - "array" type should also support "options" attribute and work similarly. - Autocomplete list should be shown whenever there is an empty key or value, or when a key or value is selected (i.e. when you double click on it). Here's an example schema: { name: "Post", fields: { title: { type: "string", required: true }, category: { type: "select", options: ["main", "news", "business", "tech"] }, state: { type: "object", fields: { authors: {type: "array"}, visibility: { type: "select", options: ["draft", "published", "archived"] } } } } }