


Optimizing Blog API Integration: Lessons Learned with Dev.to and Hashnode
During the development of my personal portfolio with Astro, I ran into an interesting challenge: how to efficiently integrate my Dev.to and Hashnode posts without having to rebuild the site every time I post new content?
The Problem
The problem seemed simple at first: display all my posts from both platforms on a single page. However, I encountered several challenges:
- Pagination Limits: Initially, I was getting only the first 20-30 posts
- Lost Posts: Every time I published a new post, I had to modify the code for it to appear
- Aggressive Cache: New posts did not appear immediately due to cache
The Solution
1. Serverless Endpoint
I created a serverless endpoint in Astro that combines the posts from both platforms:
export const GET: APIRoute = async () => { const [hashnodePosts, devtoPosts] = await Promise.all([ getHashnodePosts(), getDevToPosts() ]); const allPosts = [...hashnodePosts, ...devtoPosts] .sort((a, b) => new Date(b.rawDate).getTime() - new Date(a.rawDate).getTime() ); return new Response(JSON.stringify(allPosts), { headers: { 'Content-Type': 'application/json', 'Cache-Control': 'no-store, no-cache, must-revalidate' } }); };
2. Maximizing Post Earnings
The key is to request the maximum number of posts possible:
// Para Dev.to const params = new URLSearchParams({ username: 'goaqidev', per_page: '1000', // Máximo número de posts state: 'published' }); // Para Hashnode const query = ` query { publication(host: "goaqidev.hashnode.dev") { posts(first: 1000) { // Máximo número de posts edges { node { title brief // ...otros campos } } } } } `;
3. Avoiding the Cache
To ensure fresh content, I implemented an anti-cache strategy:
const timestamp = new Date().getTime(); const response = await fetch(`/api/posts.json?_=${timestamp}`, { headers: { 'Cache-Control': 'no-cache', 'Pragma': 'no-cache' } });
4. Client Implementation
To keep the interface up to date, I created a React component that handles loading and updating posts:
import { useState, useEffect } from 'react'; function BlogPosts() { const [posts, setPosts] = useState([]); const [loading, setLoading] = useState(true); useEffect(() => { const fetchPosts = async () => { try { const timestamp = new Date().getTime(); const response = await fetch(`/api/posts.json?_=${timestamp}`); const data = await response.json(); setPosts(data); } catch (error) { console.error('Error fetching posts:', error); } finally { setLoading(false); } }; fetchPosts(); // Actualizar cada 5 minutos const interval = setInterval(fetchPosts, 5 * 60 * 1000); return () => clearInterval(interval); }, []); if (loading) return <div>Cargando posts...</div>; return ( <div className="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-4"> {posts.map(post => ( <article key={post.id} className="card"> <h2>{post.title}</h2> <p>{post.brief}</p> <a href={post.url}>Leer más</a> </article> ))} </div> ); }
Benefits Obtained
- Automatic Update: New posts appear without needing to rebuild the site
- Better Performance: Initial loading is faster thanks to the serverless endpoint
- No Content Loss: All posts are accessible, regardless of when they were published
- Reduced Maintenance: No manual intervention required to display new posts
Error Handling
I implemented a robust error handling system:
async function fetchPosts() { try { const response = await fetch('/api/posts.json'); if (!response.ok) { throw new Error(`HTTP error! status: ${response.status}`); } const posts = await response.json(); return posts; } catch (error) { console.error('Error fetching posts:', error); // Intentar cargar desde caché local si está disponible const cachedPosts = localStorage.getItem('blog_posts'); return cachedPosts ? JSON.parse(cachedPosts) : []; } }
Performance Optimization
To further improve performance, I implemented:
- Local Cache:
// Guardar posts en localStorage localStorage.setItem('blog_posts', JSON.stringify(posts)); // Cargar posts desde localStorage mientras se actualiza const cachedPosts = localStorage.getItem('blog_posts'); if (cachedPosts) { setPosts(JSON.parse(cachedPosts)); }
- Lazy Loading of Images:
function PostImage({ src, alt }) { return ( <img loading="lazy" src={src} alt={alt} className="w-full h-48 object-cover" /> ); }
This solution has proven to be robust and efficient, allowing me to:
- Keep my portfolio automatically updated
- Improve user experience with fast charging
- Reduce the need for manual maintenance
- Ensure all my content is available and up to date
Next Steps
I plan to implement:
- Post search and filtering system
- Content preview
- Engagement metrics
- Unified comment system
The above is the detailed content of Optimizing Blog API Integration: Lessons Learned with Dev.to and Hashnode. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

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

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

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

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



Article discusses creating, publishing, and maintaining JavaScript libraries, focusing on planning, development, testing, documentation, and promotion strategies.

The article discusses strategies for optimizing JavaScript performance in browsers, focusing on reducing execution time and minimizing impact on page load speed.

Frequently Asked Questions and Solutions for Front-end Thermal Paper Ticket Printing In Front-end Development, Ticket Printing is a common requirement. However, many developers are implementing...

The article discusses effective JavaScript debugging using browser developer tools, focusing on setting breakpoints, using the console, and analyzing performance.

The article explains how to use source maps to debug minified JavaScript by mapping it back to the original code. It discusses enabling source maps, setting breakpoints, and using tools like Chrome DevTools and Webpack.

There is no absolute salary for Python and JavaScript developers, depending on skills and industry needs. 1. Python may be paid more in data science and machine learning. 2. JavaScript has great demand in front-end and full-stack development, and its salary is also considerable. 3. Influencing factors include experience, geographical location, company size and specific skills.

This tutorial will explain how to create pie, ring, and bubble charts using Chart.js. Previously, we have learned four chart types of Chart.js: line chart and bar chart (tutorial 2), as well as radar chart and polar region chart (tutorial 3). Create pie and ring charts Pie charts and ring charts are ideal for showing the proportions of a whole that is divided into different parts. For example, a pie chart can be used to show the percentage of male lions, female lions and young lions in a safari, or the percentage of votes that different candidates receive in the election. Pie charts are only suitable for comparing single parameters or datasets. It should be noted that the pie chart cannot draw entities with zero value because the angle of the fan in the pie chart depends on the numerical size of the data point. This means any entity with zero proportion

In-depth discussion of the root causes of the difference in console.log output. This article will analyze the differences in the output results of console.log function in a piece of code and explain the reasons behind it. �...
