search

chriskodehub / kodehode-course-plan

Application supporting the planning of teaching on the Kodehode course
GNU General Public License v3.0
1 stars 2 forks source link

Breakdown of the project into logical categories #5

Open chriskodehub opened 2 years ago

chriskodehub commented 2 years ago

It will be good to divide the project into logical parts to manage the tasks more efficiently and have more minor details of the project to deal with. It will also be easier to do assignments.

My suggestion is this, but I don't know if it is the best solution.

Can you introduce your ideas?

Once we define the division of the project into areas, I will add Labels to the project and when creating the Issue or later, it will be possible to assign an Issue to a given group.

Ken9Kodehode commented 2 years ago

First we need to get this idea from a text to something we can work towards. Is anyone here very good with Figma ? So we can atleast draw up an idea.

And second: Would this be a web application or an actual app we have to install etc ? My suggestion is a web app because this can really grow big if we do it any other way!

Ken9Kodehode commented 2 years ago

If we find a free open sourced web app we could use as a starting point all this would be much easier to get a grip on :)

chriskodehub commented 2 years ago

First we need to get this idea from a text to something we can work towards. Is anyone here very good with Figma ? So we can atleast draw up an idea.

And second: Would this be a web application or an actual app we have to install etc ? My suggestion is a web app because this can really grow big if we do it any other way!

A very important topic. In order not to get lost in this thread, I suggest you create a separate Issue with the title "Workflow for Project." This will make it easier for us not to lose sight of him. In addition, it is worth adding a Label to the topic, eg Backend and Frontend, to make it easier to filter the Issue, which will be hundreds in a moment.

This Issue is about what Labels we should add so that such an important topic as yours does not get lost in the thicket of other news.

In the new Issue, you can also invite our teachers to help us choose the way we work. To do this, you enter @ and you should see a list of people connected to the project.

You can read about Labels here

Ishajob commented 2 years ago

I can help you with the a map for topics for each level for HTML/CSS , SQL

**Frontend

HTML og CSS : Level 1**

  1. [ ] Elements
  2. [ ] Anchors and attributes
  3. [ ] Head
  4. [ ] Strong and emphasis
  5. [ ] File naming and organisation
  6. [ ] CSS Borders, Outline, Margin, Padding
  7. [ ] Lists, images and multimedia (small parallex website building)
  8. [ ] Debugging
  9. [ ] HTML Best Practices
  10. [ ] (Scrimba “HTML og CSScrash course, Module 1, 2)

Level 2

  1. HTML forms and inputs
  2. HTML Tables
  3. Css Pseudo-classes
  4. Css transitions
  5. Css Animations

Backend Level 3 Backend SQL

[ ] 1. INTRODUCTION [ ] 2. Instalation [ ] 3. TYpes of databases [ ] 4. SQL Commands​ [ ] 5.  CREATE DATABASE [ ] 6. CREATE TABLE​ [ ] 7. SQL Data Types [ ] 8. Create Table​ [ ] 10. Drop Table​ [ ] 12. Truncate Table​ [ ] 14. Insert Into​ [ ] 16. Insert Multiple Rows​ [ ] 18. Select​ [ ] 20. Select Distinct [ ] 22. Where Clause​ [ ] 24. Where Operators ​ [ ] 26. AND, OR and NOT​ [ ] 28. Order By​ [ ] 30. Insert Into​ [ ] 32. Null Values​ [ ] 34. Is Null​ [ ] 36. Is Not Null​ [ ] 38. Update​