UI/UX/concept design #39
Comments
mimi-uxui-dev
changed the title
|
Results |
|
feedback
|
|
Results |
|
Worklog Video |
|
Worklog Video |
|
Results |
|
Worklog |
|
feedback also, going through the latest iteration of the slide deck, the We did not make one time "events" that are not bound to a chapter a thing, because coding cannot be learned in a weekend, so a serious effort needs regular events and a small group of people to support each other regularly, therefore the events should always be connected to a chapter and not a one-off event somehow in the air after which all efforts stop again. |
|
feedback a goal for wizardamigos is:because wizardamigos is decentralized, which means anyone can use the tools to make their own workshops, codecamps, etc.. with their own logo and theme and host it on their own domain .... probably wizardamigos.com should not be special if we don't have to be special.
...
...maybe we will even start using some other peoples tools to make our stuff (like css pixelart editor?) ...and others use our tools to make workshops about how to use their tools. In the end we are just one of many people using workshops and making tools :slight_smile: If we can be humble and blend into the background in a global network of people making tools and workshops and linking to each other, that would be preferrable, so our website should ideally not be necesary at all or it should be at most some sort of entry point/portal into the networked game where many people participate by making tools and workshops. ...where in the future many such entry point websites do exist, not just ours |
|
Results |
|
Results I see what you mean that changes everything, I think we should :
|
|
|
feedback 2022.03.07` we have different types of users (roles), which can use our tools to do something based on our "use cases" and we should probably create issues for each of those ...and later that should be written in a markdown file and a slide for each of them. gig
workshopsthere is no list of workshops on wizardamigos other than maybe a skilltree. wizardamigos does not maintain any workshops other than maybe a few workshops which teach what wizardamigos is and how the tools work, but all other workshops are maintained by the authors who make them. codecampsthe same is true for code camps, so also for code camps we dont have a list (see workshops) no signup/loginThe main page can be structured the way it is, but its totally old school too :slight_smile: Like, we do not have a "sign up" or a "login", because we dont have a database. the website just generates a so called "cryptographic keypair" for first time visitors and later it just loads it from the local cache and if the person clears their cache they lose the keypair, so even later we will store it in a users wallet (like metamask) .... no blogwe do not plan to have a blog at the moment no FAQwe do not have an FAQ, because everything should be self explanatory and if not there should be workshops. a game does not have an FAQ, you just start and learn it by playing if the game is good STORY TELLING maybe the wizard amigos website should be the the first page of the game? ...maybe it should all start with a workshop? ...or it should start with an empty profile page that needs to open the default workshop that explains what wizardamigos and the workshop is about? And the tool in that first workshop is the profile page maker? And when you finish it, you can get back to your profile with the successfully completed "profile page workshop" where you used the "make profile tool" to create your account and which shows you the recent workshop you did (which is the first workshop) and what workshops you can do from here? ...but if you load wizardamigos and you made already a profile, it loads that instetad? AND The little minimap shows you the current workshop and the dependencies and what other workshops you can unlock, but if you click full screen on that minimap, maybe thats how you see the whole skill tree? In the chat you can click on other learners to view their profile? or you can click on the author of a gig in the gig list? |
|
feedback ok, i now listend to the videos too. regarding the FAQ true, there is an issue, but it was always meant as something temporary while we dont have awesome apps yet to be self explanatory and support everytying well, but i would make it unnecessary to have an FAQ because everything is clear :-) regarding the blog
these updates have more the form of updates of system notifications, etc... and each piece of software and in our case each workshop, each chapter, etc... would or should have an updates log where people can subscribe and receive notifications. regarding workshop gigs basically, if a workshop is a blog post or a tweet or a ...or even beter, a github repository, then a gig is more like a github issue, anyone can open one. |
|
|
feedback
|
|
feedback
👍 regarfing UX. we need more than just simple resizing, but at the very least we need that :-) I think we need a tiling window manager. regarding HackMD notes taking
regarding playlist
*tiling window manager 4. regarding "no json mode"
So people who are scared of JSON (the "english" of data formats regariding its wide spread use and its also simple) and it is relatively human readable too. It also makes it easier for somebody to copy the json of a given workshop when they want to modify it to create their own. it enables people to look behind the scenes and encourages them to copy to create their own. I would agree with your assessment if it wasnt for wizard amigos being exactly about teaching coding as the new literacy :-) ...so everything we do should always make it as easy as possible for anyone to take a look behind the scene and switch from just a consumer user to become a coder and creator themselves :-) regarding description regarding info on gig-maker/workshop-creator |
|
feedback Wireframes: 1. full screen workshop video
2. nice idea to have icons to toggle other views
3. the "video area" might actually not always be a video
4. the "info" section is more a summary and it can include links to additional resources
5. idea: "add workshop description to workshop.json"
more on gigs/exercises: the gig details in the end is where you mention the gig page could be maybe a seperate page. A workshop is supposed to be an atomic unit to convey one skill or concept. So if a user could finish only the first 3 lessons in a workshop and can already do a gig then.... then the remaining lessons should be a different workshop. That kind of view could be good though if we are talking about a codecamp that groups multiple workshops. NEXT:
so in some ways, a "gig" is quite similar to the elements a workshop has.
also, while the learner is working on the gig, they might use the same tool the workshop was providing, ALSO: ...so i am not sure the popup overlay would solve the use case well more thoughts on "summary description": In general, i think we are dealing with two types of information:
For example, i was thinking that clicking the "title bar" of the "lesson window", Also, to keep things more generic and less specialized, a workshop could always have a very short lesson one with a summary about the workshop. Also, i have used many online learning platforms and also youtube and they often have summaries before or for example below youtube videos. Also if every repository on github at some point has a little workshop about the repository itself and a bunch of lesson. What about displaying the summary instead of video1 ...basically by generating some sort of "lesson 0" before things start? Alternative would be to include in the workshop tool and in our docs or our workshop about making workshops, that lesson 0 is seen as the "summary lesson". BUT also the point of workshops is to have good titles and to be so short, that people literally dont need summaries. That is of course different from "codecamps" :-) |
|
feedback 6. profile icon
technically: onmessage = ({ source, data: message }) => {
if (source === iwin) handle(message)
}
const iframe = document.createElement('iframe')
iframe.src = "https://wizardamigos.com/wallet/index.html"
document.body.append(iframe)
iframe.onload = () => { iwin = iframe.contentWindow }
var iwin
function handle (message) {
const { type, data } = message
switch (type) {
case: 'ready': return iwin.postMessage({ type: 'request-profile' })
case: 'profile': return updateProfilePicture(data)
// ... we can define more protocol messages to interact with our profile iframe "database"
}
} 2. The profile page feels relatively traditional at the moment.
...anyway, there should probably be a regarding code camps also, a user clicks on a code camp, its cool to preview maybe the json in the form you show, but: Maybe a codecamp could look like a part of the entire skilltree? skilltree: ...imagine a workshop has 20 needs, but there is only a few slots space around a workshop, so the remaining "needs" can be next to that workshop on a differnt layer and a user/player/learner can just use the elevator or teleporter to get there. ...just kidding :-) maybe your little skill tree map with boxes picture is good enough? :-) there is a type of game called in a map of regarding indicating that on the skilltree.
But, by browsing through different wizardamigos workshops, each workshop will talk to the users profile page (=wallet) and request information or store worksgop progress or accomplishments or open gigs by sending that data to the users profile page, so when the user returns to a workshop, the workshop can request all that information again to let the user continue where they left off ...basically the users profile page iframe is our user database :-) BUT: the users profile page is used in many contexts, not just wizardamigos one more thing:
also the way github does UI and how github does their dashboard could inspire how we do things :-) |
|
feedback you have a hackmd in the video, but cant find the link to it anywhere, can you add the link to it somewhere here? did you already somewhere update issues with that todo list in the hackmd? we definitely need to have one or more slides for each of them ...and what is too much for the slide deck goes on those hackmd files for each slide that list further details and links regarding tiling window manager: even more than that. each tile view should always consist of:
....so we can always open the program component or iframe in a tile. Later we need to upgrade that system so the programs in each tile can even communicate to other tiles, in case of iframes via all of that is definitely something supported by no off the shelve window manager component out there :P regarding default maintainer the default maintainer is definitely the maintainer and yes, they will get paid. every workshop you make in the future will list you and if other workshops build on top of those and many of them will and if they list gigs and they get done or anyone donates, you will get paid for it 😛 ...you made it, hehe 🙂 so yes, for sure |
|
feedback is says "make designs for everything". and also are the following maybe sub components of the workshop component? (and maybe also the codecamp or maybe not?)
is the following a sub issue of the "profile component" ?
|
|
Results
|
@todomain slides, each withsub slides&linked markdown files&wireframesto explain wizardamigos@output📦 wireframes & slides iteration 1 from comment1@output📦 wireframes & slides iteration 2 from comment2@output📦 wireframes & slides iteration 3 from comment3@output📦summary video@input📦summary video@input📦what have we built hackmdfrom History : How it all started #45@input📦history content slidesfrom History : How it all started #45@input📦brief summary slide deckfrom project brief @mimi_uxui-dev #42@input📦concept outline descriptionfrom get familiar with wizardamigos #46@output❓wizardamigos theme & designs@input❓wizardamigos theme & designs@output🏭wizardamigos concept slide deckfrom comment@info...
The text was updated successfully, but these errors were encountered: