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
As it stands today, the tool is functional but lack a lot on the user experience, as it was made to simply fill an internal problem to deal with collection-generation within the memo project.
We need to make sure that memo_editor also fits the same quality that memo brings to their users, as we eventually plan to release an alpha version that anyone can use to customize its collections and memos, suggest additions to the core memo repository, etcetera.
This also involves adding a bunch of other functionalities that are missing today, like validating the collection properties text fields, responsive layout (with experience-adjusted features for each "major" device size), connecting the existing collections in the memo repository and "bridge" the changes-suggestion in the core repository (using this editor tool), and a lot of other things.
This also brings us one important question (that we are currently evaluating): should we actually merge this editor into the main tool (/memo repository) and diminish the difficulty for new entrants to join the memo ecosystem and start contributing?
The text was updated successfully, but these errors were encountered:
As it stands today, the tool is functional but lack a lot on the user experience, as it was made to simply fill an internal problem to deal with collection-generation within the memo project.
We need to make sure that
memo_editor
also fits the same quality thatmemo
brings to their users, as we eventually plan to release an alpha version that anyone can use to customize its collections and memos, suggest additions to the corememo
repository, etcetera.This also involves adding a bunch of other functionalities that are missing today, like validating the collection properties text fields, responsive layout (with experience-adjusted features for each "major" device size), connecting the existing collections in the
memo
repository and "bridge" the changes-suggestion in the core repository (using this editor tool), and a lot of other things.This also brings us one important question (that we are currently evaluating): should we actually merge this editor into the main tool (
/memo
repository) and diminish the difficulty for new entrants to join the memo ecosystem and start contributing?The text was updated successfully, but these errors were encountered: