The domain name, mapping, and record set should be listed in services/template.yaml.

At the very least the view page should let one go to the browse page.

Be sure to sketch the design first.

Consider also showing progression. Either
a. Looping animation.
b. Frame from mouse position.

Reproduce by creating a rectangle with an odd width/height.

Clear example:

Fuzzy example:

Replace the builder title with RIEK. See https://github.com/kaivi/riek.

Other improvements:

• Remove the edit icon.
• Increase the font size.

Create a utility that adds a listener to the beforeunload event. This will cause a message to be shown to the user before they reload or exit the site.

window.addEventListener('beforeunload', event => {
  event.preventDefault();
  event.returnValue = '';
});

Call this utility in the componentDidMount method of Create. Remove the listener when the user publishes the fractal.

• Make the API Edge Optimized
• Create a distribution for static assets in S3

Lines should appear when the side of a shape line up with the side of another shape. Additionally, the shape should sort of "jump" to meet the point.

Currently, api.fractal.parts/fractals lets one specify a sort parameter. Results after always returned in ascending order. In this ticket, enable descending order with a - prefix.

Create fractals using the builder UI then save the database rows to disk. See https://knexjs.org/#Seeds-CLI.

Useful resources for fractal IFS:

• http://paulbourke.net/fractals/ifs/
• http://ecademy.agnesscott.edu/~lriddle/ifs/ifs.htm

Potential libraries

• http://hammerjs.github.io/
• https://modernizr.com/

The encompasses drag and drop.

Specifics TBD. This should be some sort of guide that leads users through creating a fractal.

Create a scheduled Lambda that runs every five minutes. The Lambda should hit all three api.fractal.parts endpoints (GET /fractals, POST /fractals, GET /fractals/{key}). As part of this ticket, add a parameter to each Lambda (e.g. warming, healthcheck).

Of course this Lambda will not fix all cold starts. Scale outs will still have cold start problems.

When the user navigates to fractal.parts/<title>, the site should GET /fractals/<title>. If the fractal is found, render the attractor. If the fractal is not found, display a 404 page.

Fractals display fine structure; the attractor shows irregularity at arbitrarily small scales. Users of fractal.parts should be able to infinitely zoom in on a fractal. Fractals will need to be rendered lazily.

TBD

The builder renders improperly for small screens.

Shapes should show the move cursor. Handles should show the appropriate resize cursor.

https://github.com/marketplace/category/continuous-integration

POST /fractals should save the given fractal in a DynamoDB table. GET /fractals/<id> should retrieve the fractal with the given ID from the database.

Negative width/height causes a shape to be unclickable. Reproduce by dragging a handle beyond the opposite handle.

This should exist at a draggable element near the shape.

In the viewer, users should also be able to see the original template. Ideally, they should also be able to see a progression from template to attractor: https://en.wikipedia.org/wiki/Iterated_function_system#/media/File:Ifs-construction.png.

Unanswered questions:

• Should this be a quick animation between template/attractor states? Or should this be a slider where the user can control the speed and pause?
• Should the viewer display both directions (Template -> Attractor and Attractor -> Template)?
• Should this also appear in the builder as well?

This should just be for a single shape.

All previous operations should work with these new shapes.

fractal.parts/browse should GET /fractals and display a (rough) grid of fractals. Clicking a fractal navigates to its designated page. Implement pagination and sorting.

Currently the attractor renders with the same dimensions as the base in the original template. The attractor should actually be sized relative to the canvas. Be sure that the attractor isn't stretched.

Use the same (or at least similar) logic to size the base shape in the builder.

With this template

and one iteration, the attractor becomes

Consider the chain of responsibility design pattern.

Reference the structure seen in your "squares.js" prototype.

Use ajv.

Current shapes store rotation in degrees. Use radians instead to remove the need for excessive unit conversion.

https://github.com/facebook/create-react-app

Clicking Publish in the builder should POST the template to /fractals. The user should be redirected to fractal.parts/.

Shown in the console:

TypeError: t.t0.response is undefined Create.js:139:16

Options include:

• Render type (random vs. progressive).
• Number of iterations.

Consider a drawer: https://ant.design/components/drawer/. The drawer could be triggered on a gear button:

<Button size="large" icon="setting" />

Currently, users can drag shapes outside the canvas. Objects should either not be allowed outside the canvas or should jump back to the canvas on mouseup.

On publish, validate that

• The title has been edited.
• The title has at least one alphanumeric character.
• The title doesn't already exist.
• At least one shape has been added.

Add draggable elements at the corners and sides of rectangles.

Add a new shape object to the canvas stack. This needs to hook up to the "New" button in the builder UI.

See https://coderwall.com/p/vmkk6a/how-to-make-the-canvas-not-look-like-crap-on-retina

GET /fractals should pull all fractals from the database. Users should be able to sort on creation date or views.

This should live in the browse and view pages. Show either a spinner or gray content (e.g. https://ant.design/components/skeleton/)