2022-03-25

#done/process

Outflow (Rufus)

#done/process

• Create separate product sections to get clear on the separate products and their roadmaps and interdependencies
• Hire a growth marketer https://growthexpert.io
  • Talk to Nathen at Life Itself
• Pages pitch
• Take over the datahub blog
  • Why not just take over DataHub - what's the problem? Why don't we just go for it and stop messing around 😉

Switch datahub.io stuff over to a new system

• Work out how to do the reverse proxy (suggest cloudflare workers)
  • Research options/info?
    • https://pham.codes/blog/reverse-proxy-with-cloudflare-workers
    • How Rufus did this once b4 at life itself
• Create mega site - is it pages or something else. Who cares! Right now, would just run with next.datahub.io code base …

Misc

• Solve cloudflare symlink issue (if we were using symlinks)

Pages - open source a part of pages …

#done/process

Repos

• /pages
  • templates
  • docs
• /next.datahub.io - core website (may not be public for now => we source some conte)

Asides

• Annoyance that stuff between portaljs and page but hey that's livable with

Portal.JS as a product

#done/process

The open source framework/library for building data driven sites

• open a product page here for portal.js
• Collect all existing materials / taglines for that (plus plan of work??)
• mock up a home page
• launch and share

Thoughts

On composition-vs-inheritance

The downside of composition is that a lot of stuff is manual.

e.g. nextjs has a compositional model.

What we have is 200 examples in nextjs repo for each case but what about when i want them all together. They all interfere in _app.js so there is this great fragility about installation and upgrading.

In inheritance / templating model the slots approach means that you can just add your plugins and they'll just work™️ (most of the time)