Appearance "Fit & Finish" - Header/Footer (and, indeed, sidebar) Consistency

Abierto
#702 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Refactorización
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
frontend

Línea de trabajo

This is a design discussion about the site's navigation, not a fixed change. Start by comparing the header dropdown menus, the footer links and the sidebar on the mirrors docs page linked in the issue. Linked issues #71, #117, #158, #546, #597, #634 and #556 cover the same ground and should be read first. Done would need a maintainer-agreed grouping of navigation items before any template edits.

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

Descripción

It almost seems like we are looking at a failed merge of the OCF Wiki (which was created many years after 'o.b.e'): we have pages, e.g. 'https://www.ocf.berkeley.edu/docs/services/mirrors/', that link to other pages from the right-hand side of the site only... even though - by standard convention - we would want any ("top-level") page that we can navigate to linked from the template at the top, i.e. via the drop-down menus...

Further, the footer - if providing links as it does now - should likely match the "flattened" categories of the header; we aren't too far from that (basic) standard... but some effort at grouping items (e.g. policies, "official" documents, etc.) & adding and/or removes one or two of the items between the two 'Services' listings would make our site look smart (and likely reduce some of the "cognitive dissonance" that can scare off a diversity of perspectives - most of whom we could use as allies long-term!)...

Please note #71, #117, #158, #546, #597, & #634 also pertain to our... beautification... agenda (maybe #556 too - not sure about the scope of effort)...

Lenguaje dominante
Python
Estrellas
46
Forks
106
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 ocf/ocfweb

Todos los issues de ocf/ocfweb

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.