You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should put together a mockup (in Figma, or Balsamiq, or draw.io, or whatever) to make sure we understand what the MVP for notree entails, and also to have a basic understanding of what the flow of the site looks like.
After putting together a mockup, should we try to put together some architectural docs and then start hammering out the web app?
The text was updated successfully, but these errors were encountered:
I'm wondering if the saas web app is going to distract from building out our core functionality at this stage or if it would help accelerate ideas. Not sure - could go either way 🤔.
@jollyjerr - I feel like it would help drive the core functionality, personally. I think it's a good way to showcase the core components, and how users of the opensource packages would actually use them (see how your notes page has helped drive the functionality of our graphing)
I think we should put together a mockup (in Figma, or Balsamiq, or draw.io, or whatever) to make sure we understand what the MVP for notree entails, and also to have a basic understanding of what the flow of the site looks like.
After putting together a mockup, should we try to put together some architectural docs and then start hammering out the web app?
The text was updated successfully, but these errors were encountered: