Différences entre versions de « Pin »

De Mi caja de notas

(Page créée avec « ''cette page a démarré sur iwc:pin et migrera après traduction sur iwc:pin-fr'' {{emojicon|📌}} {{stub}} '''<dfn>pin</dfn>''' or <dfn>pinning</dfn> is a fe... »)
 
 
(2 versions intermédiaires par le même utilisateur non affichées)
Ligne 5 : Ligne 5 :
 
{{stub}}
 
{{stub}}
  
−
'''<dfn>pin</dfn>''' or <dfn>pinning</dfn> is a feature that allows the author to choose a [[post]] to put at the top of their profile (or [[homepage]]) which is then called a <dfn>pinned</dfn> or <dfn>sticky</dfn> post.
+
'''<dfn>pin</dfn>''' or <dfn>pinning</dfn> est une fonctionnalité qui permet à l'auteur de choisir un [[post]] à placer en haut de son profil (ou sa [[homepage-fr|page d'accueil]]) qui est ensuite appelé un post  <dfn>pinned</dfn> (épinglé) ou <dfn>sticky</dfn>.
  
−
== Why ==
+
== Pourquoi ==
−
Sometimes you want to bring attention to a post that's more currently relevant than just the most recent post in your stream, e.g.
+
Parfois, vous souhaitez attirer l'attention vers un post qui est plus particulièrement pertinent que le post le plus récent dans votre flux, par ex.  
−
* before an imminent [[event]] (human) or [[site-deaths|site shutdown]]
+
* avant un [[event|événement]] imminent (humain) ou la [[site-deaths|fermeture d'un site]]
−
* a currently active event
+
* un événement actuellement actif
−
* fundraising campaign
+
* une campagne de levée de fonds
−
By "pinning" such a post to the top of your stream, you make sure any new readers (or returning readers) who visit your homepage or profile see that post first, and consider it as recently (or still) relevant even if it is not the most recent thing you have posted.
+
En "épinglant" un tel post en haut de votre flux, vous vous assurez que tous les lecteurs d'actualités (ou les lecteurs revenant) qui visitent votre page d'accueil ou votre profil le voient en premier, et le considère comme récemment (ou encore) pertinent même si ce n'est pas la chose la plus récente que vous avez postée.
 
__TOC__
 
__TOC__
−
== IndieWeb Examples ==
+
== Exemples IndieWeb ==
 
=== Aaron Parecki ===
 
=== Aaron Parecki ===
 
{{aaronpk}} supports pinned posts in tag pages [https://aaronparecki.com/2016/12/28/3/day-8-pinned-posts since 2016-12-28], e.g.:
 
{{aaronpk}} supports pinned posts in tag pages [https://aaronparecki.com/2016/12/28/3/day-8-pinned-posts since 2016-12-28], e.g.:
 
** https://aaronparecki.com/tag/100daysofindieweb
 
** https://aaronparecki.com/tag/100daysofindieweb
  
−
=== ... add yourself! ===
+
=== ... ajoutez-vous ! ===
 
...
 
...
  
−
== Software Support ==
+
== Support Logiciel ==
−
* [[WordPress]] has supported sticky posts since 2.7
+
* [[WordPress]] supporte les posts sticky depuis la v. 2.7
  
−
== Silo Support ==
+
== Support Silo ==
 
=== Facebook ===
 
=== Facebook ===
 
[[Facebook]] has supported pinned posts on [[event]]s, [[pages]], and [[groups]] for quite some time (the admin/creators of such posts/pages has the ability to (un)pin posts).
 
[[Facebook]] has supported pinned posts on [[event]]s, [[pages]], and [[groups]] for quite some time (the admin/creators of such posts/pages has the ability to (un)pin posts).
Ligne 42 : Ligne 42 :
  
 
=== Last.fm ===
 
=== Last.fm ===
−
[[Last.fm]] supports adding pinned [[jam|obsessions]] to the top of one's user profile. These are automatically set to [[expiring_content|expire]] after one week.
+
[[Last.fm]] supporte l'ajout d'[[jam|obsessions]] épinglées tout en haut du profil d'un utilisateur. Ces obsessions sont automatiquement réglées pour [[expiring_content|expirer]] après une semaine.
  
−
Example of UI to set a pinned post (aka obsession): notice red button
+
Exemple d'UI pour régler un post épinglé (aka obsession) : remarquez le bouton rouge
 
[[File:Lastfm_set_obsession.PNG]]
 
[[File:Lastfm_set_obsession.PNG]]
  
−
Example of UI for pinned post (aka obsession)
+
Exemple d'UI pour un post épinglé (aka obsession)
 
[[File:Lastfm pinned obsession.PNG]]
 
[[File:Lastfm pinned obsession.PNG]]
−
 
  
 
== Brainstorming ==
 
== Brainstorming ==
−
More thinking on pinned / sticky posts. Various thoughts:
+
Plus de pensée sur les posts épinglés / sticky. Différentes idées :  
  
−
=== first or just near top ===
+
=== premier ou juste près du haut  ===
 
* You may not want it to be the first post in your profile - because that may give the illusion that there's nothing newer.
 
* You may not want it to be the first post in your profile - because that may give the illusion that there's nothing newer.
 
* Possibly 1-2 normal in-stream posts display, then followed by the pinned post, almost like it is a [[promoted]] post for itself.
 
* Possibly 1-2 normal in-stream posts display, then followed by the pinned post, almost like it is a [[promoted]] post for itself.
Ligne 60 : Ligne 59 :
 
** Note: {{aaronpk}} implements pinning as show as first post, and [[Twitter]], [[Facebook]] both also implement pinning as first post.
 
** Note: {{aaronpk}} implements pinning as show as first post, and [[Twitter]], [[Facebook]] both also implement pinning as first post.
  
−
=== special presentation ===
+
=== présentation spéciale ===
 
Any special presentational considerations for pinned posts? Besides being shown "first" (see above)?
 
Any special presentational considerations for pinned posts? Besides being shown "first" (see above)?
  
Ligne 68 : Ligne 67 :
 
*** new template slot? a specific spot in a home page template for a pinned post may help move some presentational distinctions to just HTML+CSS, and leave the "engine" to just find and put a pinned post in the right spot in the template. The more presentation that can be done in HTML+CSS rather than procedural coding, the better. Since this may be engine specific, I’ll add more in: '''[[Falcon#pinned_posts]]'''
 
*** new template slot? a specific spot in a home page template for a pinned post may help move some presentational distinctions to just HTML+CSS, and leave the "engine" to just find and put a pinned post in the right spot in the template. The more presentation that can be done in HTML+CSS rather than procedural coding, the better. Since this may be engine specific, I’ll add more in: '''[[Falcon#pinned_posts]]'''
  
−
=== markup details ===
+
=== détails de marquage ===
 
* {{t}} Just an [[h-entry]]. Should a pinned post have any different markup than a regular post? Only if there is a specific use-case need, otherwise, it's just a post.
 
* {{t}} Just an [[h-entry]]. Should a pinned post have any different markup than a regular post? Only if there is a specific use-case need, otherwise, it's just a post.
 
* {{t}} Still part of explicit (or implicit) [[h-feed]] on the page. Since a pinned post should only be shown once in a stream (instead of twice, at the top and in the stream in sort order), the pinned post h-entry should be either explicitly in the same h-feed, or at least at the same level (from a [[microformats2]] parser perspective) as the other h-entrys on the page, so that h-feed consuming code will just include it in the overall stream it presents to readers etc.
 
* {{t}} Still part of explicit (or implicit) [[h-feed]] on the page. Since a pinned post should only be shown once in a stream (instead of twice, at the top and in the stream in sort order), the pinned post h-entry should be either explicitly in the same h-feed, or at least at the same level (from a [[microformats2]] parser perspective) as the other h-entrys on the page, so that h-feed consuming code will just include it in the overall stream it presents to readers etc.
Ligne 88 : Ligne 87 :
 
  <nowiki><div class="ui green right corner label"><i class="ui pin icon"></i></div></nowiki>
 
  <nowiki><div class="ui green right corner label"><i class="ui pin icon"></i></div></nowiki>
  
−
=== tag or category specific ===
+
=== tag ou catégorie spécifique ===
 
* I want to be able to pin posts in different feeds, ie. on certain tag pages. So the post could still appear chronologically in places where it's not pinned. - {{rhiaro}}
 
* I want to be able to pin posts in different feeds, ie. on certain tag pages. So the post could still appear chronologically in places where it's not pinned. - {{rhiaro}}
 
* Note: {{aaronpk}} has implemented this, e.g. https://aaronparecki.com/tag/100daysofindieweb
 
* Note: {{aaronpk}} has implemented this, e.g. https://aaronparecki.com/tag/100daysofindieweb
  
−
=== pinning and feed files ===
+
=== épingle et fichiers de flux ===
 
* I don't want a reader to treat a pinned post as always the most recent in a feed. Do readers sort things themselves by published date, or display things in the order they pull them from a feed? - {{rhiaro}}
 
* I don't want a reader to treat a pinned post as always the most recent in a feed. Do readers sort things themselves by published date, or display things in the order they pull them from a feed? - {{rhiaro}}
 
* {{t}} I would not do anything with pinning in feed files. Readers are likely to just display in dt-published order most recent first anyway.
 
* {{t}} I would not do anything with pinning in feed files. Readers are likely to just display in dt-published order most recent first anyway.
  
−
=== auto-unpinning ===
+
=== auto-désépinglage ===
 
{{t}} I am considering implementing pinned posts, but having them auto-unpin (or [[expiring_content|expire]]) after some period of time like ~60 days. This will both make them easier to implement, and also provide an automatic way to not have to worry about unpinning something eventually. I like systems that by default clean-up after themselves.
 
{{t}} I am considering implementing pinned posts, but having them auto-unpin (or [[expiring_content|expire]]) after some period of time like ~60 days. This will both make them easier to implement, and also provide an automatic way to not have to worry about unpinning something eventually. I like systems that by default clean-up after themselves.
  
Ligne 103 : Ligne 102 :
 
* [[2013/Hollywood/Pinning_Posts]]
 
* [[2013/Hollywood/Pinning_Posts]]
  
−
== See Also ==
+
== Voir aussi ==
 
* [[one day banner]]
 
* [[one day banner]]
 
* [[GitHub]] supports pinning of [[issues]]. Example as of 2018-12-28: [https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues FriendsOfPHP/PHP-CS-Fixer].
 
* [[GitHub]] supports pinning of [[issues]]. Example as of 2018-12-28: [https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues FriendsOfPHP/PHP-CS-Fixer].

Version actuelle datée du 11 février 2019 à 13:32

cette page a démarré sur iwc:pin et migrera après traduction sur iwc:pin-fr

📌

Cet article est une ébauche. Vous pouvez m'aider à l'améliorer et le compléter. Merci.

pin or pinning est une fonctionnalité qui permet à l'auteur de choisir un post à placer en haut de son profil (ou sa page d'accueil) qui est ensuite appelé un post pinned (épinglé) ou sticky.

Pourquoi

Parfois, vous souhaitez attirer l'attention vers un post qui est plus particulièrement pertinent que le post le plus récent dans votre flux, par ex.

En "épinglant" un tel post en haut de votre flux, vous vous assurez que tous les lecteurs d'actualités (ou les lecteurs revenant) qui visitent votre page d'accueil ou votre profil le voient en premier, et le considère comme récemment (ou encore) pertinent même si ce n'est pas la chose la plus récente que vous avez postée.

Exemples IndieWeb

Aaron Parecki

portrait Aaron Parecki supports pinned posts in tag pages since 2016-12-28, e.g.:

... ajoutez-vous !

...

Support Logiciel

  • WordPress supporte les posts sticky depuis la v. 2.7

Support Silo

Facebook

Facebook has supported pinned posts on events, pages, and groups for quite some time (the admin/creators of such posts/pages has the ability to (un)pin posts).

  • Noticeably absent: Facebook DOES NOT have the ability for a user to pin a post on their own profile/timeline.

Fichier:Facebook-pinned-post-group.png

Facebook pinned posts appear with a separate header from "recent activity" and look visually distinct from the chronological list of posts.

Twitter

Twitter's mid-2014 UI update added support for a pinned post on a user profile.

Fichier:Twitter-pinned-tweet.png

Twitter pinned tweets are marked with "pinned tweet", but otherwise are integrated into the primary list of tweets.

Last.fm

Last.fm supporte l'ajout d'obsessions épinglées tout en haut du profil d'un utilisateur. Ces obsessions sont automatiquement réglées pour expirer après une semaine.

Exemple d'UI pour régler un post épinglé (aka obsession) : remarquez le bouton rouge Fichier:Lastfm set obsession.PNG

Exemple d'UI pour un post épinglé (aka obsession) Fichier:Lastfm pinned obsession.PNG

Brainstorming

Plus de pensée sur les posts épinglés / sticky. Différentes idées :

premier ou juste près du haut

  • You may not want it to be the first post in your profile - because that may give the illusion that there's nothing newer.
  • Possibly 1-2 normal in-stream posts display, then followed by the pinned post, almost like it is a promoted post for itself.
  • portrait Tantek Çelik: I'm pretty sure I want my pinned post to presentationally be the first post-like thing on my profile, in the stream of posts etc.

présentation spéciale

Any special presentational considerations for pinned posts? Besides being shown "first" (see above)?

  • portrait Tantek Çelik - the pinned post should have some indication that it is pinned and not just the latest post.
    • minimum: text (and/or icon) above the post (content) like Twitter's "Pinned Tweet" or Facebook's "Pinned Post", or portrait Aaron Parecki's little "pin" icon on a green triangle in the top right of a post block.
    • maybe a separate border around the post? especially if there is a header like "Recent Activity" after the pinned post but before the normal ordered stream of posts (FB does this)
      • new template slot? a specific spot in a home page template for a pinned post may help move some presentational distinctions to just HTML+CSS, and leave the "engine" to just find and put a pinned post in the right spot in the template. The more presentation that can be done in HTML+CSS rather than procedural coding, the better. Since this may be engine specific, I’ll add more in: Falcon#pinned_posts

détails de marquage

  • portrait Tantek Çelik Just an h-entry. Should a pinned post have any different markup than a regular post? Only if there is a specific use-case need, otherwise, it's just a post.
  • portrait Tantek Çelik Still part of explicit (or implicit) h-feed on the page. Since a pinned post should only be shown once in a stream (instead of twice, at the top and in the stream in sort order), the pinned post h-entry should be either explicitly in the same h-feed, or at least at the same level (from a microformats2 parser perspective) as the other h-entrys on the page, so that h-feed consuming code will just include it in the overall stream it presents to readers etc.
<div class="status__prepend">
<div class="status__prepend-icon-wrapper">
<i class="status__prepend-icon fa fa-fw fa-thumb-tack"></i>
</div>
<span>
Pinned toot
</span>
</div>

The Atom feed doesn't have the pinned statuses in.

Aaron's pinned posts likewise have 

<div class="ui green right corner label"><i class="ui pin icon"></i></div>

tag ou catégorie spécifique

épingle et fichiers de flux

  • I don't want a reader to treat a pinned post as always the most recent in a feed. Do readers sort things themselves by published date, or display things in the order they pull them from a feed? - Modèle:Rhiaro
  • portrait Tantek Çelik I would not do anything with pinning in feed files. Readers are likely to just display in dt-published order most recent first anyway.

auto-désépinglage

portrait Tantek Çelik I am considering implementing pinned posts, but having them auto-unpin (or expire) after some period of time like ~60 days. This will both make them easier to implement, and also provide an automatic way to not have to worry about unpinning something eventually. I like systems that by default clean-up after themselves.

Session

Sessions about pinning:

Voir aussi

Récupérée de « https://ducamp.me/index.php?title=Pin&oldid=12968 »