Webmention, a W3C recommendation last updated January 12, 2017, is a simple mechanism for notifying a URL when it's mentioned on another site. Conversely, it allows a site to receive notifications when mentioned elsewhere. Essentially, it transforms your website into an active social media hub, facilitating communication from various platforms (Twitter, Instagram, Mastodon, etc.).
Implementing Webmentions varies; WordPress users can easily install plugins, while others may require more manual configuration. Let's explore the process.
Implementation Plan
- Establish a Webmention endpoint.
- Transform social media interactions into Webmentions.
- Integrate mentions into your website/app.
- Configure outbound Webmentions.
Fortunately, several services simplify this process. The third step requires more effort, but I'll detail my approach on atila.io.
My NextJS-based, server-side rendered blog uses client-side Webmention requests, easily adaptable to other React apps and JavaScript applications.
Step 1: Defining the Webmention Endpoint
To receive Webmentions, you can either create a custom script or use a service like Webmention.io (my chosen method).
Webmention.io is free; you only need to verify domain ownership. I used a rel="me"
attribute linking my website to my social media profiles. A single link suffices, but I included all my accounts.
<a href="http://www.miracleart.cn/link/069802d489a7b73dd31fd13b0f2cd690" rel="me noopener noreferrer" target="_blank"> @AtilaFassina </a>
This requires a reciprocal link from my Twitter profile back to my website. After verification on Webmention.io, add your website URL. This provides your Webmention endpoint. Include these <link>
tags in your webpage's to collect mentions:
<link href="https://webmention.io/%7Buser%7D/webmention" rel="webmention"> <link href="https://webmention.io/%7Buser%7D/xmlrpc" rel="pingback">
Replace {user}
with your Webmention.io username.
Step 2: Processing Social Media Interactions
While Webmentions are ready, their usage is limited. Converting social media interactions is crucial. Bridgy, a free service, connects syndicated content and transforms it into Webmentions. Using SSO, connect your various profiles.
Step 3: Displaying Webmentions on Your Site
This step involves retrieving and displaying Webmention data. We'll break it down into stages: counting mentions, fetching mentions, and integrating with NextJS (optional).
Counting Webmentions
The Webmention.io API provides a count of mentions. The response is structured as follows:
type TMentionsCountResponse = { count: number; type: { like: number; mention: number; reply: number; repost: number; }; };
This is processed to:
type TMentionsCount = { mentions: number; likes: number; total: number; };
The endpoint is: https://webmention.io/api/count.json?target=${post_url}
. Max B?ck and Swyx combine likes with reposts and mentions with replies.
const getMentionsCount = async (postURL: string): Promise<tmentionscount> => { const resp = await fetch(`https://webmention.io/api/count.json?target=${postURL}/`); const { type, count } = await resp.json(); return { likes: type.like type.repost, mentions: type.mention type.reply, total: count, }; };</tmentionscount>
Fetching Webmentions
The https://webmention.io/api/mentions
endpoint is paginated, accepting page
, per-page
, and target
parameters. A successful response includes a links
array of mentions:
type TMention = { source: string; verified: boolean; verified_date: string; id: number; private: boolean; data: { author: { name: string; url: string; photo: string; }; url: string; name: string; content: string; published: string; published_ts: number; }; activity: { type: 'link' | 'reply' | 'repost' | 'like'; sentence: string; sentence_html: string; }; target: string; };
The fetch request:
const getMentions = async ( page: string, postsPerPage: number, postURL: string ): Promise => { const resp = await fetch( `https://webmention.io/api/mentions?page=${page}&per-page=${postsPerPage}&target=${postURL}` ); const list = await resp.json(); return list.links; };
NextJS Integration (Optional)
NextJS offers getStaticProps
, getStaticPaths
, and getServerSideProps
for data fetching. I chose a client-side approach using SWR for caching and state management.
Displaying the Webmention Count
A MentionsCounter
component displays the count:
// ... (import statements and types) ... const MentionsCounter = ({ postUrl }) => { const { t } = useTranslation(); const { data = {}, error } = useSWR(postUrl, getMentionsCount); if (error) { return <errormessage>{t('common:errorWebmentions')}</errormessage>; } const { likes = '-', mentions = '-' } = data; return ( <mentioncounter> <li> <heart title="Likes"></heart> <counterdata>{Number.isNaN(likes) ? 0 : likes}</counterdata> </li> <li> <comment title="Mentions"></comment> <counterdata>{Number.isNaN(mentions) ? 0 : mentions}</counterdata> </li> </mentioncounter> ); };
Displaying the Mentions
A Webmentions
component displays the actual mentions, using state for pagination and useEffect
for fetching:
// ... (import statements and types) ... const Webmentions = ({ postUrl }) => { const { t } = useTranslation(); const [page, setPage] = useState(0); const [mentions, addMentions] = useState([]); useEffect(() => { const fetchMentions = async () => { const olderMentions = await getMentions(page, 50, postUrl); addMentions((mentions) => [...mentions, ...olderMentions]); }; fetchMentions(); }, [page]); return ( {mentions.map((mention, index) => ( <mention key="{mention.data.author.name}"> <authoravatar lazy src="%7Bmention.data.author.photo%7D"></authoravatar> <mentioncontent> <mentiontext activity="{mention.activity.type}" data="{mention.data}"></mentiontext> </mentioncontent> </mention> ))} {mentions.length > 0 && ( <morebutton onclick="{()"> setPage(page 1)} type="button"> {t('common:more')} </morebutton> )} > ); };
Step 4: Handling Outbound Mentions
Webmention.app, with an API token and webhook, simplifies outbound mentions. Alternatively, Remy Sharp's wm
CLI package can be used as a post-build script. Microformats (h-entry and h-card) are essential for richer outbound mentions.
Conclusion
This guide provides a comprehensive overview of Webmention implementation. Remember to share this post if it was helpful!
References
- Using Web Mentions on Static Sites (Max B?ck)
- Client-side Webmentions (Swyx)
- Send outgoing Webmentions (Remy Sharp)
- Your first webmention (Aaron Parecki)
Further Reading
- Webmention W3C Specification (Recommendation)
- Webmention.io
- Webmention.App
- Outbound WebMentions CLI
- Bridgy
- Microformats.org
- IndieWeb
The above is the detailed content of Jumping Into Webmentions With NextJS (or Not). For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

CSScounterscanautomaticallynumbersectionsandlists.1)Usecounter-resettoinitialize,counter-incrementtoincrease,andcounter()orcounters()todisplayvalues.2)CombinewithJavaScriptfordynamiccontenttoensureaccurateupdates.

In CSS, selector and attribute names are case-sensitive, while values, named colors, URLs, and custom attributes are case-sensitive. 1. The selector and attribute names are case-insensitive, such as background-color and background-Color are the same. 2. The hexadecimal color in the value is case-sensitive, but the named color is case-sensitive, such as red and Red is invalid. 3. URLs are case sensitive and may cause file loading problems. 4. Custom properties (variables) are case sensitive, and you need to pay attention to the consistency of case when using them.

CSSselectorsandpropertynamesarecase-insensitive,whilevaluescanbecase-sensitivedependingoncontext.1)Selectorslike'div'and'DIV'areequivalent.2)Propertiessuchas'background-color'and'BACKGROUND-COLOR'aretreatedthesame.3)Valueslikecolornamesarecase-insens
