<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github Static Pages on Daniel Ancuta</title><link>https://ancuta.org/tags/github-static-pages/</link><description>Recent content in Github Static Pages on Daniel Ancuta</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Daniel Ancuta</copyright><lastBuildDate>Tue, 15 Apr 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ancuta.org/tags/github-static-pages/index.xml" rel="self" type="application/rss+xml"/><item><title>Serving static pages on AWS with Amplify</title><link>https://ancuta.org/posts/serving-static-pages-on-aws/</link><pubDate>Tue, 15 Apr 2025 00:00:00 +0000</pubDate><guid>https://ancuta.org/posts/serving-static-pages-on-aws/</guid><description>&lt;p&gt;After creating branding for your static website - layout, logo, typography, content, and so on - serving it should be easy, right?&lt;/p&gt;&#10;&lt;p&gt;But often, it&amp;rsquo;s overcomplicated. You think about a custom solution for the engine, look at WordPress, and realize it&amp;rsquo;s overkill for what you need.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://ancuta.org/posts/serving-static-pages-on-aws/featured.jpg"/></item></channel></rss>