Closed xynydev closed 7 months ago
Name | Link |
---|---|
Latest commit | |
Latest deploy log | https://app.netlify.com/sites/cozy-cascaron-6c7990/deploys/65db7066985bf306e676cab6 |
Deploy Preview | https://deploy-preview-28--cozy-cascaron-6c7990.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
It would be nice to have date of the blog sorted in left pane behind "All posts"
So newest would show 1st
It would be nice to have date of the blog sorted in left pane behind "All posts" So newest would show 1st
Thanks! That's implemented on the blog front page, but forgot it in the sidebar.
I first set out to document all possible migration paths, but now I'm not certain if "Create a new repository" should be included at all. I thought it would be the "lazy option" but it sounds way harder than the other one and has more cons.
I first set out to document all possible migration paths, but now I'm not certain if "Create a new repository" should be included at all. I thought it would be the "lazy option" but it sounds way harder than the other one and has more cons.
What are the cons with "Create a new repository" approach
What are the cons with "Create a new repository" approach
Listed in the draft post. Getting the error is one too.
Ok, the post doesn't have any glaring TODOs now, so I won't have to stress about that anymore. I wrote some general info in the OIDC section. I'd still like to have others review a bit of what I'm writing here. It'd be nice to know if there's any more new features I should mention, or if I'm wrong about some OIDC detail or smth.
I replaced the URLs now (b3fca65), so the PR is ready to merge whenever everything else is, once I get some comments ofc. This will cause builds to fail, but they should start working again once the repos are moved.
I'll probably keep the "create new repository" -section. Listing it as "not recommended" is enough for now.
This PR adds blog functionality with an introductory blog post to the site. The blog post should be written and ready before the repositories are moved from Universal Blue, along with a PR cleaning up th Universal Blue website and a shorter blog post that mirrors this one.
Here's a screenshot of the current state: