Obvious
-
a caching strategy. currently contentHTML is called for Preview, Publish, and Export – often at the same time!!! there’s no hint to the plugin what if any part of the params dictionary has changed – so the whole of the content must be generated from scratch. i’ve made this request more than a few times over the years i’ve proposed a bunch of ways to improve that. but really anything that’s backwards compatible and involves not generating the whole page from scratch in real time would great.
-
make a workable public API so that this bummer stops. currently very few of my plugins actually work because the api methods used by older plugins have been marked private. and now keep fluctuating, breaking all my stuff, and making it hard to stay in business.
These first two groups are dev specific API stuff
API Stuff
- add notifications to let plugins know when resources are added/removed/relinked/whatever
- the current resource api makes it difficult/impossible to do basic things (e.g. create, delete, duplicate, rename, get info) without a lot of boilerplate and use of private methods. seems like working with user data should be simple, bullet proof, and easy to figure out (since it’s not documented beyond a few header comments).
- an ExtraFiles method for site-files that isn’t a class method.
Resource Specific API Stuff
more resource types. we can refer to a single project-wide file by using a resource %macro% – i’d like to see the same for other kinds of website building stuff too:
- colors
- links – so you can change a link in one spot and then everywhere it’s used around your site gets updated
- text snippets
- code snippets
The rest of these are more user-facing features
Page Specific Stuff
both the user and the API should be able to easily place content/code at more specific places:
-
top of the body
-
bottom of the body
-
page prefix (for php)
Yeah, some of these are possible by the API or by the user or at the discretion of the theme – but it would be nice if it was standard and consistent. -
instead of plugins having their own linked CSS file, RW should have a CSS api method and append, (sass compile?), then compress all both css files together.
Site Specific Stuff
-
dark/light mode detection for themes
-
other built-in open-source compression/tidy/validation stuff
- compress CSS
- Sass
- Javascript minimization
- Tidy
- Validation
-
a window (or whatever) full of quick access bookmarks – both project specific and global.
- project specific: for your site, test-site, store page, c-panel, host-support-site, etc.
- global: markdown ref, javascript docs, your favorite stack developer, rw-forum