Along with the notes on daily-code, every individual has there own some points to add in the notes. We can create a note button to add our points which we want to add on that particular part . It should reflect to particular user only.

Some pages on https://projects.100xdevs.com/ crash randomly. Goes away when you refresh

shove it in packages for now

`export const editProblem = onCall(async (request) => {
const problemId = request.data.problemId;
const title = request.data.title;
const description = request.data.description;
const type = request.data.type;
const notionDocId = request.data.notionDocId;

const problemRef = db.collection("problems").doc(problemId);

await updateDoc(problemRef, {
    title,
    description,
    type,
    notionDocId,
});

return {
    success: true,
    id: problemRef.id,
};

});
`

When we click on download pdf button, instead of downloading the document in pdf format, a printing document interface pops up which prints a blank white page as shown below.

then, in the background all slides are combined together but the pdf does not get downloaded.

I think It would be nice if we had a feature that lets us save the slides as a PDF file so that we can store it locally and access when without internet ( also in case of server down ).

Right now we have code and blog type
We need a simple `MCQ question type which'll have a blog on the left, and question on the right that'll help the user revise the topic

1. Needs to have a new backend collection for MCQ questions (doesnt need to normalize can have everything in the same doc)
2. Need a new submissions collection that stores the users submissions
3. Frontend needs some sort of confetti when the user selects the right option

When click on Download it will navigate into another tab and content is generated but there is error in generating pdf

In mobiile view responsiveness problem

website currently only have "previous" and "next" page option, in case if anyone want to go to any specific page the need to click next of previous as per the page, there should have a page number input box that should accept the page number and forward user to that page.

pros:

1. easy to get through the content.
2. decrease the number of reloads( if a user is on page 1 and want to go to page 30 then the user will have to press "next" 29 times, which will reload the website 29 times, whereas it can be done in single click only if it have jump to page feature)

Need to Fix

Issue is this

fixs #23 #31

shadcn link -> https://ui.shadcn.com/docs/dark-mode/next

When we clicks on breadcrumb link it's redirecting to 404 page.

while setting this project . I am getting error

(node:76266) NOTE: The AWS SDK for JavaScript (v2) will enter maintenance mode
on September 8, 2024 and reach end-of-support on September 8, 2025.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check blog post at https://a.co/cUPnyil
(Use node --trace-warnings ... to show where the warning was created)
(base) riz@riz-Aspier-XXXX:~/Desktop/Open Source/harkirat-projects/daily-code/my-turborepo$ .

Should appear side by side

1- Login with buttons images are not rendering.
2- It's a very basic design we can make it a good looking.

Categories are going to be

1. Web Development (Basics)
2. Web Development (Advance)
3. Devops
4. Web3

Description

Currently, our project setup involves unnecessary lock files, causing confusion and overhead, especially for contributors unfamiliar with the project structure. By migrating to Yarn and optimizing lock file management, we can streamline the setup process and enhance the development experience for all contributors.

Background

Lock File Overhead: The presence of redundant lock files (e.g., package-lock.json) complicates the project setup and can lead to version conflicts.

Yarn Adoption: Yarn offers advantages such as deterministic installs and improved performance, making it a preferable choice for managing dependencies.

Contributor Experience: Simplifying the project setup with Yarn and ensuring efficient lock file management will lower the barrier to entry for new contributors and improve the overall development experience.

Objective

Migrate to Yarn: Transition the project from npm to Yarn for dependency management.

Update README: Provide clear instructions in the README.md for setting up the project using Yarn

1. Fix the text color
2. Use shadcn.ui Button component
3. Fix the svg icons
   

As there are more and more tracks coming every week, displaying all the tracks in the homepage maynot be a good idea. It is good to map the courses in a particular folder

such that the respective folder contains its tracks

I would like to work on this fix

Scrolling through the contents of slides, the cursor rests mostly on the bottom right side of the screen, it could be helpful if navigation to previous and next slides are available as an icon on the bottom right of each slide.

Enforce linting on PRs

To maintain a history of videos and their last played points, ensure that the playback position for each video is recorded upon the last viewing session.

In the current 100xdev App, if you watch a video and, either unintentionally or intentionally, view something else on your mobile or any device, returning to the video later results in losing your place. (ISSUE)

Implementing a zoom in and out feature for the content displayed in videos would be beneficial, especially when viewing videos on a smaller screen. This feature would enhance the user experience by providing the flexibility to adjust the content size according to individual preferences, making it easier to navigate and focus on details in a more user-friendly manner.

Steps to reproduce

1. Explore any of the tracks for example custom hooks
2. Change the them from light to dark
3. Reload the page.

Finding
The blogapp bar tends to maintain the dark theme but the rest of the page goes back to light theme

Expected behaviour

The whole track page should maintain the theme selected before page reload

I'm Attaching a video of the issue
reload_issue.webm

I feel like this'll just get harder and harder as time goes by

We don't have dependency on auth right now so the best time to move off of it

Let's migrate over to postgres + prisma and get rid of firebase completely

This is the schema of the DB right now -

Tracks

Problems

So the final DB should be like this -
Tracks
title
description
image
visible: boolean

Problems
title
description
type: "blog" | "code"

track_problems
id
problem_id
track_id
sort_order

Issue :- In AWS Deploying tracks, after getting .pem file , when we try to connect to virtual machine using ssh we get permissions denied.

For mac , it is easy to use chmod , but windows doesn't support "chmod"

Solution :
In windows 11 powershell I did run the below commands which will be equivalent to chmod

Note: first change the DIR to the folder where you have your .pem file named as key.pem

icacls.exe key.pem /reset
icacls.exe key.pem /grant:r "$($env:username):(r)"
icacls.exe key.pem /inheritance:r

@hkirat , please add the following code snippet to the track deck.

There is already a code type that shows code on the right, problem statement on the left
We need

Admin dashboard

Allow admins to put in

1. Problem statement
2. Title
3. Test cases

User side

User can see the problem statement on the left
Code editor on the right
Submit the code

After the code is submitted, it hits a HTTP Endpoint which runs all test cases one after the other
We can use judge0 for this, assume it is already deployed

Languages to support for now -

1. CPP
2. Javascript

hidden field on a track should mean it isn't exposed on the frontend.
For ex, I want to hide this track

using npm run dev gives error.

right now, notion gets light theme always
Pretty sure it was caused here - #43

To enhance performance and prevent unnecessary API calls to the backend, we can implement the following improvements on the lesson page:

1. Disable Prev Button on First Slide:
   When the user is on the first slide of the lesson, the Prev Button should be greyed out and disabled. This will visually indicate to the user that they cannot navigate to the previous slide since they are already on the first slide. Additionally, it prevents any accidental clicks that might trigger unnecessary API calls.

2. Disable Next Button on Last Slide:
   Similarly, when the user reaches the last slide of the lesson, the Next Button should be greyed out and disabled. This informs the user that they have reached the end of the lesson and cannot proceed further. Disabling the Next Button also prevents any unnecessary API calls that might occur if the user attempts to navigate beyond the last slide.

CC: @hkirat

Issue Already FIXED

@hkirat
-You are seeing light theme on refresh because of the key value pair in localstorage is there which is set to dark from previous code
if you remove the key value pair because it won't refresh on hard refresh on window
So just delete the key value pair and you'll see that the code is fixed

Description

On main project page, where all slides are present. On higher screen res the gap between column increases, but we are also able to click on blank space to select the slide in line (ss attached)

current behaviour:

Getting pointer cursor even outside the list item (in between column gap, specially when width increases)

Expected behaviour:

Should not able to open the slide if cursor is outside it. And list items should align horizontally centre on higher widths.

Steps to Reproduce:

• Go to https://projects.100xdevs.com/
• Press Ctrl/Cmd + '-' to increase the width/resolution.
• Hover between column gap (outside list item.) You will be able to select item and get pointer icon.

Environment:

prod

Currently Learning Paths are displayed in random order on the website, But if is displayed in sorted to date it will be better to navigate.

Left Arrow Key === Prev Button
Right Arrow Key === Next Button

when you are inside a project/learning path the back button on the browser will not take you to the original website which is frustrating.

Use

1. Login with google
2. Login with github