Giter Club home page Giter Club logo

website's Introduction

Getting started

To get started with this site, first install the npm dependencies:

yarn install

Next, run the development server:

yarn dev

Finally, open http://localhost:3000 in your browser to view the website.

Customizing

You can start editing this template by modifying the files in the /src folder. The site will auto-update as you edit these files.

Global search

This template includes a global search that's powered by the FlexSearch library. It's available by clicking the search input or by using the ⌘K shortcut.

This feature requires no configuration, and works out of the box by automatically scanning your documentation pages to build its index. You can adjust the search parameters by editing the /src/markdoc/search.mjs file.

Learn more

To learn more about the technologies used in this site, see the following resources:

website's People

Contributors

aryanmehrotra avatar srijan-27 avatar naveen-bandela-au2 avatar snyk-bot avatar leidorf avatar ccoveille avatar arpy8 avatar kushrajpurohit-zs avatar rakshita-zs avatar shelbybosss avatar officeneerajsaini avatar rokerzfirst101 avatar

Stargazers

 avatar  avatar  avatar Rishitha Nandanapu avatar Vipul Rawat avatar  avatar  avatar Akshat Singhal avatar

Watchers

 avatar  avatar

website's Issues

Automated Greeting Workflow

I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet users who create new issues or pull requests in this repository. The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."

Please assign this issue to me.

Add GitHub Desktop Contribution Instructions

I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.

Enhancements and Corrections for README.md Content

The README.md file for our project contains valuable information for users to get started and customize the site. However, there are a few areas where improvements can be made for clarity, consistency, and readability. This issue is raised to implement enhancements and corrections to the README.md content, including grammatical fixes, improved instructions, link formatting, and additional clarity in explanations. The goal is to ensure that users can easily understand and follow the instructions provided in the README.md file.

As a participant of GSSoC (GirlScript Summer of Code), I'm interested in taking on this issue to contribute to the project's improvement.

Assign this task to me.

Missing Code of Conduct File in Repository

Currently, the repository lacks a Code of Conduct file, which is an essential component for fostering a healthy and inclusive open-source community. A Code of Conduct serves as a guideline for expected behavior, ensuring that contributors and participants feel safe, respected, and valued within our community space.

Kindly assign me this issue, so i can work towards it under GSSOC 24

Add content in main_test.go

Currently, on the homepage main_test.go is static, allow it to be switchable with correct integration test written for the same.
With both bottom and side scrolling
Screenshot 2024-08-02 at 2 05 58 AM

Add templates for issues

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template.
you can refer this: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Some suggested prompts/questions you can add to a “Report Bug” template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug
Some suggested prompts/questions you can add to a “Feature Request” issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/issues/new/choose
Click on Get Started button and copy the template to your

Add PR template

I would like to add a pull request template for this repository. Please assign me this issue under GSSOC'24.

Learn.md

Learn repos should have a LEARN.md file to teach student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/Learn.md

Add Topics

In GSSoC'24, GitHub Topics will help the discoverability of your project.

I see that you already have great topics on your repository!
I would recommend adding the name of the company like the software you use to build like "vs-code, ghdesktop" to improve your discoverability.

If you are happy with the topics you have, feel free to close this issue. 👍

[Feature Request:] Conversion of Javascript code to Typescript code

Why Ts and why not pure vanilla js?

TypeScript stands out from vanilla JavaScript with its outstanding features like static typing, interfaces, enums, generics, union types, type guards, and decorators. These features collectively enhance code quality, readability, and maintainability, while also significantly reducing the occurrence of bugs and errors. By providing a more structured and expressive way to write code, TypeScript empowers developers to build complex applications with confidence, offering a smoother development experience and facilitating collaboration within teams.

Why I am the right fit for this project
I've successfully utilized TypeScript across projects integrating React-Three/Fiber, React-Three/drei, Three.js and React Spring into Next.js for immersive 3D websites, implemented WebRTC and sockets in TypeScript codebases, and built scalable solutions with Gatsby, GraphQL, and TypeScript, all with a focus on robustness and efficiency. I think I have required know-how on how to handle the TypeScript codebases.

Here is how I will handle my js to ts conversion

  1. Install TypeScript: I will begin by installing TypeScript globally using npm or yarn.
    npm install -g typescript

  2. Rename Files: Change the file extensions of all JavaScript files to TypeScript files. For JSX files, I will change the extension to .tsx.

  3. Enable TypeScript Configuration: If project doesn't have a tsconfig.json file, I will create one using the following command:
    tsc --init

  4. Start Converting: Begin converting my JavaScript code to TypeScript by following these steps:

  • Static Typing: Add type annotations for variables, function parameters, and return types to enhance code reliability.
let firstName: string = 'John';
let age: number = 30;

function add(a: number, b: number): number {
  return a + b;
}
  • Interfaces: Define interfaces to describe the structure of objects, promoting code clarity and maintainability.
interface Person {
  firstName: string;
  lastName: string;
  age: number;
}

let person: Person = {
  firstName: 'John',
  lastName: 'Doe',
  age: 30,
};
  • Clean Class Design: When converting existing JavaScript classes to TypeScript, refactor them to adhere to clean and object-oriented design principles, ensuring the new TypeScript codebase is more organized and maintainable.

  • Enums: Replace constants with enums to improve code readability and maintainability.

enum Color {
  Red,
  Green,
  Blue,
}

let c: Color = Color.Green;
console.log(c); // Output: 1

  • Generics: Utilize generics for writing reusable code that can work with a variety of types, enhancing code flexibility and scalability.
function identity<T>(arg: T): T {
  return arg;
}

let output = identity<string>('hello');
console.log(output); // Output: hello
  • Union Types: Specify that a variable can have one of several possible types, enhancing code flexibility.
let value: string | number;
value = 'hello';
console.log(value); // Output: hello
value = 42;
console.log(value); // Output: 42
  • Type Guards: Narrow down the type of a variable within a block of code, ensuring type-safe operations.
function printName(name: string | string[]): void {
  if (typeof name === 'string') {
    console.log(name.toUpperCase());
  } else {
    console.log(name.join(', '));
  }
}

printName('John'); // Output: JOHN
printName(['John', 'Doe']); // Output: John, Doe
  • Type Inference: Allow TypeScript to infer the type of a variable based on its value, reducing the need for explicit type annotations.
let x = 3; // TypeScript infers that x is of type number
console.log(x); // Output: 3
  • Optional Chaining: Safely access nested properties without worrying about null or undefined values, preventing runtime errors.
interface Person {
  firstName: string;
  lastName?: string;
}

let person: Person = {
  firstName: 'John',
};

console.log(person.lastName?.toUpperCase()); // Output: undefined
  • Decorators: Add metadata to classes and their members to enhance code functionality without modifying the original code, commonly used in frameworks like Angular, but if needed I can add this to the current project.
@sealed
class BugReport {
  type = "report";
  title: string;
 
  constructor(t: string) {
    this.title = t;
  }
}

function sealed(constructor: Function) {
  Object.seal(constructor);
  Object.seal(constructor.prototype);
}

When @Sealed is executed, it will seal both the constructor and its prototype, and will therefore prevent any further functionality from being added to or removed from this class during runtime by accessing BugReport.prototype or by defining properties on BugReport itself.

Additional things I will consider While converting the Js codebase to Ts codebase :

  1. Resolve Compilation Errors:
    As I convert your code, TypeScript might raise compilation errors due to type inconsistencies or other issues. I will make sure to address these errors one by one by refining your type annotations and ensuring compatibility with TypeScript's type system.

  2. Incremental Adoption:
    If the codebase is extensive, I will consider adopting TypeScript incrementally. I will start by converting individual modules or components and gradually expand the TypeScript coverage across the project.

  3. Testing and Validation:
    Test the TypeScript code thoroughly to ensure it behaves as expected. Use TypeScript's type system to catch errors early in the development process, reducing the likelihood of runtime issues.

  4. Continuous Integration:
    Integrate TypeScript conversion into continuous integration pipeline to ensure that new changes adhere to TypeScript standards and do not introduce regressions.

  5. Documentation and Training:
    Update project documentation to familiarize team members with TypeScript features.

Girlscript Summer of Code Introduction/Tracking

👋 Hi @gofr-dev,

I am Prince,web developer(Core Team) Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program

Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.

As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.

This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you :octocat:

Addition for a Code Playground

Dupl : gofr-dev/gofr#605

@hollermay
I believe it should have a playground to code same we have coding playground at websites to test tools or any programming language and if we add some basic code to execute will also be a good way to create engagement with suggestion codes below the playground or at a sidebar.

Missing CONTRIBUTING.md File in Repository

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.

Could you please assign this issue to me under GSSOC 24.

Add issues

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

Add issues of varying difficulty to the repo often. you must add the tag GSSoC'24, Level 1, Level2, Level 3 good first issue etc.
How we cacluclate the Scores on Leaderboard: Every PR one point
Level 1: 10 points
Level 2: 25 points
Level 3: 45 points
Try to add some documentation issues as well it would be easy for beginner contributor to explore opensource through your repo.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.
Reference https://github.com/Recode-Hive/Stackoverflow-Analysis/issues

Enhance README.md

Update readme.md with website UI, and add different tags as needed.

Filter genuine email

Security Feature

In your application anyone can enter using temporary or disposable email.
I will add a feature so that no one could create an account using temporary or disposable email.
It will allow only genuine users in your database.
It will help to avoid any bot.
Assign me this work under GSSoC24, I will implement it.

Update Title of all different pages

Currently, Title for all different pages is GoFr - An oppinionated Go Framework.

It has to be updated like the following

Example:
Title for https://gofr.dev/docs/quick-start/connecting-mysql: Gofr MySQL | Connect MySQLFrom Golang
Title for https://gofr.dev/docs : GoFr | Documentation.

Add blog page

Add blog page where, we can add links to blogs about gofr on the web!

Missing Code of Conduct , Contributing , Issue guidelines file .

Hey @gofr.dev , Including a README file, a Code of Conduct, and a Contributing file in your repository is essential for fostering a collaborative, organized, and respectful project environment. Here’s why each of these documents is important:

Kindly assign this issue to me under GSSoC'24 , for better User/Contributor experience .

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.