In the solutionsTemplate.html file, there is currently a dummy image.
Replace it with an html <pre> & <code> tag and style it to match the image.

In the mobile version of the landing page, add the side menu as shown in the designs here.

The following items should be included in the contents:

• A brief description of the project.
• How you can help with the project.
  — By correcting any errors.
  — By resizing and optimising any file.
  — By incorporating new features.
  — By removing any codes that are redundant.
  — As well as working on any issues we place there on a regular basis.
• How newcomers can become involved by raising issues or viewing labels on existing issues such as good first issue, up for grabs, and open to all.
• How to fork, clone, branch, and host locally, as well as how to edit the contents
• Some useful Git and GitHub commands for contributors
• A overview of Hacktoberfest and what it implies for the contributors.
• Change the file name to CONTRIBUTING.md.
• And you are free to add anything else to it aside from these.

NOTE: Make sure to use appropriate markdown syntax and emojis.

Here, you and I can discuss how we can add new and user-friendly features to this static template so that coders like us can utilise it more easily.

• You might leave a comment below if you have a new and original idea about this.
• If your suggestion is useful to the users, I'll turn it into an issue and assign it to you.
• The README.md and introductionAndFeatures.md files in the Assets folder can be used to learn more about this project.

I'm looking forward to hearing about your fantastic ideas.

Create the landing page in line with this design, using html and CSS, and keep these points in mind:

• You can copy all of the photos from the figma file as .svg and save them in a folder called Assets/Images, then utilise them in the .html file.
• The HTML file should be placed in the Markups folder, and The CSS file should be placed in the Styles folder.
• There should be no redirections or links in any of the buttons in footer and header.

Keep these in mind while you work on making the site more responsive.

• Use flex boxes and relative units instead of using px to make the lazyCode site mobile and tablet friendly.
• You can check out the figma designs here.

• Add a boilerplate in Assets/Code so that there is no need for creating headings for every question added
• The boilerplate should be in .md format
• The sample format can be copied and used irrespective to the question platform

Due to the change in image names and paths, several links are broken; please fix them.

Assign me...i can do that

We currently have dummy lorem ipsom text on the home page, which you can see in the design here, and we want to replace it with an actual introductory paragraph as well as feature points, As a result, we're looking for cool writers to share their thoughts.

• Some helpful hints for introduction and features can be found in the readme section and in the designs, and please feel free to discuss them in this issue.
• In the Assets/Features folder, place the introduction paragraph and feature points in a file called introductionAndFeatures.md.
• The following should be included in the file:
  -- Paragraph of introduction
  -- Lists of qualities of web app

Keep these in mind while you work on making the site more responsive.

• Use flex boxes and relative units instead of using px to make the lazyCode site mobile and tablet friendly.
• You can check out the figma designs here.

Hi,
I have been doing competitive programming for a few years now. I would like to add some codeforces/codechef problems and their solutions to your repository for my hacktoberfest 2021 contribution.

But I wanted to know if I could add some of my coding problems and solutions from CSES as well?
CSES is known to be a great resource with selected problems that teach everything from the basics to the advanced very quickly.
You can find world champions attempting CSES problems.

Let me know. Thanks.

• As shown in the designs, there are three small link buttons on top of the home page as part of the new design adjustment.
  Namely Codechef, Codeforces and Leetcode button.
• These buttons should be added to the homePageDemo.html file.
• Fix the bottom buttons as well. (i.e. Codechef, Codeforces, Leetcode, Hackerrank and Miscellaneous)

• Add coding questions and their solutions from sites like Codeforces, HackerRank, Leetcode, Codechef, and miscellaneous that you answered on your own.
• They should be placed in the Assets/Codes/platformName* folder (where platformName should be Codeforces, Hackerrank, Leetcode, and so on.)
• The file name for the questions should be the question name in camelcase (Ex.- aGrowingTree.md).
• The file should be a .md file, and the contents should be as follows:
  [NOTE: Follow the boilerPlate.md template included in the Assets/Codes folder.]
  -- The name of the question,
  -- the language (C++, Js, Python, etc. ),
  -- the question platform (Codeforces, Hackerrank, etc. ),
  -- and finally the question and its solution,
  -- explanation of solution is optional.

These questions will be added to the web app after the template is complete.

Keep these in mind while you work on making the site more responsive.

• Use flex boxes and relative units instead of using px to make the lazyCode site mobile and tablet friendly.
• You can check out the figma designs here.

Create the home page in line with this design, using html and CSS, and keep these points in mind:

• leave the dummy text unchanged.
• You can copy all of the photos from the figma file as .svg and save them in a folder called Assets, then utilise them in the index.html file.
• For the time being, the contributors link in the upper right corner should not include any links.
• Buttons include Codeforces, Leetcode, hackerRank, CodeChef, and Miscellaneous.

Create the Questions page in line with this design, using html and CSS, and keep these points in mind:

• Leave the dummy text unchanged.
• You can copy all of the photos from the figma file as .svg and save them in a folder named Assets before using them in the subsequentQuestions.html file. (the naming should be the same for all questions pages, i.e. hackerrankQuestions.html, leetcodeQuestions.html, and so on.)
• Top right side dropdown buttons are Codeforces, Leetcode, hackerRank, CodeChef, and Miscellaneous.

Create the solution page in line with this design, using html and CSS, and keep these points in mind:

• leave the dummy text unchanged.
• You can copy all of the photos from the figma file as .svg and save them in a folder called Assets, then utilise them in the solution.html file.
• Top right side dropdown Button include Codeforces, Leetcode, hackerRank, CodeChef, and Miscellaneous.
• The back and next are the buttons located below the compiler at the bottom.
• For the time being, add a dummy compiler image as shown in the design.

Keep these in mind while you work on making the site more responsive.

• Use flex boxes and relative units instead of using px to make the lazyCode site mobile and tablet friendly.
• You can check out the figma designs here.