The form component looks like this:

I think the text box is just an illustration of what a form is? Yet I can click it and write into it with no obvious effect. Instead, the entire box should be the click-and-drag target.

Node version: 7.0
NPM version: 3.10.8

I have tried upgrading Xcode tools, npm and node itself
as well as Redis package, but still get errors:

[email protected] preinstall: make || gmake
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] preinstall script 'make || gmake'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the hiredis package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! make || gmake
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs hiredis
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls hiredis
npm ERR! There is likely additional logging output above.

I guess this is probably a feature request for a thumbnail or something…

@morgamic just hit this snag:

Create a row with, say, three columns and put some content in.

Then change the layout of that row.

It'll delete the content of the entire row. Ouch.

We should probably warn, or disallow changing the layout if we can't reasonably salvage the content?

Explain what Napkin is, why you should use it, etc.

The offending article:

The Persona sign in button will be used across the web to mean exactly that: To sign in. Using it as a sign out button dilutes the Persona brand.

Not only this the Persona sign in button is naturally a call to action, and using a call to action for a sign out action is generally a bad idea.

Also the button (area where the sign in action is initiated) does not change significantly between signed in and signed out state. As such when I first used the site I signed in, and then signed out immediately afterwards because I assumed Persona had broken in some way.

This should be the user's gravatar/libravatar followed by their account.

Hi there

I just tried napkin and wanted to build a little base structure of a site which includes a nav bar and links between pages. Now I can add screen links to a navigation and let a screen link to itself but not to another screen, I always get a note saying "Element's screen must correspond to a real screen.". At times I get the same message on the Screen link on the menu on the left and can't even drag the Screne link onto the page.

This napkin thing looks like an awesome tool. If it works, I'd love to try it a bit more and maybe actually use it.

Cheers

Edit: I tried on Linux w/ chromium-20 and firefox-15

is the share screen supposed to be accessible by a user that isn't logged in, or only people who are logged in?

Reduce the screen width and let everything adjust accordingly. It's a bit too wide for most resolutions as not everyone is on a really wide screen (e.g. might be working on a laptop).

I'd probably think of moving the Github link to a non-conventional one (just in the side nav as a small link or something) so we don't have to worry about it blocking anything

Might want to make the sidebar a huge trash can when dragging an item. Huge drag targets for the win.

When adding a new paragraph element or heading, I sometimes see two appear. Once refreshing, only the last one appears (I edited both before refresh and noticed that it just took the text from the last one - might be a clue?)

Greyed out filter on landing page takes a while to load. (FOUC on landing.)

In order to draw attention to the sign in button the page is greyed out. This greying out filter is, however, only applied after the page has loaded thus causing a FOUC.

This repository doesn't specify under which license the code is distributed. Please add a LICENSE file.

If you tell me which one you want, I can do a pr.

Previously, we used BSD 3-clause. But I think the plan is now to do Apache 2 for Mozilla webdev projects.