Skip to content

Latest commit

 

History

History
354 lines (330 loc) · 20.6 KB

todo.md

File metadata and controls

354 lines (330 loc) · 20.6 KB
Raw

TODO: to be moved into GitHub/Linear issues

Public website release

  • inbox and top inbox. make it save into LA, as personal links.

    • create a CLI for it
    • use it. allow searches for it. add metadata to each addition

  • setup to use https://vercel.com/font (should probably look better than current font, try it out)

  • add tags support. pre tag with inbox. top-inbox

    • add ‘explain ..’ selected text. show in desktop app result with ability to drill further. if cache return instantly. if not let it process in background then send notification or instantly turn to app and stream result. user setting. cache result. always use best state of art GPT!

  • setup.ts works well

  • add command to generate the command table from package.json (as external cli tool?)

  • be able to attach a topic to a link

  • Add Create Personal Guide button (maybe next to Improve Guide)

  • allow edits of topic summary and section summary of each section

    • enter text inside, save it to html and store in db
    • render the content of the html in topic summary and each of the section summaries correctly

  • stripe updates and works

    • memberUntil should update with new date, unix to edgedb date, make work

  • user gets created on hanko auth

  • render the results like markdown in topic page using https://github.com/micromark/micromark

    • check what syntax internal links need to be to link properly

  • go through each topic in wiki and

    1. create global topic from the wiki topic
    2. parse all the links inside in ## Links
    • those links are Other links
    1. parse all links that are part of subheadings such as in js-libraries
    • the links inside the section are part of the section in the guide
    1. calculate the references from the topics, update the json file
    • make it a function that does it for a given file

  • fix search in landing page

  • use some lib from https://github.com/wooorm to render markdown as html with solid

    • topic summary. section summary are all markdown. render as markdown strings

  • full guide is showing and is pretty

  • have a count with how many links are inside a section in edit guide at least (maybe useful in global topic sections too)

  • check that non members can't run edit guide

    • and members who do edit guide. edit their own personal versions of the guide
    • first test locally, make sure edgedb updates the user memberUntil value correctly
    • then test in production. with real card. updates and works well

  • allow marking a topic as learning / learned / to learn

  • free trial limits set

  • allow users to add unverified links for their own

  • allow marking links inside sections of a guide as bookmarks or done (make icons more obvious)

    • show on hover what actions do

  • use the graph connections from above to render graph in landing page

  • add search in each global topic page

  • profile page shows links added (don't do profile until user paid for MVP as actions are paywalled)

    • or if do, must look good. choosing username is paywalled too

  • do video in https://www.remotion.dev for X post to make it snappy. write nice text (join their discord to get help)

    • do nice video overview of the tool. add it to X post but also to /pricing to show what the tool is about and what its value is

  • make raycast extension work. so it searches through topics learned/learning/to-learn + all the links added to personal collection

  • desktop app with solid-monaco that publishes the markdown content into a wiki like vitepress

    • editing of files from a connected folder in file system
    • add publish button to each topic. publish (if member) to wiki in similar style as vitepress
      • support adding of notes
      • also show in each global topic user published topics. show fragments of the topic in a list (similar to how links or notes are there) (clicking on the fragment of the topic for the user will go to the topic for the user)

  • go deep into solana. do https://www.soldev.app/course

    • setup buy. and release with next.js using https://github.com/nightly-labs/solana-web3-template
      • join discord, ask for help.
      • need to be able to pay for digital good with solana and unlock the content for the user
      • need to be aware of their wallet address before purchase is made. check before doing transaction that this user is aware of this solana address?
      • check and use https://github.com/solana-labs/solana-pay for payments. its robust!
      • setup stripe checkouts for each digital good sold too!
      • release gumroad clone
        • sell course through LA buy.. users who bought get access. users who already bought course via email get discount code they can enter in course purchase screen and get access to course for free
      • talk to Felix from hanko on how to reuse hanko login session from la proper to buy.la (how to do it)
      • check auth works well with react/next.js (should be even better as hanko has first class support for react). adapt ideas to solid code
    • use code from https://github.com/nikitavoloboev/sol-pay
    • try do escrow service for idea marketplace
      • use https://squads.so. ask for help in their discord and also Mango founder. make it work

  • mobile app start with ignite

    • remove all non useful files etc.
    • have similar DX to solid website
    • buy and try out https://tamagui.dev/takeout | take ideas from it
    • solve hanko auth and ability to do graphql requets

  • make related links work

    • potentially as an icon on Link component to expand to see related links
    • make it work inside edgedb schema well, what is a related link?
    • link to Wikipedia in all Intro maybe as special icon on Intro section (to the right)

  • guide edit

    • show all links in the topic in Other. move all links to Other by default.
      • links in the sections above should be removed from Other on addition
    • guide edit grafbase, show error in toast, if error happens
    • show toast when succesfully updated the guide
    • check that user has paid using hanko id
      • test the stripe thing, make sure it updates user on stripe success with date
      • test it locally, then in production too
    • show loading indicator on submit changes button as grafbase mutation is processing
    • grafbase mutate global topic
      • edgedb mutation
      • validate inputs on the web page in /edit
      • all should live update
      • check in production, it works
    • and have a way to add a new global link too by pressing Add link button
      • will go to /links/new page
        • add ability to go to /links/new with url as param, to instantly prefill everything
        • also allow attaching a link to a topic instantly too
    • index all global links and put in orama db for search
    • add input box to search over the titles
    • allow adding description to section
    • add a search box for title that searches over all the links attached to the current topic
      • on choosing a link, add a link to a section
    • allow rearranging links inside a section
    • do it topic by topic
      • parse topic links, make each global link have main topic as the topic in wiki
        • try do a link to global topic (if fails do as string), then fix it later as real link
    • have separate search for global links that have the topic as main topic
    • and have another search that searches through all global links
    • when pressing return on one of the global links in search, show all the link details
    • allow rearranging of links, use https://solid-dnd.com
      • also allow rearranging of sections
    • make Search work with orama, no fuse.js
    • lock guide edit to admins of topic only

  • change getGlobalTopic query, probably remove it and replace it with just a call to get all user info details about what topics user is learning etc. same for links etc.

    • as separate query

  • clean up data model, don't think there is need for relatedLinks and relatedNotes

    • global link and global note will have a reference to the topic already so can get this info this way

  • return all the global links as part of query for global topic

    • use the links returned in search for the guide edit

  • fix ui glitch on hovering over search results in landing page

    • part of Search component issue

  • modular forms + valibot

  • clear undefinedundefined from url in global links

  • use create, not add in edgedb function names

  • use modular forms for all the forms

    • validate the FormData

  • use edgeql queries raw for queries that I can't do with edgedb-js

    • figure out how to use them in nice way

  • on success of global link edit

    • make sure only admins can do edits of global links
    • allow main switching topic connected

  • separate page to edit links

  • in guide edit, search for exsting links by title, add them

    • on edit, go to separate page to do an edit
    • allow reordering of links
    • make endpoints work for all!GG

  • check for global links, some start with https: still

    • i.e. "https://www.mikeash.com/pyblog/friday-qa-2015-07-31-tagged-pointer-strings.html"
    • do select query and check
    • make protocol required

  • put all global links into links.json with all properties shown with id for fast search

  • go through each wiki page

    • create global topic
    • scan all the links inside the file
      • create global links from all files (make sure description, related links are there)
    • calculate graph connections (folder/file or mentions of other topics)

  • /links/<id> or /links/<url> to make edits to global link data

  • edit guide

    • add/delete section
      • section guided/unguided
    • add link to section
    • section

  • links/new = add new global links

  • test stripe works

  • make graph work

  • load all urls from wiki, not just from ## Links

  • make sure on /auth, account gets created

  • remove / from end of url in GlobalLink

  • integrate search deeply (https://docs.oramasearch.com)

  • design close to Fey.app & Luma (clean UI)

  • load all global links into local storage with tinybase

  • allow searching all global links in landing page

    • have a way to switch between looking for topics and looking for a link to open
    • non member feature, for non members, load in 1,000 top links, then on using result go to /pricing

  • update UI of topic page for editing

  • update UI of topic page for viewing

  • make sure hanko auth web component does not freeze on auth in Ubuntu

    • hanko team is aware of it, ask what is the progress on it

  • update readme.md what happens when bun web causes error with crypto not working properly

    • try make it so error does not happen with bun!

  • use R2 (https://developers.cloudflare.com/r2/) to store user profile images

  • stripe works, updates memberUntil status of users when payment is succesful

  • blur 50 % of guide for non members

  • global edit of guide working

    • works well with global stores
    • mutations work
      • adding new sections/links
      • deleting links/sections
      • reorder of links/sections
    • entering URL into URL input, does search if URL exists as GlobalLink
      • if it does, grab all metadata for URL and prefill it
      • otherwise, give option for user to create new GlobalLink with new metadata
    • make it work visually well
    • all links in sections are GlobalLinks and thus can be tracked as working on / completed
    • section can have ordered list of links and unordered
      • order list of links is sorteable, order matters

  • upload guides for 1050 topics

    • start with 3d-printing and go down the generated list one by one

  • update topic graph in landing page

    • landing page looks and works great
    • graph works well on mobile/desktop, nicely scrollable and zoomeable

  • DX: add codegen for all resolvers, so they are typed

  • test auth works in dev.

  • test grafbase works in dev.

  • test user can sign in and mark topic as learned and on refresh it keeps the state for user

  • check mobile layout works for landing page / pricing / global topic page / user profile

  • global topic page works well visually (new design)

  • update readme.md and make sure dev env is easy to setup for new devs

  • use docs/todo.md for all issues until KusKus adds support for GitHub

    • in future have KusKus sync up GitHub issues with this docs/todo.md file
    • each of the ## headings here is a GitHub issue. with an option to create one of the bullet points into a separate sub GitHub issue (where sub issue will show the parent issue)
      • this sync is important to have discussions available. still, everything is serialisable into this markdown docs/todo.md file, updated on CI
    • grab a list of all todo: comments in code and show it as a generated list in code-todo.md too
    • embedding images should work too, inline links to images (probably uploaded to GitHub inline in todo.md) (once KusKus works with GitHub)

  • design UI for when users hit a / that is not yet in LA db

    • show empty state, users can still mark progress on the topic and request to be moderator of it to create a guide for it

  • /links/<url> to show full url + all the metadata

    • allow members to make suggestive edits to the link with new metadata

  • update readme to make it work with local edgedb

    • pre seed it with content so dev ux is amazing

  • add footer like https://twitter.com/steveruizok/status/1712487213852749911

    • link to X, GitHub, Discord
    • say in pretty letters Free coode. Build the tool you want.

Public desktop app release

  • use https://github.com/alxnddr/solid-monaco for editor
    • move all other text editor code to solid-ui repo
    • keep clean code, work with monaco as much as possible
  • let users choose a folder of existing markdown files to sync with
  • or allow choosing a folder where markdown files will be synced to
  • load in all the .md files as topics and show in sidebar
  • allow searching of topics
  • allow editing of topics using CodeMirror
    • or Monaco editor, CodeMirror is cleanest (what Obsidian uses)
  • loads all the desktop app state into SQLite
    • tauri/rust reads and writes from sqlite db. sqlite db is fully reactive
    • so if changes are made to files in the connected folder, sqlite db is updated with changes
    • likewise if changes are made to solid store state, it gets persisted to sqlite and also to the file system where needed
  • public content
  • global hotkey to add current link from safari/chrome using applescript (or some other way)
  • search existing bookmarks with raycast

Public user wikis

  • all content published via desktop app, rendered as in wiki.nikiv.dev

Mobile app release

Public website improvements

  • hit Grafbase cache for most things where it makes sense
    • global guides, more?
  • official topics should have verified badge

GlobalLink improvements

  • global links added should have verified: false/true
    • LA validates links that are non verified to make sure they have right metadata

Analytics

Uses

  • ability for users to share their stack of tools they use

API access

  • add API access to read/write to LA, guarded with Unkey potentially

DX

  • annoying how when you do mobius query and then try to access stuff with .data.publicGetGlobalTopic for example, it's super unsafe
    • find a nice way to solve this

Other

  • if not editing guide sections inline, can highlight the section being edited when section edit slide window shows
  • better web search using https://github.com/oramasearch/orama
  • do proper observability and logging, especially on edgedb CRUD queries, make sure it can't fail for bad reasons, and if error happens, surface it to grafbase/users
  • log all console.error with TinyBird or HyperDX
  • add multiplayer support using tinybase/partykit
  • allow importing of other people's bookmark presets (minus private bookmarks)
  • get https://github.com/thetarnav/solid-devtools working, specifically ability to select an element in browser and go to the component in code
  • release all Figma to public
    • FigJam + Figma main design files
  • import { Motion } from "@motionone/solid" always gives type trouble, don't get why
  • replace fuse.js with orama in Search component. don't use fuse.js any more
  • setup nice way to do dump and restore of a database
    • 2 separate commands
      • on dump will most likely move the edgedb.db into private/ folder? so its git ignored. otherwise can git ignore for *.db
  • setup nice way to bootstrap edgedb locally with content
    • read the seed folder and load things into edgedb
    • create global topic users can see with a guide editor fully working etc.
  • maybe move to Vercel as there is more features than Pages
    • also can setup grafbase deploys on each branch with preview websites easily as grafbase natively supports it
    • otherwise need to use this api https://developers.cloudflare.com/api/operations/pages-project-update-project
      • and on each branch created, setup preview deployment that will point to grafbase preview deploy URL
      • look at github webhooks and consume the preview url of Grafbase for each branch for grafbase test deploys
  • have infinite login sessions with hanko (how you can do it)
  • in grafbase, what do I do on success in resolvers?
    • do I return "success"?
  • update tiptap editor in website to allow making links to other topics simiar to markdown links with ../topic.md syntax. show a popover with search over topics
    • should be fast to edit topic guides
  • remove non used packages in all package.json (there is tool that helps with this)
  • pressing on section in right sidebar of global topic, should jump/scroll to section
  • make all resolvers be try catch (err), then show error via GraphQLError(error)
  • all catch (err)
    • should log to baselime
    • actually log every useful log to baselime!
  • wrap around mobius and show a pill or toast when error happens with any of the grafbase requests
    • this way you can just do queries to grafbase and error showing is fully abstracted and nice
  • replace npx grafbase@latest dev with bunx grafbase@latest dev. issue with bun. reach out to help resolve it
  • run command to remove non used package.json deps
    • there was github repo that did this well