Seeking feedback from any who use webv4 - especially if you've customized the stock pages or added new content or sidebar modules to your site. If this doesn't apply to you ... uh, don't read this, because it'll be very long and boring for you.
No objections from me. As for the update process, feel free to add stuff to exec/update.js if it
helps (when relevant).
Re: A 'mods' directory for webv4I symlinked most (all?) the .examples/* files to their parent dirs. And pages/More/.examples to pages/More. But I don't have any uncommitted local changes, so won't be a problem for me.
By: Digital Man to echicken on Wed Sep 23 2020 14:45:54
No objections from me. As for the update process, feel free to add stuff to exec/update.js if it helps (when relevant).
I was thinking about that earlier, and it'd be a good fit for update.js.
The only people I can see this causing problems for are folks who are using webv4 from a git-controlled directory. They might have copied eg. pages/.examples/* up one level, where there were no files before by default; now they would conflict with files from the repo.
I'm not sure if anyone's using it that way. If they are, I hope they don't mind making a small adjustment. Or perhaps I can find another way around it.
|Nodes:||4 (0 / 4)|