bit-badger/myWebLog
1
0
Fork 0
Code Issues 4 Pull Requests Packages Projects Releases 11 Activity

Revise theme experience #20

New Issue
Closed
opened 2022-07-16 15:23:37 +00:00 by danieljsummers · 1 comment
danieljsummers commented 2022-07-16 15:23:37 +00:00 (Migrated from github.com)
Copy Link

The theme experience within myWebLog can be convoluted, and adds multiple steps to the onboarding experience. To remedy this: (#19 is a prerequisite)

  • Modify the startup logic to look for -theme.zip files in the application root folder, and load those themes on startup, using the name of the file without -theme.zip as the slug. (Currently, the name of the file without .zip becomes the slug.)
  • Provide a theme maintenance page (visible to Administrator users). The admin theme should not appear in the list of themes.
  • When a theme is uploaded, load it into the database, and save the .zip file in the application root; when it is removed, delete it from both places. (Users may not upload admin-theme.zip.)
  • Deletion should ensure that no weblogs are currently using that theme; additionally, it should not allow the admin or default themes to be deleted.
  • Update the build packaging process to place admin-theme.zip and default-theme.zip in the application root folder rather than a separate directory.
  • Update the installation / upgrade documentation.
The theme experience within myWebLog can be convoluted, and adds multiple steps to the onboarding experience. To remedy this: _(#19 is a prerequisite)_ - [x] Modify the startup logic to look for `-theme.zip` files in the application root folder, and load those themes on startup, using the name of the file without `-theme.zip` as the slug. (Currently, the name of the file without `.zip` becomes the slug.) - [x] Provide a theme maintenance page (visible to `Administrator` users). The `admin` theme should not appear in the list of themes. - [x] When a theme is uploaded, load it into the database, and save the `.zip` file in the application root; when it is removed, delete it from both places. (Users may not upload `admin-theme.zip`.) - [x] Deletion should ensure that no weblogs are currently using that theme; additionally, it should not allow the `admin` or `default` themes to be deleted. - [x] Update the build packaging process to place `admin-theme.zip` and `default-theme.zip` in the application root folder rather than a separate directory. - [x] Update the installation / upgrade documentation.
danieljsummers commented 2022-07-27 02:37:05 +00:00 (Migrated from github.com)
Copy Link

This is complete; will be part of RC1

This is complete; will be part of RC1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area
infrastructure
Issues related to supported frameworks and libraries
area
podcasting
Issues related to podcasting / episodes
area
setup
Issues related to installation and setup
area
theming
Issues related to templates and theme
area
writing
Issues related to pages and posts
bug
annoyance
An issue that should be fixed, but is not a show-stopper
bug
footgun
Prevent preventable errors
bug
moderate
An issue that should be fixed with the next release
bug
urgent
A show-stopping bug; fix urgently
duplicate
enhancement
deprecation
Replace deprecated libraries with newer ones
enhancement
feature
A new feature to be added
help wanted
invalid
question
wontfix
No Label
Milestone
No items
No Milestone v2-rc
Projects
Clear projects
No project
Assignees
Clear assignees
danieljsummers
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bit-badger/myWebLog#20
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?