You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
installation process now asks the developer which theme they want to install;
installation process currently favors installing CoreUIv2, so we can't say Tabler is the default just yet;
UPGRADE GUIDE - note all version of our packages that support Backpack v6, so it's easy for people to bump the version;
UPGRADE GUIDE - shouldn't we tell people to change all their custom pages to extend backpack_view('blank') because that's provided by all themes?
UPGRADE GUIDE: you should run php artisan backpack:install to properly install Basset and the theme;
UPGRADE GUIDE - shouldn't we tell people to delete their errors folder? if they haven't customized it with their own error views of course;
UPGRADE GUIDE - in v6 we define the uploaders in the crud.php config file; do we instruct people to add these in the upgrade guide? what happens if they don't do it? nothing; they will add them when they want to create custom uploaders; which is never;
i'm pretty sure the bp-section classes we've added aren't documented at all; see this as an example;
we should document how someone uninstalls a Backpack theme; for ex in the upgrade process we instruct them to use CoreUIv2, and only after everything is workding... install Tabler and uninstall CoreUIv2; but we don't explain how to do that (uninstall);
currently our docs don't do a good job at highlighting how much of a team effort Backpack v6 was; we MUST give credit where credit is due; we must mention our team members by name; and thank them for their efforts;
we should mention how much work has gone into v6, with numbers:
To document:
installation process currently favors installing CoreUIv2, so we can't say Tabler is the default just yet;UPGRADE GUIDE - shouldn't we tell people to change all their custom pages to extendbackpack_view('blank')
because that's provided by all themes?php artisan backpack:install
to properly install Basset and the theme;errors
folder? if they haven't customized it with their own error views of course;UPGRADE GUIDE - in v6 we define the uploaders in thenothing; they will add them when they want to create custom uploaders; which is never;crud.php
config file; do we instruct people to add these in the upgrade guide? what happens if they don't do it?UPGRADE GUIDE - in v6 all operations content class defaults to being wide (nah... let's let them keep their old width;col-md-12
); should we instruct people to do that in their upgrade guide?metas
and you can send variables to your buttons; is this documented anywhere?bp-section
classes we've added aren't documented at all; see this as an example;The text was updated successfully, but these errors were encountered: