coderedcorp / coderedcorp/coderedcms

Header managed in the same way as footer

Ouverte
#286 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
Type: Enhancement
Langage dominant
Python
Étoiles
765
Forks
154
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

Hello guys,

First of all I'm sorry for may bad english.

I'm just discovering this really awesome CMS. It's exactly what I need. It produces very simple html code output that I just need to style.
Congratulations for this work. I continue to investigate on it by trying a migration from an existing ecommerce site.

Now I have a suggestion. The footer is managed as a snippet. Why it's not the same for the header?
Sometimes we may have complex headers but you provide only a navigation snippet. What I'd like to have is a snippet header built in the same way than the footer and the possibility to integrate menus defined in the snipped navigations to this header as a streamfield. More generrally navigations should be available everywhere as a snippet like a card or carousel.

Maybe this can be done by using the reusable content feature but I'm not really sure about and in any case this is not intuitive.

Kind regards

Pierre

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

Review how the footer and navigation snippets are currently managed, along with the reusable content feature mentioned in the issue. Define whether headers should become reusable snippets and how navigation snippets would be exposed in them and elsewhere; done means the behavior and scope are agreed before implementation.

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

Évaluation

Stack technique
django, python
Domaine
content
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

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