lmika/weiro
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions

Styled the post list and added updating of posts

Browse source
This commit is contained in:
Leon Mika 2026-02-22 10:09:34 +11:00
parent e77cac2fd5
commit aef3bb6a1e
31 changed files with 1230 additions and 118 deletions
Download patch file Download diff file Expand all files Collapse all files

1
_test-site/posts/2026/02/18-first-post.md
View file

@ -4,7 +4,6 @@ title: First Post
date: 2026-02-18T11:17:00Z
tags: []
slug: /2026/02/18/first-post
---
Hello World!

1
_test-site/posts/2026/02/19-about-a-db.md
View file

@ -4,7 +4,6 @@ title: About a DB
date: 2026-02-19T11:17:00Z
tags: []
slug: /2026/02/19/about-a-db
---
Hello again.

12
_test-site/posts/2026/02/20-first-attempt-at.md
View file

@ -5,10 +5,10 @@ date: 2026-02-20T22:48:58Z
tags: []
slug: /2026/02/21/first-attempt-at
---
If you're seeing this, then posting from the UI works.
The UI is using service-side HTTP rendering, so there's nothing fancy going on here. I've chosen to use Boostrap for the frontend. It's a little traditional but hey, it looks good. I can't post a screenshot of the UI as Weiro doesn't have attachments yet, but I will once I have attachments working.
The new post should have been saved in the Sqlite3 database, which should trigger a rebuild of the site and a publish to Netlify. The existing posts should still be there too. At the moment, the publishing is done inline, which won't be the case for long, but I want to make sure the publishing flow is working properly.
If you're seeing this, then posting from the UI works.
The UI is using service-side HTTP rendering, so there's nothing fancy going on here. I've chosen to use Boostrap for the frontend. It's a little traditional but hey, it looks good. I can't post a screenshot of the UI as Weiro doesn't have attachments yet, but I will once I have attachments working.
The new post should have been saved in the Sqlite3 database, which should trigger a rebuild of the site and a publish to Netlify. The existing posts should still be there too. At the moment, the publishing is done inline, which won't be the case for long, but I want to make sure the publishing flow is working properly.
Okay, here we go.

1
_test-site/posts/2026/02/20-netlify.md
View file

@ -4,7 +4,6 @@ title: Direct Publish To Netlify
date: 2026-02-20T06:36:00Z
tags: []
slug: /2026/02/20/netlify
---
Just a quick one right now. Integrated the Netlify client allowing direct publish to Netlify.
Previous attempts were using the Netlify CLI, but after learning that Go has a Netlify client,

1
_test-site/posts/2026/02/20-success.md
View file

@ -4,7 +4,6 @@ title: Success!
date: 2026-02-20T22:59:18Z
tags: []
slug: /2026/02/21/success
---
Okay, publishing from the frontend works.

10
_test-site/posts/2026/02/21-have-got-the.md Normal file
View file

@ -0,0 +1,10 @@
---
id: oV-tykrLgCoo
title: ""
date: 2026-02-21T23:08:52Z
tags: []
slug: /2026/02/22/have-got-the
---
Have got the post list looking decent. Although the edit links don't go anywhere.
But maybe if I try to update this post everything will work out okay.

8
_test-site/posts/2026/02/21-with-a-bit.md Normal file
View file

@ -0,0 +1,8 @@
---
id: OlI4xZu7SSS2
title: ""
date: 2026-02-21T22:11:28Z
tags: []
slug: /2026/02/22/with-a-bit
---
With a bit of luck, this should only be published locally, and not to Netlify.