https://notes.ducatillon.net/fr/tags/automation/Recent content in Automation on FDUCAT NotebookHugofr-FRhttps://notes.ducatillon.net/fr/docs/devops/githubpages/Mon, 01 Jan 0001 00:00:00 +0000https://notes.ducatillon.net/fr/docs/devops/githubpages/<h2 id="static-content-hosting-with-github-pages">Static content hosting with GitHub Pages<a class="anchor" href="#static-content-hosting-with-github-pages">#</a></h2> <p>Let&rsquo;s review the nuances between site types and how to automate their deployment.</p> <h3 id="github-pages-site-types">GitHub Pages Site Types<a class="anchor" href="#github-pages-site-types">#</a></h3> <table> <thead> <tr> <th style="text-align: left">Feature</th> <th style="text-align: left">User Site</th> <th style="text-align: left">Organization Site</th> <th style="text-align: left">Project Site</th> </tr> </thead> <tbody> <tr> <td style="text-align: left"><strong>Primary Intent</strong></td> <td style="text-align: left">Personal portfolio, resume, or central hub.</td> <td style="text-align: left">Brand, company, or collective identity.</td> <td style="text-align: left">Documentation or landing page for a specific repo.</td> </tr> <tr> <td style="text-align: left"><strong>Repo Naming</strong></td> <td style="text-align: left"><code>username.github.io</code></td> <td style="text-align: left"><code>orgname.github.io</code></td> <td style="text-align: left"><code>any-repo-name</code></td> </tr> <tr> <td style="text-align: left"><strong>Default URL</strong></td> <td style="text-align: left"><code>https://username.github.io</code></td> <td style="text-align: left"><code>https://orgname.github.io</code></td> <td style="text-align: left"><code>https://username.github.io/repo/</code></td> </tr> <tr> <td style="text-align: left"><strong>Apex Domain</strong></td> <td style="text-align: left"><strong>Supported</strong> (e.g., <code>domain.com</code>).</td> <td style="text-align: left"><strong>Supported</strong> (e.g., <code>company.com</code>).</td> <td style="text-align: left"><strong>Supported</strong> (e.g., <code>project.com</code>).</td> </tr> <tr> <td style="text-align: left"><strong>Subdomain</strong></td> <td style="text-align: left"><strong>Supported</strong> (e.g., <code>user.domain.com</code>).</td> <td style="text-align: left"><strong>Supported</strong> (e.g., <code>org.domain.com</code>).</td> <td style="text-align: left"><strong>Supported</strong> (e.g., <code>docs.domain.com</code>).</td> </tr> <tr> <td style="text-align: left"><strong>Capacity</strong></td> <td style="text-align: left">One (1) per account.</td> <td style="text-align: left">One (1) per organization.</td> <td style="text-align: left">Unlimited per account/org.</td> </tr> <tr> <td style="text-align: left"><strong>Permissions</strong></td> <td style="text-align: left">Individual ownership.</td> <td style="text-align: left">Shared team administrative access.</td> <td style="text-align: left">Inherited from the project repository.</td> </tr> </tbody> </table> <h3 id="deployment-workflow-strategies">Deployment Workflow Strategies<a class="anchor" href="#deployment-workflow-strategies">#</a></h3> <p>Static site generators (SSGs) like Hugo or MkDocs require a build step to turn source files into HTML. How you handle that build defines your workflow.</p>