🍴PPPs: Week 2 - ForkableRecipe.com
My first PPP intentionally forecasted out 2 weeks. Oops. Switching to 1-week plans now. So, this week's plan is kind of the back-half of the 1st week's plan.
Plans📆
-
Enable a user to add a lightning address or node information.
-
Get a crude button/link functioning that uses the user's lightning address somehow.
-
OR
-
Take custody for the user...still an open question. Going to experiment with it next Saturday night.
Progress âś…
-
âś… As planned - Moved the app on both dev and prod behind nginx and HTTPS!
-
âś… As planned - Got some thoughts out of my head, behind /docs, and improved the home-page content
-
âś… Bonus Progress - Actually implemented a tiny bit of the vision where the recipe object model can get rendered. You can now make a repo, using the CookLang.org file format (with a tiny tweak to their spec to call out the "Open Recipe Repo Format".
Current Problems/Questions/Help âś‹
-
I'm trying to learn enough to implement a "tip" or "boost" button on a per-recipe context. The front-end parts of this are tricky for me. I'm looking at René's work, and the Stacker News, and trying to do something somewhere in between on a per-recipe basis.
- Question 1: Does anybody else know of any other inspirational patterns/implementations/libraries? Maybe trimmed down, first-principles stuff? Just trying to learn.
-
We all (the makers in this hackathon, plus other Bitcoin-project developers) need the right words, to help pre-coiners understand stuff like Bitcoin, Lightning, Sats, etc. I'd rather have the actual words on my site, to be able to tweak to the users I expect.
- Question 2: Does the Bitcoin community have any boiler plate primers that are intended to be copy-pasted like I put in the FAQ (at the bottom of this page) to help teach pre-coiners?
Links đź”—
-
New /docs page
-
Example recipe being rendered from Cooklang Spec and object model.