Skip to content

Conversation

@austinkregel
Copy link
Owner

No description provided.

@austinkregel
Copy link
Owner Author

austinkregel commented Jun 12, 2025

  • Make projects, and updates owner-only (user who created it, is the only one who can edit/delete/add plugins/themes)
  • Themes are still not extracting in the right location.

@austinkregel austinkregel force-pushed the improve-dashboard-page branch from e41eb59 to ff61d1a Compare June 12, 2025 06:26
@austinkregel
Copy link
Owner Author

austinkregel commented Jun 24, 2025

Features

  • Package repackaging (downloading the versions from github, and moving the folders inside to the structure Winter is expecting.
  • Installing packages & themes directly (currently has an issue with Winter installing a different version than expected leading to a failed direct install 😞)
  • Linking projects to a WinterCMS instance
  • Syncing projects to a WinterCMS instance* (right now you need to install other composer deps manually)
  • Package Change logs
  • Package documentation
  • Upgrade Guide for packages & Package licenses; turns out this is based on the plugin's source code, not the marketplace. Create an upgrade.md file, or a license.md file to get these to populate.
  • Core updates
  • Package and theme updates

@austinkregel
Copy link
Owner Author

Recently spoke with Luke in the WinterCMS discord about this project and he pointed me to the team's PR for updating the update manager parts of the code which also has a Storm update needed in order to get running.

I like the updates he and his team have put together, and I think moving to a more Composer based package manager is a huge win for the project over all. 🤔 That said, it does appear that development has slowed a little over there. I plan on joining the development effort to help push it forward some; however, I would at the very least like to get Frostbreak up and running fully before joining their effort.

I want Winter's system to be finished, but I think this project is closer to an initial release, so I'm going to stay here until at least then.

Once Winter's plugin system has been updated to support composer based package management; I'll return here to update this project to support both methods (at least initially) before releasing some 2.0 version that supports winter's updated package management method only.

@austinkregel
Copy link
Owner Author

RE: Installing packages & themes directly (currently has an issue with Winter installing a different version than expected leading to a failed direct install 😞)

Luke had mentioned something in our brief conversation that I hadn't thought of. The packages can apparently be bundled with their respective vendor directories. So I'm going to explore possibly pre-packaging the packages with composer install --no-dev and see how successful that is with the latest version of Winter 🤔

@austinkregel austinkregel merged commit 5897914 into main Jun 25, 2025
1 check passed
@austinkregel austinkregel deleted the improve-dashboard-page branch June 26, 2025 01:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants