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

Abierto
  • ¿Algo no está bien?
#20 1 comentario 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
content, design

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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?
Lenguaje dominante
CSS
Estrellas
5
Forks
23
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codemeta/codemeta.github.io

Todos los issues de codemeta/codemeta.github.io

Issues similares

Más issues de Content

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.