Continuing on from our review of the project’s end goal, let’s sketch out the architecture for the frontend, with a focus just on local-only functionality.

Keeping things as simple as possible, I want a text field that we can edit, and which will persist our changes across reloads of the page. Lucky for us, automerge has a tutorial that does just that.

Since we’ve sorted out our build system, nothing there should need to change, and whatever functionality we get locally during development should be the same after deployment (though the state will be different for both).

All that taken together:

  1. Update the Fulcro code to have a text field we can edit, but without persistence
  2. Follow the automerge tutorial, sorting out how to integrate automerge with Fulcro, and ultimately introducing persistence with automerge.

While each of those items has many sub-items, some of which I’m aware of and some I’m sure will surprise me, I think that’s a good enough breakdown to get moving.

Until next time!