This is a good reference to the majority of the link locations: http://noflojs.org/

This shot could do with some work:

Needs to incorporate the copy from https://github.com/bergie/noflo

Preferably centred:

live:

psd:

More padding needed, minimum of 60px top and bottom should be a good marker.

Live:

PSD:

There's a page in NoFlo documentation describing NoFlo JSON graph format: http://noflojs.org/documentation/json/

While GoFlow is slowly progressing towards support of loading graphs at run-time, the documentation provided for NoFlo JSON is not enough for a 3rd-party implementation. It contains just a minimal example without an explanation, while a more formal and detailed specification is required for the format to be supported by 3rd-party FBP runtimes.

Example questions left after reading the current docs:

• what is "metadata"?
• is "metadata" related to "initial IP" concept?
• how are initial IPs represented on the graph if it isn't?
• what is "data" and which component is responsible for reading it?
• etc.

Backgrounds crop with a 25px (approx) margin, should be full width

live:

psd:

Probably due to content awaiting to be populated.

http://noflojs.org/documentation/

Not currently integrated.

https://www.dropbox.com/s/v7sy4c3jbqhv2mp/nav.jpg

Shows search too

In 0.4, NoFlo works on both Node.js and the browser. Some generic components will be available for both platforms, but most are specific to one of them.

Users should be able to choose whether they want to see component libraries available for browsers, or for Node.js

As per #31 the base reusable unit of code in NoFlo is a Component. Components are shipped in libraries that usually contain multiple of them, but the thing that will interest a developer is the components available, not the libraries.

In addition to a page where users can see and search for components for Node.js or browser, we should have a details page for each component.

This page should show the metadata of the component (name, author, library, etc), but also the annotated source code.

Here is an example of how that could look like (from the old NoFlo UI)

Using Flowtrace, refs noflo/noflo#536

Right now Github Pages does the page build. This means we don't get notified about failures until we merge to master, when its already too late. It also limits what we can use to what gh-pages support, and requires checking in intermediate/generated data to the git repo.

I'm interested to see how to do flow control in noflo with methods like these: https://github.com/baconjs/bacon.js/wiki/Diagrams

The list of components shouldn't have a border and a slightly tighter, harsher shadow. Also, "version" text isn't italicised

live:

psd:

Andr̩ Neves etc

Live:

psd:

Book image cropped on slide. Due to mask (needs unmasking) in psd

Sub text should also be smaller (14px with line height of 20px) or whatever is relative

Also cut off at the top. This is due to a mask in photoshop. We could identify these and I can start generating the assets?

Should replicate this list: https://npmjs.org/browse/depended/noflo

Imagine this will get automated at some point

Need to either prepare larger images or a frame to the site to prevent this.

Note: Background colours are off too.

Live:

psd:

Build and/or min .js file with only used components.

A Component Library is a collection of NoFlo components, reusable pieces of software that you can use as nodes in a FBP graph.

The important part should really be the components, not the libraries they come from (though this info should also be available)

Missing for code examples both on https://noflojs.org/api/NoFlo/ and https://noflojs.org/tutorials/canadianness/

https://noflojs.org does not work, fails with a certificate error because the cert is for *.github.com.

This is especially problematic because we host software on this domain, ie for noflo-browser builds used in Flowhub and other places. These cannot be loaded on a HTTPS site, and for HTTP can be intercepted without detection.

More padding top and bottom to give more breathing room for text;

Live:

Psd

Currently implemented at 120 degrees (approx). This may help tighten them up.

More padding bottom please:

Link colour should be a little darker: 467eb8

live:

psd

Note: companies are just placeholders for now. Need confirmation on who actually uses it from Henri.

Note: Top bar is thinner (60px)

Reintroducing the logo on mobile. Listing the dropdown of everything site wide under the table of contents (three lines)

White background displaying on image:

More padding top as well please

Dropdown is missing on the main nav for:

• Github
• share
• contact

Some examples of json graph definition have a "source" port instead of "in" for ReadFile.

Leading (line height) on titles need to be tighter, more space for dividing keyline

i try this both on branch gh-pages and kickstarter and face the same problem after running npm install and then grunt dev.

Running "connect:dev" (connect) task
Started connect web server on localhost:4000.

Running "sass:src" (sass) task
OptionParser::InvalidOption: invalid option: --sourcemap
  Use --trace for backtrace.
Warning:  Use --force to continue.

Aborted due to warnings.

Passing groups, disconnects, etc., and why.

White bg on image logos

Example of unresponsive type: excuse the retina display (for live)

live:

psd

More margin needed between text and image. Body copy is smaller too.

code:

psd

Slightly lighter and less saturated blue is used. hex: 5396db hsb(210,62,86)

Live:

psd:

live:

psd

The builded noflo.js at http://noflojs.org/download/ does not work when included with the instructions included in the page.

Apparently it does not include the selected libraries and aliases .coffee files instead of .js

Also doesn't condense text into (3 lines) table of contents icon:

live:

psd