final client meeting

showing the new features first
- as said last time
  - documents
    - begin by focusing on new features
  - not fully optimized yet
    - what's possible at this stage
  - next term with these features
    - let us focus on exploring what can be achieved
  - screen shared 1:15
- we are in the admin panel right nonw
  - zhao is sharing
- upload videos
  - demonstrate
- title
  - course2
    - and then
  - module
    - what lesson you want to be
  - create the modul
    - inside the module you can video
  - different modules
    - it's ine
      - you will be creating module first
    - then
      - you can
    - go back
  - it will be more user friendly
    - click on your course
  - add a description
    - video
  - for now how the video works
    - vimeo url
      - the video will be diplayed in the webstie
    - no direct uploading
  - zhao
    - it's not working on the elarn page
      - slides presentation
    - documentation
      - we require for smooth transition
    - key achievements
      - we are nikawiy productions
    - it has been doing great doing the project
      - start with agenda
    - do project summary
      - key achievements
        
        outsstanding work
      - overview
        
        documentation
      - user manual
      - technical manual
      - transition plan
        
        recommendations
      - overview
        
        client nikawiy productions
      - business objective: create a cms platform and learning application for mocassin
        
        preserve history
        
        video upload, manual upload
        
        key chievements
        
        video upload and management
        
        modulee and lesson creation
        
        contact form integration
        
        admin features
        
        (feedback view, contact form update, admin login)
        
        basic wwebsite pages nav landing
        
        abouts us
        
        delieverables
        
        personas
        
        wireframe
        
        project charter
        
        tech
        
        ma
        
        transition plan
        
        business process map
        
        olayykina
        
        thank you saurav
        
        outstanding work
        
        migration
        
        many bugs
        
        on the website
        
        that needs to be fixed
        
        team
        
        finish deliverables
        
        full requirements
        
        test plan
        
        test the
        
        viability of our website
        
        worked on that
      - diagram
        
        finished
      - ERD
      - branding finalization
    - filling placeholders
  - transition plan
    - detailed steps for continuing or completing the project
  - user manual guidance for using the website
- technical manuals
  - backend and development details for future developers
    - steps for the next
      - i'm going to hand over to saurav
    - a user manual is a guide that explains how to use the features and functionality of the website
      - admin
    - how
      - i think
    - saurav can you hear me
      - i can hear you
    - end users
      - came to know how it works
    - function of the website
      - ok
        
        so basically this is the document
        
        six basic steps
        
        introduction of the website
        
        how it's going to work
        
        and beneift the end users
      - system requirements
        
        browser
        
        introduction
        
        system reqs
        
        website nav
        
        key features
        
        user actions
        
        screenshots
        
        how to upload video for the admin
      - how to get to different pages of the website
    - how is the admin going to respond to that thing
  - for users
    - really going to tell the users
      - how they're going to tell the feedback
    - go to next session
      - we'll be ending this document
        
        where screenshots
      - of this users
        
        i would like to pass on to zhao
      - ok
    - techinical manual
      - is generated for the developer
        
        to
        
        to
      - reference how to
        
        put this into the local
      - the first statement
    - developer environment
      - let me share my screen
    - requirements
      - about this system
    - desktop
      - or laptop
    - tablets
      - smartphone
    - modern web browser
      - browser like chrome
    - safari
  - internet connection
    - should be minimum speed of
  - 5mbps
    - is recommended
      - streaming tutorials
    - steps
      - should be
    - from the end
      - nextjs
        
        database
      - superbase
        
        clerk
      - tailwind css
    - admin panel
      - adminjs
    - this CMS works on windows 10 or 11
      - mac os
        
        linux
      - install
        
        load the js
      - visit
        
        nodejs official website
      - LTS version
        
        for your operating system
      - windows or mac os
    - choose a version
  - suited for your operating system
    - run the installer, open the terminal
  - show the version
    - node
  - yes
    - for the version control of this
      - website
        
        we used git
      - if you want to install this
        
        you need the github url
      - go to our repository
        
        then clone the url
      - stick it to the right folder
    - install the git
      - check the git version
        
        set it to the right place
      - if it's not installed
        
        go to the official github website
      - for your operatin gsystem
        
        right version
      - for this website
        
        vscode
      - also
    - we recommend
      - install the following instructions
    - prisma
      - tailwind
    - external dependence
      - superbase
        
        postgres database hosting
      - you should sign up for super base
    - create an account
      - go to
        
        the settings
        
        database
        
        collections stream
      - collections stream to our local
    - provide database URL
      - make the local file
    - clerk
      - we should also have a clerk account
    - we need to copy our
      - secret and public keys
    - we need to add those keys to the local file
  - for the prisma
    - objected
      - relation
        
        mapping
      - object
        
        superbase
        
        to simplify database interaction
        
        migrations
        
        prisma
        
        already a built in function in this project
        
        we still need to install
        
        the database is working
      - we should install the prisma
        
        to initialize
        
        the development locally
        
        then,
        
        through the configuration
        
        we should define your database modal
      - define database schema
        
        email
        
        password
        
        user
        
        apply the schema changes
      - we can use
        
        prisma
        
        migrate
        
        apply
        
        schema changers
        
        to the database
      - if you want
        
        to
        
        detailed guidance of how to use prisma
        
        we can go to prisma documentation
        
        for this
        
        CMS website
        
        Vimeo
        
        URL
        
        embed
        
        uplpoad
        
        create our content
        
        upload our
        
        to vimeo
        
        like this
        
        copy the url
        
        each link of the video
      - copy link
        
        we should save those links to CMS main panel
      - so we can upload the video
        
        how we run this application
        
        first we need to open VSCode
      - terminal -> gitbash
        
        copy
      - git clone url
        
        navigate to the correct folder
        
        nikaway .env.local
        
        add environments variables
        
        copy supabase url
      - apply those new changes
        
        to our superbase database
        
        using our following command
        
        x prisma
        
        four steps
        
        database
        
        populate the database with the initial data
        
        seed data
      - then we can start the application
        
        start the application
      - npm run dev
        
        localhost
      - main page
        
        of our application
      - if you want to start the admin cp
    - navigate to the admincp
  - right now we have some issues or bugs
    - we don't have times to fix yet
      - video playback issues
    - if the vimeo embedded link is not correct
      - it's a copy
    - copy link
      - it shouldn't be a copy embed link
    - it won't display
      - verify links
    - before adding them to the admin panel
      - vimeo setting
    - share to public
      - some issues with the admin panel performance
        
        if the sate
      - is too large
        
        the website can response times
      - high response time
        
        patch
      - limiting to the data size
        
        to our website
      - we have some information
    - troubleshooting
      - console log for debugging
    - terminal as well
      - to monitor logs for unexpected behaviour
    - for the troubleshooting
  - we provide some
    - some links
      - for this application
        
        documentation:
        
        NextJS
        
        Superbase
        
        github repo
        
        if you are having some issues you can go to these links
        
        to check for reference
        
        yeah
      - ok
        
        ok
      - ok
    - 23:12
      - olaaykina
    - transition plan
      - we need to
    - plan
    - ensures
    - the
    - smooth
    - transfer
    - of
    - project
    - work
    - between
    - student
    - project
    - teams
    - it outlines the current status of the application, updates t orelevant documentation, and recommendations for seamless onboarding
  - technical manual
    - understand everything we've done
  - requirement
    - admin is able to upload the videos
      - upload the videos
    - able to
      - we meet most of the requirements
      - meet all
        
        contact form is in progress
        
        feedback view is in progress
        
        navigation is in progress
        
        about is in progress
        
        change from admin
        
        contact information
        
        change the contact
      - complicated
        
        navigation
      - from one point to another
    - landing page
  - we already completed that
    - person asked
  - wireframe
    - completed
  - the business process map
    - core functions
  - we need to fix some bugs
    - time for us to fix those
  - all the documents
    - test plan
  - ERD
    - is not yet completed
  - send us the
    - colour coding of the website
  - send some of the images
    - videos
  - so
    - nesting
  - for you not to complete
    - fill in those
  - website currently
    - user manual
      - instructions to
    - navigate from
  - creation
    - so
  - also the user manual
    - overview
      - also the
        
        techinical manual
      - integrational details
    - video streaming
      - nextjs
    - git
      - also
    - need to mention
      - work on this project
    - nextjs
      - language
    - go and language
      - finalizing
        
        tesing
      - functionally
        
        also
      - a completely full
        
        test plan
        
        ERD
        
        branding, aligned
      - logo
    - position
      - to access github
    - login
      - get assets
        
        provided
      - in conclusion
    - this transition plan
  - hand off meeing
    - walkthrough
      - completed features
      - pending tasks and documentation with incoming team
    - hand off next steps
      - inspect
    - code
    - resources manuals
      - no documents // -> #relevancy
    - #Relevancy
      - Our client is a media production company. What is the best possible things to present to her, both successes and failures?
        
        -> #Detail is fine, as long as relevancy is adequate, and it doesn't try to go too far into the weeds on it. As long the justification and clarity is there.
        
        36:20
        
        Cross team hand off -> Isiah
      - Detailing
    - techinicalities
      - #Techinicality
        
        #handover
        
        Thorough
        
        bug.
        
        bug.
        
        #Mitigation
        
        #Haphazard
        
        #Bandaid
        
        #temporary_fix
        
        #Unintended_Effects
        
        #Technical_Manual
        
        associated
        
        to specific account
        
        you probably don't want to have one of those
      - superbase
    - link to instructions
      - superbase account
    - superbase

There is a lot of ecosystems we're using here. There's a lot of layers of abstraction. So, using something like Microsoft Co-Pilot is more than adequate here. Of course, we recommend Stack Overflow a bit more granular, or debugging. Firstly, you should at least familiarize yourself with NextJS and React documentation, before considering the former.

Supabase handles the create, read, update, and deletion of our tutorial system. We're using PostgresSQL, which has some slight semantic differences, very minimal, so if you understand MySQL or have used SMMS, the language is about the same, you'll want to familiarize yourself on the few semantic differences.

To interact with our database, we're using an ORM, an object relational model. It allows us to use a modelling style of creating database, which also allowed us to create the database without an ERD. The syntax is also much clearer for when interfacing with

The way we approached this was develop as you go, which isn't necessarily ideal, but for such a short time, we chose frameworks that certainly can output a great product, especially when it transitions smoothly. The transition plan is the most important part of this project. If the next developer understands exactly where to go, and is guided to the point of reasonable knowledge, or is equipped with the know how of knowing where to look. Which is half the battle sometimes, for even skilled programmer, or developer.

I've designed this transition plan to bridge the divide in language that we've used here. It's a series of frameworks, correct? I've made my best recommendations possible to point the new developer in the correct direction and make them stay there, until of course, they're ready to transition themselves.

What documentation is available for your project, and where can it be accessed?

Aggregate
- NextJS documentation / React documentation ✅
- Microsoft Co-Pilot ☑ #Overall #Best
  - Cursor // ✅ #NextJS
- Superbase -> #Database #Core #Postgres
- Prisma -> #Database #Interface
- AdminJS -> #Control_Panel #Framework
- Stack Overflow -> #Granular #Debugging

Which of your project tasks are currently in progress, and what is their status?

Navigation is
- there's complications in the code somewhere, for the navigation. what that complication is? It's probably Saurav not really being too savvy with css, or just whatever. Are there any outstanding issues or risks that need attention for your application?
The outstanding issues or What knowledge transfer is needed for your client? Are there specific areas of expertise or critical information that you would like to bring to your client's attention? Are there any specific configurations or setups that need to be replicated for your client? What testing activities have been conducted for your application, and what is the status of the test results?

#Concise #Deployment #Installation #Transitional #Transient #Nature

So, what would I tell people if I wasn't there to help them.
- Requirements Document for review
  - ==Are they done yet? Why or why not? What is in progress. What did you fail to achieve.==
    - Navigation. // #Assume #Failure
      - bug: the url must be clean // no additional for

superbase

Deploy

Install

Transition