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
Please ask us anything you don't understand or need to know about the project.
To find out how exactly, please watch the @input tagged explanatory video linked above
in short:
Just post a worklog comment and write or post a screencast to show us the materials
or anything you want to ask and we will quickly post a feedback comment to provide answers.
How this works is descibed in your personal issue in the input screencasts that explain it further.
task
The "end users" of the website will be the members of the dat ecosystem consortium
and everyone who founds and build their own project on top of the same software stack,
which at the moment is mainly https://hypercore-protocol.org and we can answer all questions on behalf of all other "end users".
Based on the many resources above which you can use as inputs How would you structure the website to somehow integrate the long history into the new website?
Please feel free to edit your issue and make more tasks and todos and move some of the inputs under todos where they belong
If you can group inputs based on the part of the website that will deal with them, that might make it better.
You might also want to create new issues and link them as todos so some inputs can be handled in that sub issue.
Everything that helps to keep things more neat is great :-)
to repeat it again - the technique how to do all that is described in the @input video above
The text was updated successfully, but these errors were encountered:
@todo
@input
📦dat-ecosystem project screencast
from trial phase #3@input
📦github issue management system
from trial phase #3@input
📦example project screencast "wizardamigos"
from trial phase #3@input
📦example project screencast "datdot-ui"
from trial phase #3@input
📦little checklist and summary
from trial phase #3"new dat-ecosystem website project plan"
and post it in the comments below as your first worklog@output
❓new dat-ecosystem website project plan issue
@info
section in each task issue or sub task issue you made@output
❓website UI/UX specification & wireframes
@output
❓dat-ecosystem design system
@output
❓list of re-usable web components
@output
❓implemented website
@output
❓link to one or multiple final screencasts (each 3-5 minutes max) where the candidate walks us through the entire project plan
@info
all details of the dat-ecosystem project can be found here
@info
sectionquestions
Please ask us anything you don't understand or need to know about the project.
To find out how exactly, please watch the
@input
tagged explanatory video linked aboveworklog
comment and write or post a screencast to show us the materialstask
The "end users" of the website will be the members of the dat ecosystem consortium
and everyone who founds and build their own project on top of the same software stack,
which at the moment is mainly https://hypercore-protocol.org and we can answer all questions on behalf of all other "end users".
Based on the many resources above which you can use as inputs How would you structure the website to somehow integrate the long history into the new website?
@input
video aboveThe text was updated successfully, but these errors were encountered: