Switch out Flowbite UI for another framework such as Skeleton or Carbon

[v79]

I've created a test project using Skeleton. I think it will work for me, though some of it is quite different from Flowbite.

Steps will be:

• [x] Create new branch
• [X] Update Node/NPM from 18.17.0 and 10.2.3 to 20.11.0 and 10.2.3
• [x] Create new Skeleton project (in a new folder, so I can keep the existing Web project as reference)
• [x] Create application shell and routes
  • [x] posts
  • [x] create new post
  • [x] load post
  • [x] save post
  • [x] delete post
  • [x] pages
  • [x] load page list
  • [x] create new page
  • [x] load page
  • [x] save page
  • [x] save new page
  • [x] delete page
  • [x] create folder
  • [x] delete folder
  • [x] setting a page as the index/root for a folder?
  • [ ] templates
  • [x] create new template
  • [x] load template
  • [x] save template
  • [x] delete template
  • [ ] create, manage and delete template sections
  • [x] trigger regeneration of pages based on template
  • [x] media
  • [x] load image gallery
  • [x] upload new image
  • [x] delete image
  • [ ] project configuration
  • [x] load and save existing configuration
  • [ ] create, manage and delete custom attributes
  • [x] create, manage and delete image resolutions
• [ ] Configure a CSS theme for the project
• [ ] Generation menus
  • [x] Rebuild metadata
  • [x] Rebuild all pages
  • [x] Rebuild all posts
  • [ ] Rebuild image resolutions
• [x] Improve navigation, e.g. with proper page titles, and clearing stores on navigation
• [x] Spinner for long running tasks like generation and metadata regen

This will be a good opportunity to restructure the project based on what I've learned about SvelteKit so far.

[v79]

Making good progress and using this as an opportunity to rewrite code based on all that I have learned. Good progress, but slow. Can fetch and list the posts in the project.

[v79]

I looked at sveltekit's advanced routing to create different sub layouts - one layout for editors (pages/posts/templates) and one for other routes like project config and image gallery, but it was a lot of work for not a lot of gain.

[v79]

Having implemented all the core functionality for pages and posts, and basic functionality for templates, I am deploying to production. Then I will bump version numbers and progress with other features.

[v79]

I think I have done enough to close this branch down. The remaining things on the list were never part of the previous version, so I'm ahead of where I was.