Skip to content

Data model #66

@asim

Description

@asim

I can definitely see that as you get to more apps you need a set data model for cards and apps. In 4-5 different packages there are different ways to represent the cache, the data, the cards, the apps, etc. so I need a way to unify it

  1. A way to represent Card data and the html. Needs to include title, link, more, timestamp, etc
  2. A way to publish that card data so that we are always getting the latest on the home page
  3. A way to cache app data without needing to explicitly do it e.g across cold restarts it's the same data
  4. A way to manage long running go routines for polling RSS feeds, etc.
  5. A way to present the app on the web an API that's consistent across everything
  6. A clean way to use the LLM model that isn't baked into the chat app
  7. ...I could go on and on

There's a sort of endless list of tasks. Meaning lots of opportunities to build something useful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions