podfeetIn this instalment of Programming By Stealth, @bart walks through how he used the tools he taught in “Programmed by Stealth” to migrate the Let’s Talk website from WordPress to GitHub Pages. Most things worked well, but there were still some surprises.
N-gated Hacker NewsAh, the cutting-edge #innovation of decentralized social networking—now with a ✨sparkling✨ new paint job called "static sites". 🚀 Just fork, enable, and pretend you're not just slapping lipstick on an HTML pig. 🤡 Who needs dynamic interaction when you can have the excitement of watching paint dry on GitHub Pages instead? 🎨
http://satproto.org/ #decentralizedsocialnetworking #static #sites #GitHubPages #webdevelopment #humor #HackerNews #ngated
http://satproto.org/ #decentralizedsocialnetworking #static #sites #GitHubPages #webdevelopment #humor #HackerNews #ngated
Marco SiccardiI have just launched a redesigned version of my portfolio website: https://msiccdev.net
It now gives a much better picture of my products, my software engineering background, and the kind of work I care about building.
AptiviSwitching GitHub Pages deployment method from classic to modern method demonstrated with Textify.
#GitHub #GitHubPages #GitHubActions #TechNews #TechUpdates #website
AptiviSwitching GitHub Pages deployment from Classic to Actions-based deployment
GitHub has introduced another method to deploy your GitHub Pages website from the classic method to the modern deployment method from your GitHub Actions workflow. This avoids having to select a dedicated branch (usually called gh-pages) from your repository, which is separate from all your branches, including the main one.
This removes a huge overhead in having to maintain a separate branch dedicated for GitHub Pages files, which are static files that contain HTML, CSS, JS, and other website-related files. Instead, you can deploy your website straight from one branch and one workflow.
As part of our public apology for the API docs not being updated to take new design into account, we have first followed the steps that changed how the deployment works:
After that, we have edited the API documentation workflow so that it uses a more modern approach to deploying the docs site. The edits went like this for Textify (reference):
permissions: contents: read pages: write id-token: write github-pages, and set the deployment URL to the pages URL fetched from the deployment step. environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}peaceiris/actions-gh-pages@v3 action with the actions/upload-pages-artifact@v3 action. - name: Saving changes to gh-pages
uses: actions/upload-pages-artifact@v3
with:
path: 'docs'deployment, that uses actions/deploy-pages@v4. - id: deployment
uses: actions/deploy-pages@v4After that, a commit that edited the workflow file was made, and the workflow has been run according to the rule that was set (to use the latest codebase found in the main branch):
on: push: branches: - main pull_request: branches: - main As soon as this workflow ran, the Generate API Documentation workflow has run, and all steps went green! You can see the deployment logs below (after building the documentation):
Run actions/deploy-pages@v4 with: token: *** timeout: 600000 error_count: 10 reporting_interval: 5000 artifact_name: github-pages preview: false env: DOTNET_ROOT: /usr/share/dotnet Fetching artifact metadata for "github-pages" in this workflow run Found 1 artifact(s) Creating Pages deployment with payload: { "artifact_id": 5799820482, "pages_build_version": "b7cdd6b433d112ca575333cbfee3e92eb91ea304", "oidc_token": "***" } Created deployment for b7cdd6b433d112ca575333cbfee3e92eb91ea304, ID: b7cdd6b433d112ca575333cbfee3e92eb91ea304 Getting Pages deployment status... Reported success! Finally, the API documentation has been generated and deployed to a github.io site for Textify, which you can find here. This has fixed issues related to outdated content appearing in the deployment, even though that deployment appeared to have been successful.
Our recommendation is that if you use the classic GitHub Pages deployment method, you should consider migrating to the modern method, after studying implications and migration costs, depending on how the deployment is made.
#github #GitHubPages #news #Tech #Technology #update
Frontend DogmaQuick Tip: Hosting HTML/CSS/JS Demos From Source Code on GitHub Pages, by @codepo8:
Dave CrossI've published my first Action to the GitHub Marketplace. It's a very simple tool (as all the best ones are!) that takes your repo's README and converts it to HTML for use in a GitHub Pages website. It scratched a very particular itch for me, but it might be useful to other people, too.
🦆 √ 🐄 📡 NOT4BFLU55 ist jetzt maschinenlesbar live.
Bildtafeln mit Transkription + Kontext → offen archiviert: https://git.not4bflu55.de/
Sitemap für Crawler: https://git.not4bflu55.de/sitemap.xml
Warum?
Weil Text im Bild ohne Text im Web für Maschinen Rauschen ist.
Hier liegt der Sinn wieder als Text neben dem Bild.
#NOT4BFLU55 #Infologie #Filterblase #OpenArchive #WebCrawling #GitHubPages #Sitemap #Fediverse #Maschinenfutter
Sam TrippI've published a new blog post: Creating and Hosting a Website with Hugo 🚀
https://www.samtripp.co.uk/posts/creating-and-hosting-a-website-with-hugo/
#blog #blogpost #githubactions #github #githubpages #Hugo #webdev
xoron 
Local-Only File Encryption with JavaScript.
I've been exploring the #WebCryptoAPI and I'm impressed!
When combined with the #FileSystemAPI, it offers a seemingly secure way to #encrypt and #store files directly on your device. Think #localstorage, but with #encryption!
I know #webapps can have #security vulnerabilities since the code is served over the web, so I've #OpenSourced my demo! You can check it out, and it should even work if #selfhosted on #GitHubPages.
Live Demo: https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo
Demo Code: https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js
About the Dim framework:
https://positive-intentions.com/docs/category/dim
IMPORTANT NOTES (PLEASE READ!):
* This is NOT a product. It's for #testing and #demonstration purposes only.
* It has NOT been reviewed or audited. Do NOT use for sensitive data.
* The password encryption currently uses a hardcoded password. This is for demonstration, not security.
* This is NOT meant to replace robust solutions like #VeraCrypt. It's just a #proofofconcept to show what's possible with #browser #APIs.
#Encryption #Cryptography #JavaScript #Frontend #Privacy #Security #WebDevelopment #Coding #Developer #Tech #FOSS #OpenSource #GitHub #MastodonDev #Programming #WebStandards #FileSystem #WebAPI #ProofOfConcept