For example:
challengeSeed: [] is not included in the output and it needs to be. Same for the various language descriptions.

Challenge Type is a numeric, for one of these values:

  common.challengeTypes = {
    HTML: '0',
    JS: '1',  // Waypoint
    VIDEO: '2',
    ZIPLINE: '3',
    BASEJUMP: '4',
    BONFIRE: '5',
    HIKES: '6',
    STEP: '7'
  };

Drop down should display as:
Waypoint (1)
...
Bonfire (5)
...
Step (7)

So you can see the value as well as the common name.

Hints are defined as follows

on the challenge object
{ hints: [ ...String ] }

An array of single line strings.

The default is an empty array

It should ask for saving the changes or cancel before refreshing the page.

When writing the JSON file a newline should always be appended to the final output.

We are changing the seed structure to use a nested file and added a few new properties.

challenges/
|- xx-name-of-challenge-super-block
  |- challenge-block.json

adds superBlock and superOrder properties

Currently on branch feature/hikes, but should be merged in soon.

From @BerkeleyTrue on October 30, 2015 18:51

Copied from original issue: FreeCodeCamp/ChallengeOMatic1003#7

So far I've found that step challenges step index types are transform from Number to String.

Audit COM and freeCodeCamp/freeCodeCamp@f9c2da7 to ensure no other data types are being changed

All fields should consistently display in the same order in the challenge editor.

The unsaved changes modal warning should be given higher z-index.

The releasedOn field will not always be set, but if it is, we should have a nice jQuery date picker.

Output format of the date should be:
MMMM D, YYYY
IE:
January 1, 2016

Field must be blankable.

Not sure if I'm doing something wrong, could be user error. Would appreciate thoughts.
When I go to the main page, seemingly triggered by the e/files express route, i get a list of files in my ~/freecodecamp/challenges. These files cannot be interacted with in any way I can see. Lastly in the DOM order is a 'choose files' button. Clicking this button seems to do nothing, according to screenreader. Nothing else appears to be on the page.
Would like to add some accessibility and general information to some of the challenges, can't do that now since I don't really fancy editing the raw json data. Any comments very much appreciated :)

Various fields are "single line" fields and should display the proper height.

Fields which are limited to a list of values, such as challenge type should display as a drop down. Boolean values should have a true/false or "don't display" value.

Challenge type 7.

These have a unique structure:

description: [
  [
   "Image URL (Required)",
   "Image Description (Required)",
   "Text (Required), One line broken by <br />",
   "Click To Open URL (Optional)"
  ], 
  /* Additional Steps */
]

It seems like a nice interface would have single line for most of these, maybe a multi-line editor for the "text" item (description[2]) that would automatically create <br /> entries.

There would be an "Add New Step" button as well.

Some feature requests

• Toggle Spell check
• Tab key should insert 2 or 4 spaces
• Ctrl + O binding to show open file sidebar

Clicking "Choose File" should rescan the challenge directory.

If a new file has been added and any other file has been removed, then it should re-scan the challenge page to show all latest files.

Current Workaround:-

• Refesh the page

From @SaintPeter on November 24, 2015 21:15

Fix the Choose File/Export/Back menu bar at the top of the screen so it can always be seen/clicked. "Prev/Next" buttons could go here as well.

Copied from original issue: FreeCodeCamp/ChallengeOMatic1003#28

Please add the following code to the CodeMirror init.
CodeMirror.keymap.default.End = "goLineRight"
CodeMirror.keymap.default.Home = "goLineLeft"

This will cause the home and end keys to go to the start/end of the word wrapped line, rather than the absolute end of the line.

From @BerkeleyTrue on November 1, 2015 21:49

Copied from original issue: FreeCodeCamp/ChallengeOMatic1003#12

From @SaintPeter on November 24, 2015 23:5

Need UI buttons at the top of the interface to navigate to the prior or next challenge quickly.

Copied from original issue: FreeCodeCamp/ChallengeOMatic1003#29

From @SaintPeter on November 4, 2015 3:56

If tag does not exist, allow creation.
If tag does exist, allow true/false values.

Copied from original issue: FreeCodeCamp/ChallengeOMatic1003#13

Highlight currently active tab in header so that it's obvious which tab I'm currently in.

npm ERR! fetch failed https://registry.npmjs.org/lodash-es/-/lodash-es-4.6.0.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404

That error comes up a couple times and then it exits.

If I try to run npm run build it then says that it can't find webpack

From @SaintPeter on November 24, 2015 18:46

Since we're able to write to the local file system, it would be nice to be able to read from it as well.

If we load a local file, we should then be able to "reload" the file, so we can quickly pick up changes we've made by directly editing the JSON.

Low Priority.

Copied from original issue: FreeCodeCamp/ChallengeOMatic1003#26

From @BerkeleyTrue on November 1, 2015 21:47

Copied from original issue: FreeCodeCamp/ChallengeOMatic1003#11

Currently, the header has to be scrolled every time switching to different meta data.
It would be nice to fix it at the top.

Press CTRL+S key to save challenge.

I took a deeper look into this error message:

$ npm test

> [email protected] test d:\mean\COM1000
> node node_modules/.bin/babel-tape-runner tests/**/*.js | faucet

d:\mean\COM1000\node_modules\.bin\babel-tape-runner:4
case `uname` in
^^^^

SyntaxError: Unexpected token case
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:414:25)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:136:18)
    at node.js:963:3
 not ok 1 no plan found
not ok 2 no assertions found
⨯ fail  2
npm ERR! Test failed.  See above for more details.

And realized that the command is trying to run a shell script with node. . . 😄

The correct command, I think, is:
node_modules/.bin/babel-tape-runner tests/**/*.js | node node_modules/faucet, but I don't get any output.

Running without faucet gives me:

$ node_modules/.bin/babel-tape-runner tests/**/*.js
TAP version 13
# #reducer.spec
# Test 1 should return a default state if none is provided
ok 1 should be equivalent
# Test 2 should return a new state upon a valid action type
ok 2 should not be equal
# Test 3 should return previous state on invalid action
ok 3 should be equivalent
# #tape.spec
# Test 1 should fail
# Assertion passes
ok 4 should be equal
# Assertion fails
not ok 5 should not be equal
  ---
    operator: notEqual
    expected: undefined
    actual:   5
  ...

1..5
# tests 5
# pass  4
# fail  1

From @SaintPeter on November 24, 2015 23:11

Call it what it is. "Challenge-O-Matic" in the title.

Copied from original issue: FreeCodeCamp/ChallengeOMatic1003#30

Would it be possible to change the highlighting format type based on a user selected option? Like a radio button?

challenges now have a property

{ "translations": Object }

It's keys are IETF language tags. for example...

  "translation": {
    "es": {
      "title": "Challenge TItle",
      "description": [ "line 1" ]
    },
   "pt-PR": ...

The old method of having challenges at the top level will be removed

Fields should be grouped together under tabs to make it easy to edit sections of content and reduce unnecessary scrolling.

First Pass on Grouping:

• Display
  • title (with Language Selector)
  • description (with Language Selector)
• Code
  • head
  • challengeSeed
  • tail
  • tests
• Solutions
  • solution 1
• Settings
  • isBeta (boolean)
  • updatedOn (Date Picker)
  • challengeType (Dropdown)
  • type (is this even used?)

I'm totally flexible on this grouping, this is just a straw dog.

Assume a "Half Screen Display" until we have live preview. This should be intended to display in a single column, ~1000px wide.