Some quick pieces of feedback for a newbie looking at the website

Ouverte
  • Quelque chose ne va pas ?
#20 1 commentaire 1 réaction 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Domaine
content, design

Piste de recherche

Start by reviewing the front page, navbar, and JSON-LD subpage mentioned in the feedback. The issue lists several optional suggestions but does not say which to implement; agree on a specific scope first, then consider it done when the chosen changes address that scope.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Hey all - this looks like a really neat project!

I just took a look through the codemeta website for the first time, and just wanted to give some of my first-impressions in case they're opportunities to improve the site! I hope they don't come across as criticisms, they are meant in the spirit of constructive feedback! Feel free to disregard this entirely :-)

Some of the comments might seem a bit silly, but I tried to keep my relatively naive perspective in browsing the site, since I think that's the perspective many users would have.

  • I like how the page explains the need and motivation for code metadata, but after reading the front page I still wasn't sure what codemeta does. Maybe beginning with a short "this is what codemeta does" paragraph would be helpful.
  • The word "CrossWalk" shows up on the page, but I never saw an explanation of what this means. Maybe this is a technical word that users will already know, but it'd be helpful to explain something like "CrossWalks are a means of mapping key/values between different styles of metadata. The CodeMeta project maintains CrossWalks between a number of different metadata types (e.g. Python distutils and R DESCRIPTION files) and a common "codemeta" format.
  • The word "Terms" shows up in the navbar, but I originally didn't click on it because I assumed that it was short for "Terms and Conditions" (aka, license stuff) rather than "metadata terms". Perhaps this could be "Fields" to avoid the confusion?
  • I found the fonts a bit small to read - perhaps they could be increased in size in order to be more legible?
  • I also didn't see a link-out to an introduction to what JSON linked data is, this would be helpful for newbies that don't know what it is! edit: I found the video on the JSON-LD sub-page really helpful, perhaps it could be linked to from a "getting started" header?
Langage dominant
CSS
Étoiles
5
Forks
23
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de codemeta/codemeta.github.io

Toutes les issues de codemeta/codemeta.github.io

Issues similaires

Plus d'issues Content

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.