Is there any existing issue for this?

• I have searched the existing issues

Description

After clicking the contributor's profile. It's showing a 404 error. I added a screen recording please check

Screenshots

Any additional information?

I'm using Brave Browser

What browser are you seeing the problem on?

No response

Features Proposed

• Integrate Testimonial section
• Render Testimonials

Description

add the prev and next button to navigate between the previous and next contribution guide section

Screenshots

No response

Additional Information

No response

Description

The home page currently holds the documentation as a placeholder
that needs to be changed to more meaningful stuff about GitOpener

Screenshots

No response

Additional Information

No response

Describe

• Get total number of contributors from database
• Display total number of contributors

Description

hi maintainers. Kindly add some requirements such as adding GitHub org readme, support, banners etc.

• it helps newcomers to add value
• we can get more github contributors
• Trust
• best community

Now it's basic

Screenshots

Additional Information

No response

Description

Must have the introduction of GitOpener at the top
Use some screenshots

Screenshots

No response

Additional Information

No response

Description

Just add a security policy for the OSS project.

How to add?

click on the insights tab > then Community Standards > then click on propose In the security policy

Screenshots

Additional Information

No response

Describe

• In small devices menu icons are popping up while clicking on the theme change icon, That makes the UX awful

What would you like to share or ask?

As clsx library has the same and better potentials to handle class names of tailwindcss so using clsx would be better than manual conditioning.

Additional information

Try to replace each and every component that uses className attribute as a condition.

Features

• Add loading bar
• Add existing contributors page
• Create link for each contributor to navigate

Features

• Add a popular contributors section
• Design it
• Fetch Popular people from API
• Render them

Describe GitHub in your words,You can mention the basic functionalities of Github, Put a reason why Github.

Is there any existing issue for this?

• I have searched the existing issues

Description

Edit on Github button is not working on start contributing section. And showing 404 not found.

To reproduce
Go to
start contributing section of the web app
Click on
edit on github icon [+-]

Screenshots

No response

Any additional information?

Expected Behaviour
Redirect to github repository file with edit mode open

What browser are you seeing the problem on?

No response

Features

• add loading bar
• add theme context
• add dark mode
• modify all components according to theme

Description

Make separate Favicons for light and dark theme
we have one right here /public/favicon-dark.svg

Screenshots

No response

Additional Information

No response

• Added a CONTRIBUTING.md
• Fix broken links

Features Proposed

• Mention how can an contributor set up that project in their machine?
• Render Contribution Guideline
• Render Contributors Section, display few contributors with a view all link that navigates to /contributors

Description

This section will list feature/popular and beginner level opensource projects

Screenshots

Additional Information

maybe we can also add specific issues to grab in beginners section

• Create start-contributing page
• Add functionalities
• Fetch data from file system
• Write markdowns
• Add a menu for navigation
• Make the page responsive for small devices
• Design and add styles

Description

In Guide page section enable # referencing

• Create a RefWrapper mdx component to wrap h2, h3 headings
• Create a rehype plugin withRefLinks that grabs h2, h3 elements and wrap with RefWrapper mdx component
• Design RefWrapper component so that on hover # sign pop ups and user can copy the link.

Screenshots

Additional Information

No response

Is there any existing issue for this?

• I have searched the existing issues

Description

Sidebar is automatically pointing to the welcome when page gets reloaded, that does not match the content.
To reproduce
Go to
start contributing section of the website change links to installation
then
reload the page

Screenshots

Any additional information?

Expected Behaviour
Links should be persistent with the page, for above example it should be pointing to installation instead of welcome after reload.

What browser are you seeing the problem on?

Chrome

- Description

• Fork this repo.
• Create a file inside the contribution folder.
• Create a file that matches your github username with the .mdx extension (eg. your-github-username.mdx)
• Add your contribution and create a pull request.

- Check the official guide: Add your profile

📌 If you're facing any problem you can discuss your problem in the Discussion area.

• Enable syntax highlighting using Prism Js
• Add styling tokens in a new css file prism.css

###Describe

• Whenever a menu button is clicked in active page it is automatically scrolling to top.
• Thats should not be the basic behaviour, it needs to be scrolled to the top when a route is changed not in current route

Description

The issue is about creating a custom plugin that identifies internal and external type by string matching. Then it should wrap internal links with next Link component & for external links the link should open in a new tab.

Steps

• Create a new file withNextLinks inside src/lib/mdx/rehype
• Build an rehype plugin using visit function
• Import the the plugin in getMdxComponents and enlist that plugin with rehypePlugins list

Screenshots

N/A

Additional Information

This feature will improve documentation experience. And will prevent unnecessary link opening and also will leverage the power of next Link component.

Try to explain in a very simple easy to understand (beginner-friendly) words.
This will be referenced in the Application

You can mention what you do when you contribute to a open source project.

Some Practices I personally follow

1. Create a branch with issue tag like -<feat / bug / other>- for example 31-docs-question
2. Adding specific commit regarding changes applied
3. Committing all changes to that branch
4. Push to local repository
5. Create a pull request by tagging resolvable issue number
6. Added more commits to that branch if any changes are requested by the maintainers.

Describe

• This feature implements CRUD for contributor
• This feature will establish a connection with Database and will query according to the request.

Description

Currently, social links are not working as they are not plugged in. Retrieve social links from contribution meta data and add as link component and render respective icon.

Screenshots

No response

Additional Information

No response

Suggest a suitable description for Git Opener based on your observation

Description

I would like to inform you that you should change the repo name to GitOpener.
gitopener.vercel.app is the website name.

Screenshots

Additional Information

No response

• Enable recommended type checking for typescript from typescript-eslint pluging
• Resolve all file issues

Add a short note on Git in your words, Please make it specific and beginner-friendly

Description

Structure and rename folders inside “/docs/guides” start with -

Screenshots

No response

Additional Information

No response

Describe what behaviour is expected from each contributors, what should not to do?

You can write importance of pull request, why one should consider specific pull request while working with different changes.

You can add a short note on issues, You can break it down in feat,bug and other or any good practice you know about.

Description

• Add Footer section
• Add Links
• Add a slogan
• Add copyright
• Design Footer

Description

In this feature user should be able to navigate to next or previous page according to the next or previous file accordingly.

• Create a component that accepts prev and next props which can be used for navigation
• Enable page mapping, map prev and next page link based on current page return null if no prev of next page found
• Align the component to the bottom of documentation layout
• Design the component with responsiveness

Screenshots

No response

Additional Information

No response

Changes Proposed

• Rename component files using React naming convention
• Using FC component instead of simple function tag

Is there any existing issue for this?

• I have searched the existing issues

Description

No response

Screenshots

Any additional information?

No response

What browser are you seeing the problem on?

No response

Description

I would like to say that please add GitHub actions such as greetings, build test, semver release, stale issue etc. These will help automate some works.

Screenshots

No response

Additional Information

No response

Bug:

• Synchronisation of theme isn't working properly

Description

This changes will be synced will database,
Create a Document contributors model with

------
---
{
slug:{
  type:String, // should be the page unique slug(params url)
  required:true
},
contributors:[
  {
   avatar:String,
   gh_username:String,
   github_url:String
  }
],
}
------
---

create API for fetching contributors from Github API and store it to database.
The fetching should occur once at build time.

Screenshots

N/a

Additional Information

N/A

Describe what does a contributor need to do to contribute.

Description

Add mdx components to enhance mdx writing experience. These are the required components

• Tip : For a tip message, should be green coloured
• Warning : To display a warning message, should be yellow coloured
• Info : To display some additional information, should match accent colour

Design those components and update allowed mdx components list

Screenshots

No response

Additional Information

No response

Description

Features

• Create profile of each contributors,
• Display their name and occupation as contributed in the .mdx file
• Show their Github profile avatar and bio
• Add Introduction, Skills, Socials section as of now
• Build a Tab mdx component

Screenshots

No response

Additional Information

If you want to contribute to this, instead of creating pull request direct on main branch create on here

Is there any existing issue for this?

• I have searched the existing issues

Description

After running release workflow its showing invalid

Screenshots

No response

Any additional information?

No response

What browser are you seeing the problem on?

No response