blumilksoftware / keating Goto Github PK

Right now all CRUD actions are buttons, so they are unclickable with right-click if anyone would like to open it in new card.

It would be nice to refactor links to links (link = something that opens new page) and leave buttons as buttons (button = something that opens some modal and stuff).

It would be nice to add tooltips to all "icon-only" buttons, like here:

It would be perfect to have an option "publish this news on Google Classroom". Somehow we would need to point to which channels it should be published.

This is related to #15 and should be done after implementation of this task.

In this initial task I expect to have:

• dockerized development environment
• fresh and cleaned Laravel installation ready-to-run
• our common Github Actions added
• initial readme file

FAQ should be manageable from the dashboard. Every entry should have a proper question and answer, like here:

We need:

• studies modes database structure (with internal id and name) (eg. "studia stacjonarne")
• CRUD actions

As this is the first time I have launched this project, I see some small things that could be improved.

• Page titles - title of the page is the link of the page I am currently on - I'd like to have real title, like "Studenci" or something like that.
• Tooltips - I didn't know that this check icon is for making the semester active/inactive. Adding some tooltip would be really helpful.

• Delete icon - I think that trash icon will be better.
• Add some sorting/filters on index views.
• Add missing translation in validation attribute (password)
• Confirmation dialog - instead of traditional confirmation dialog like we have now

it will be cool to have "undo" feature like Google Gmail provides

• Adding course to semester - if no coursse/semester exists, select looks like this:

Things below should be configurable from the dashboard:

• university logo
• primary and secondary color for theming

404 page should be designed in funny way and implemented in the project.

Current 404 page:

Courses should be visible for guests:

• on /kursy page with nice table
• on /kursy/{id} pages with course details

Table should include course code, full name, assigned field, semester number, form. Active courses should go first.

This is related to #10 and should be done after implementation of this task.

I'd like to have seeded real (or almost real) data in the database:

• students
• courses
• semesters
• fields
• semester courses

Contact info should be manageable from the dashboard. That includes:

• university email
• optional github handle
• optional alternative channel (like slack URL or linkedin profile)

We need:

• courses database structure (with internal id, abbreviation, full name, WYSIWYG description, semester number (not semester relation!) to chose and relations to field and form)
• CRUD actions

Current solution:

In current solution course has a field "is active" but I would move it to separate entity.

We need a dashboard layout designed. Right now it look like here:

This could be implemented as separate view or as a part of #11. I would like to have a grid with:

• list of all students in group in rows (sorting would be cool!)
• list of columns defined for every group (maybe columns should have types like "nullable boolean", "classic grade", "text", "final grade"?)

Current solution:

Grades page should:

• be available under \oceny page
• provide a form where student should choose semester of interest, course from courses attached to the selected semester, group from groups attached to the selected course and his index number
• for existing student a matrix with all grades should be shown
• all other students names should be truncated and unidentifiable (GDPR) and maybe randomized
• selected items in the form should be added to URL
• nice to have: next to the index number input there could be "Remember me (in cache)" checkbox

This is related to #11 and #12 and should be done after implementation of these tasks.

Application should have proper titles. This looks bad without any HTML base title and favicon:

FAQ items should be visible for guests on /faq page.

This is related to #14 and should be done after implementation of this task.

This will be more complex than typical CRUD.

We need:

• a connection between semesters and courses, eg. course "Projektowanie i programowanie obiektowe I - L" is conducted in "semestr zimowy 2023/24"
• every course in semester should have multiple groups, eg. "s2INF1(1)"
• every group should have multiple students assigned

Current solution is a little different, because there's different view for all groups, but I find it little unhandy:

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• - Update dependency @typescript-eslint/eslint-plugin to v7
• - Update dependency @typescript-eslint/eslint-plugin to v8
• - Update dependency @vitejs/plugin-vue to v5
• - Update dependency eslint to v9
• - Update dependency laravel-vite-plugin to v1
• - Update dependency primevue to v4
• - Update dependency ubuntu to v22
• - Update dependency vite to v5
• - Update docker/build-push-action action to v6
• - Update postgres Docker tag to v16
• 🔐 Create all pending approval PRs at once 🔐

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• - Update all non-major dependencies with digest and pinDigest (@formkit/auto-animate, @headlessui/vue, @heroicons/vue, @inertiajs/inertia, @tailwindcss/forms, @tailwindcss/typography, @typescript-eslint/eslint-plugin, @vitejs/plugin-vue, actions/cache, actions/checkout, actions/setup-node, appleboy/scp-action, appleboy/ssh-action, autoprefixer, blumilksoftware/action-pr-title, blumilksoftware/codestyle, composer, composer/composer, docker/build-push-action, docker/login-action, docker/metadata-action, docker/setup-buildx-action, dompurify, eslint, eslint-config-prettier, eslint-plugin-tailwindcss, eslint-plugin-vue, fakerphp/faker, guzzlehttp/guzzle, laravel-vite-plugin, laravel/framework, laravel/sanctum, mockery/mockery, node, nunomaduro/collision, php, phpunit/phpunit, postcss, postgres, primevue, quill, redis, shivammathur/setup-php, spatie/laravel-options, stevebauman/purify, tailwindcss, vite, vue)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• - Update dependency axios to v1.7.4 [SECURITY]

Vulnerabilities

Renovate has not found any CVEs on osv.dev.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

We would like to have additional way of login to the management system.
It should allow us to :

• login with email without password.
• it should send as link to authorize the login session, we wanna have the ability to authorize the session from other device than the one we trying to log in from. For example : i try to login from university PC and i wanna authorize the login session from my smartphone
• login session should be set for limited time like in bank applications.

News should be manageable from CRUD panel like in current solution:

I would like to type "zolw" in search field and receive student names "Adam Żółw". For that we would need to drop accent sensitive search in Postgres.

ref: https://stackoverflow.com/questions/11005036/does-postgresql-support-accent-insensitive-collations/11007216#11007216

We need:

• fields database structure (with internal id, abbreviation and name)
• CRUD actions

Current solution:

Main page should contain:

• configured in dashboard data like name, surname, university name, etc.
• biograms
• maybe some nice counters?
• maybe some shortcuts to contact page?

Right now data are hardcoded, but of course they should came from the database or maybe some cache engine.

In general system should have only one user for now: administrator. We should provide:

• a way to log in
• a way to log out
• a way to change password
• a structure to protect dashboard (designed in #3) from other users than administrator

Right now it look like this:

Dashboard navigation should be dynamic.

Maybe it's not the of of this pull request, but it is so little thing that we can fix. I mean, when I click "Studenci", in the menu "Dashboard" is highlighted, not "Studenci"

Originally posted by @EwelinaSkrzypacz in #45 (review)

We need:

• students database structure (at least internal id, index number, name, surname)
• searchable (by names and numbers) list of all students
• form to add new student
• form to edit existing student
• a way to delete student

Current solution:

Things like below should be ready to enable and disable per application instance:

• biograms on main page
• news section
• FAQ section
• contact section?

Contact page should be visible for guests on /kontakt page and it should contain:

• huge and linked email to the teacher
• linked github icon with handle
• all additional forms of contact defined in the dashboard (Linkedin profile, slack channels and so on)

This is related to #13 and should be done after implementation of this task.

We need:

• discuss if we need it in code as enum or in database? if in database, then:
• course forms database structure (with internal id, one-letter-abbreviation and name) (eg. "L" -> "laboratorium")
• CRUD actions

I would like to have designed layout for student section. Right now it looks like that:

Main page (as described in #23) should:

• be configurable by sections (administrator should have option to disable any section)
• sections should be: landing, about me, counters, contact; maybe something else?
• should have fillable "about me" columns
• should have fillable counters

We need to add Renovate to the repo

News should be visible for guests:

• on /aktualnosci page with pagination/filtering by year maybe
• on /aktualnosci/{id} pages with news details and buttons to share

This is related to #15 and should be done after implementation of this task.

It would be nice to have a test environment somewhere. I would like to deploy on main merge.

We need:

• semesters database structure (with internal id, name and status)
• CRUD actions
• only one semester should have active status

Things below should be configurable from the dashboard:

• teacher name and surname (#65)
• teacher email (#65)
• teacher titles (#65)
• university name (#65)
• department name (#65)
• university logo?
• maybe some primary color for theming?