Foire aux questions #1466
Merged
Foire aux questions #1466
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1463
Contexte
Suite à la migration des articles blog vers django-prose, on s'est aperçus que la FAQ n'était pas une page en soi.
Scope
Création de la page FAQ
On a pris un design utilisant des accordéons (comme chez ma-cantine) pour éviter le scroll vers le bas en utilisant un index avec des anchor-links.
Les réponses ont du HTML dedans, donc l'utilisation d'un objet JS à itérer dans le template n'était pas pratique. Par exemple :
Lien dans le header
La FAQ apparaît désormais à côté des ressources :
Ajout d'une bordure dans les article blog
Un petit dév non-lié à la FAQ : une bordure pour différencier les meta-données de l'article blog du contenu.
Après :
Avant (frontière peu claire lors qu'on utilise des entêtes variés) :