Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

trial phase task for @CodeLawd #10

Closed
12 tasks done
Tracked by #3
serapath opened this issue Apr 25, 2022 · 2 comments
Closed
12 tasks done
Tracked by #3

trial phase task for @CodeLawd #10

serapath opened this issue Apr 25, 2022 · 2 comments

Comments

@serapath
Copy link
Member

serapath commented Apr 25, 2022

@todo

  • make a very detailed project plan for the new dat-ecosystem website using our github issues based project management methods
    • @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
    • study all the input materials provided
    • create a new "roadmapping" issue called "new dat-ecosystem website project plan" and post it in the comments below as your first worklog
      • @outputnew dat-ecosystem website project plan issue
    • create a detailed project plan from A to Z about the new dat-ecosystem website
      • keep in mind the project should last 4-8 weeks
      • include a high level list of tasks that can be issues itself to outline the important parts of the project
      • include all inputs listed above and whatever else you find important as inputs in your main project issue or any sub issue
      • create more sub tasks and sub issues to get to all tasks that will need to be executed to finish the entire project
      • write the expected input links to documents and expected output documents for each tasks or sub task in your project plan
      • link all planned outputs of the earlier tasks in your plan as inputs of the later tasks in your project structure
      • add for each task additional information or links or inspiration or anything in the issues @info section in each task issue or sub task issue you made
      • write down/adapt/modify/update the list of final output(s) for your plan plan in a comment here below in this issue
    • @outputwebsite UI/UX specification & wireframes
    • @outputdat-ecosystem design system
    • @outputlist of re-usable web components
    • @outputimplemented website
    • @outputlink 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

questions

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
@serapath serapath mentioned this issue Apr 25, 2022
12 tasks
@CodeLawd
Copy link

CodeLawd commented Apr 28, 2022

@worklog

Below is the first worklog

@playproject-io playproject-io locked as resolved and limited conversation to collaborators May 1, 2022
@serapath
Copy link
Member Author

serapath commented May 6, 2022

merged into #49

@serapath serapath closed this as completed May 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants