You can load the bootstrap blog theme to see this happen

No need for everything to turn red when saving a form.

I'm looking at you Horn.

Something is trying to access firebase before we're ready during login.

highlight()

And it's because of the wh-tray-wide class: https://github.com/webhook/webhook-cms/blob/master/app/controllers/wh/content/start.js#L100

@snide you might know what's going on there.

Reminder, no need for this immediately.

Already dreading this in documentation I'm writing. Best to lock a user out when they try to edit a doc that is currently being edited by someone else.

cc @LtSquigs

Currently, the formbuilder creates fields names like item.some_field. The content type itself though goes from "Video Games" to "videogames". This should be uniform. I don't really care which way we go, it just needs to be consistant, since this is ultimately what the template writers will be writing all day.

Allow other users to see the form. Hide controls behind toggle. User must acknowledge intent.

Adding a file (in this case audio) from a URL breaks.

• Save as a single object, not a list.
• Do not send a signal to rebuild.
• Menu item goes directly to form.

Link should be active.

You should be able to upload an image and add it to markdown. Would exist the same way as redactor.

Initial version could just add the tag into the text field.

Later version should allow positioning similiar to redactor. This would be done in the preview side of the document with the same exact controls.

Defering insert animations on widgets until after form loads first time

Delete Field - remove data.
Change Field - update data.

One-offs only have one save option. The message shouldn't say Saved as Draft. It Should be the green one, Saved, viewable live.

If you save without first flipping out of html view, any edits you made in html view are not saved.

http://snid.es/image/370B2h0F2C17

Currently, when uploading a gallery of images, the button will just hang if you picked a lot of images. Should prolly put a spinner in the button immediately to let the user know something is going on any they should just wait.

http://wyrmtest.readthedocs.org/en/latest/forms.html

Format to use on the above page.

3 states:

• Save as draft
• Publish in future.
• Is live already, save for changes or change state.

Apply .on to .wh-server-down when the websocket is lost in the CMS. This should only happen locally.

If you use a URL, instead of a desktop file, the button state changes to be just a spinner. Looks weird, should probably add text that says fetching or some such.

http://snid.es/image/0K3y352a0R3O

You need that trailing p tag at all times to click into around figures and other elements.

http://snid.es/image/2n2a1O25222G

The value is there, because it's sorting correctly on the frontend.

If you go into an existing article, move an image around or resize it, then hit save. The content is not saved. You have to actually add some text first.

Reminders

1. If control-group is selected already, remove the the selection class (wy-control-group-edit) as soon as you begin dragging.
2. Apply class to control group after placement (wy-control-group-placed) and then remove it after 1/2 sec.
3. When placing a new widget, if you then delete that widget on the left nav, it doesn't properly revert to the add widgets panel.

Keep content data and contentType information in sync on the list page.

Just some spec notes for the form builder.

1. There are three form types. This is selected when creating a form.
   • Editorial (comes with date/time publishing).
   • Objects of a set (comics, games...etc)
   • Single object (About us page, twitter widget that requires some editable fields.)
2. Every form requires the following.
   • Object name (articles, videos, comics, games, twitter widget)
   • Title
   • Slug overwrite.
3. List page in CMS is built by doing the following
   • Show title
   • If image widget is included in form, show image.
   • If form type = editorial, include publish date info.

Form creator should both save and be able to load a JSON file with the particulars of the form, thereby making them reusable. We can then load preset git repos oh wh create that include both the templates and the CMS configs for common site patterns (aka youtube site, podcast site, instructional site...etc).

Every form field should have the following

1. Label text.
2. Help text (optional).
3. Is required?
4. Placeholder text.

http://wyrmtest.readthedocs.org/en/latest/forms.html

Format to use on the above page.

3 states:

• Save as draft
• Publish in future.
• Is live already, save for changes or change state.

• After editing an exisiting movie, creating a new movie form populates with data from the edit.
• If you create a new movie, the gets corrupted when the list auto updates with the data. If you're just looking at your own screen it looks like it doubles the content.
• Hook up the sort and column "display view" on the list page. We should probably just default to the first three fields if no display view was set.
• Wire up confirm / warning alerts on actions. http://wyrmtest.readthedocs.org/en/latest/alerts.html#alert-trays
• On deletes, let's give them time to undo the delete rather than doing the normal "are you sure" question.
• Sort order current puts newest objects last. Should prolly be the reverse for the default.
• If fields are left empty, the row doesn't build properly in the list. http://snid.es/image/0W3D461s223k
• The formbuilder will show data from items of that form-type http://snid.es/image/3N2L0b0A2n0C

Hey, can you pass me an extra wrapping div in the widgets on the right side of the form builder called wy-control-group-disabled. It should be inside wy-control-group-edit.

I think I can use a z-index, transparent element to disable the forms that way.

If your content type is named item data gets saved in the wrong space.

We should also try other javascript reserved words and such to see if that also fucks it up.

When hasMany polymorphic relationships are supported in Ember Data we can use them for widgets. Each widget would have its own model and validations all bundled together.

Then we won't have to jump through these data hoops between ember and firebase. (In theory)

For file uploads it would be nice to store some extra info about the files themselves.

Specifically for audio files it would be nice to have the time duration and filetype (mp3, ogg...etc).

In the form nav, all the options for a wysiwyg should be on by default. You should have to turn them off instead.

When a content type is saved and scaffolding is created, give me a message block to let them know what just happened. Likely best done through a modal that they have to close so we know they read it.

Similarily. If they save the content type after scaffolding has already run, we should alert them the scaffolding was not updated, and ask if they'd like it rebuilt (warning them this will overwrite changes). cc @LtSquigs for this bit.

Handle permission errors and auth token expiration after you're already in the system.

FIREBASE WARNING: auth() was canceled: Auth token is expired.

Fields should be embedded in content-type.

I'm trying to show a start here badge on the add content types menu item when no content types exist. For some reason, the class isn't applied to the li.

Line in question

https://github.com/webhook/webhook-cms/blob/master/app/templates/wh/_nav.hbs#L24

Here is the information needed to implement file uploading:

URL: http://23.253.89.18:3000/upload-file/ Will change at a later date
Method: POST
POST parameters:
    site: name of site
    token: token of site
    payload: file being uploaded
Multipart request

A simple Form tag with three form fields (site, token, payload as file field) was able to post an upload a file. So just need to do the equiv of that in javascript.

Not sure if possible to have a progress meter, as none of that information is really relayed. And it would only be a progress to our server, not to the other server.

This was on creation of a new type.

http://snid.es/image/3g1d1V210z2b

Don't display the dates as default fields in the list view on creation. They don't tell you much. Rather, show the first 3 items from the actual form, in this case, the wysiwyg/markdown stuff.

if there is any scroll offset, the cloned helper is offset up by however far you are scrolled down.

webhook/webhook#2

http://snid.es/image/2k3v2E1C0m1h

Investigate using StateManager for validations on new and edit item forms. Use styles here: http://wyrmsass.org/section-6.html

• Do not check required until saved.