[Doc] Update the store display picture and description

[Xsy41]

Description

We plan to unify the name of HyperCRX, update the image display of the store, and modify the introduction name. 1. Unified name 2. Change the store picture Our current picture of the store is a little blurry, with multiple images pieced together. Try using small pictures to show the content. Roughly follow this idea to change the display image.

3. Introduce the name change

[HalloMelon]

Like the introduction of this plug-in, and based on the previous issues (https://github.com/hypertrons/hypertrons-crx/issues/833). I think the introduction can be written like this:

Adds analytic dashboards to GitHub, facilitating the tracing of projects and exploration of developer networks.

Features: 📊 Displays developer activity and OpenRank trends 🤝 Visualizes developer relationships and networks 🤖 Uses GPT technology to generate content and suggestions (not available) 📈 Shows repository activity and OpenRank trends 🏁 Displays repository activity in a racing bar format 🔧 Provides detailed information on repository forks 📌 Adds labels for OpenRank, activity, contributors, and participants to repository headers 📑 Shows detailed information on repository issues 🔗 Visualizes relationships between repositories 🔀 Provides detailed information on pull requests ⭐ Shows detailed information on repository stars

Download now and transform the way you navigate and contribute to GitHub projects!

[HalloMelon]

Hello @Xsy41 ,I just submitted a PR and modified the text, but there are still some problems with workflow processing. When I click "Test Token", there are two failure situations, one is an invalid token, and the other is that users did not click "save" first. In the second method, when you directly click "Test Token", can the corresponding prompt pop up, such as: "Please save first and then test."？

[wangyantong2000]

Hello @Xsy41 ,I just submitted a PR and modified the text, but there are still some problems with workflow processing. When I click "Test Token", there are two failure situations, one is an invalid token, and the other is that users did not click "save" first. In the second method, when you directly click "Test Token", can the corresponding prompt pop up, such as: "Please save first and then test."？

It should be better to modify the workflow, and it should also be possible to test without saving after input.

[HalloMelon]

Hello @Xsy41 ,I just submitted a PR and modified the text, but there are still some problems with workflow processing. When I click "Test Token", there are two failure situations, one is an invalid token, and the other is that users did not click "save" first. In the second method, when you directly click "Test Token", can the corresponding prompt pop up, such as: "Please save first and then test."？

It should be better to modify the workflow, and it should also be possible to test without saving after input.

Oh yeah, I read the specific requirements:

Provide a UI interface allowing users to input their GitHub Tokens. Securely store user's Tokens. Encapsulate a network request method that uses the GitHub Token, which will be called by other new features needing to access the GitHub API in the future.

So, it is better to test before save, and the current tip is ok.

[wangyantong2000]

Oh yeah, I read the specific requirements:

Provide a UI interface allowing users to input their GitHub Tokens. Securely store user's Tokens. Encapsulate a network request method that uses the GitHub Token, which will be called by other new features needing to access the GitHub API in the future.

So, it is better to test before save, and the current tip is ok.

The current problem is that this function has a problem, when the first input, the correct token after the test, will also be reported error. This feature should be perfected.

[Xsy41]

I changed the image display in the app store. Below is a link to the image. Picture link I feel like we can change our name in the App Store from "HyperCRX" to "HyperCRX for GitHub" and change the brief section to "Adds analytic dashboards to GitHub".

[HalloMelon]

Yeah, I think it's great. But maybe the screenshots can provide more relevant introduction, like this one：

[Xsy41]

Okay, I've added a few more screenshots with more specific text. Below is a link to the image. Picture link

[HalloMelon]

It is better, and I have the following picture as a supplement.

[HalloMelon]

I updated with two new screenshots.

[HalloMelon]

The current introduction in the mall has been updated as follows:

Hypercrx project adds analytic dashboards to GitHub, aiming at tracing, digging and gaining insight into the projects and developers you're interested in. We do this by inserting useful dashboards into GitHub pages. Hypercrx provides an effective way for digital operations and analysis of open source community.

Features: 📊 Displays developer activity and OpenRank trends 🤝 Visualizes developer relationships and networks 🤖 Uses GPT technology to generate content and suggestions (not available) 📈 Shows repository activity and OpenRank trends 🏁 Displays repository activity in a racing bar format 🔧 Provides detailed information on repository forks 📌 Adds labels for OpenRank, activity, contributors, and participants to repository headers 📑 Shows detailed information on repository issues 🔗 Visualizes relationships between repositories 🔀 Provides detailed information on pull requests ⭐ Shows detailed information on repository stars

Download now and transform the way you navigate and contribute to GitHub projects!