[#21006] - [4.0] New Backend Template
- Fixed in Code Base
- 9 Jul 2018
- Medium
- Build: 4.0-dev
- # 21006
- Diff
- wilsonge:new-template
User tests: Successful: Unsuccessful:
This is the main body of work on the redesigned backend template per @svom and @coolcat-creations awesome new design in the Joomla Magazine from November.
Clearly this isn't finished but should be as useable as the current one (so yes that means it's missing mobile design, it's missing RTL etc)
This is a PR so that some basic sanity testing can happen before it is merged and so the system tests can be fixed
TODO BEFORE MERGING
- Fix system tests (probably merge joomla/test-system#45 and then swap the default branch here back to the main 4.0-dev branch)
- Fix hound (it only errors on the compiled es5 files and a boostrap vendor file so i guess it's just setting up the right ignores)
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_admin com_associations com_banners com_cache com_categories com_checkin com_config com_contact com_content com_contenthistory com_cpanel |
| Labels |
Added:
?
|
||
I know the menu has changed but why have the admin presets been removed? The ability to import preset is still present but now errors
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-07-09 23:49:36 |
| Closed_By | ⇒ | wilsonge |
Someone tell me it's an intentional decision to not link to the module manager ANYWHERE but the control panel quick icon please.
@coolcat-creations
I do not have this layout here at all. Including the icons
I just updated an existing test site via eclipse. Anything I should do?
@infograf768 - as @wilsonge stated in the PR it's absolutely not in the state to be finished ...
Please take the invision prototype and the jcm article as a reference...
@mbabker the menu transformation is not complete atm! There are still items that need to be removed from the menu and others that need to be added (eg modules), the first step was to get the 2 views system and help in place and then patch the rest. This is not the final, production ready code, even the menu logic (js) is not yet updated, so please bear with us as we’ll try to finish this task
It would be really good if only production-ready code would be commited to this repository... It doesn't look like this PR was ready to be merged.
Please take the invision prototype and the jcm article as a reference...
No idea what it means but I will be patient.
Nevertheless please do add the Save and Close button separately.
We really miss that...
@Hackwar I think due to lack of people working on the other repo the decision was to move the code here so more devs can contribute and thus accelerate the process. The j4 menu is known to been far from production ready code since the first alpha, nothing new here
@infograf768 looks like this:
Source: https://projects.invisionapp.com/share/8SES9JLZB#/screens/267320995
Link to the article: https://magazine.joomla.org/issues/issue-nov-2017/item/3289-episode-iv-a-new-user-interface-for-the-joomla-backend
Link to the prototype (Mentioned in the article): https://projects.invisionapp.com/share/8SES9JLZB#/screens/266861164_Desktop_-_Login
@dgrammatiko I don't want to complain to much, because I've been guilty of this in the past, too, but I still want us to be able to release at any time with this repo. Merging unfinished code prevents that. From a quick glance, this is in the state of work-in-progress and thus not even in alpha state. Don't get me wrong, I value the work that is being done here, but I'd rather have this split up into X PRs which are only merged when ready. Even if it looks a bit strange from time to time because new code doesn't really fit visually with old code, at least everything would work...
but I still want us to be able to release at any time with this repo.
for reasons (that i don't agree with) it was decided that this was not to be the case at this stage of J4 development
1.4.1 Stable master branches
It is critical to our mission that the master branch of each major version of a Joomla product is always stable and ready for a release within a short time. This is supported by our Contributor Policy.
good that we have renamed the main branch to staging :-P
I've said since JAB that I'm also starting to tighten up on the stuff I'm merging as I understand the repo now needs to move towards stability. Getting the new template design in was the one last missing part. Given the existing template was also broken in many ways I'd rather stop getting PRs to fix something that is broken and getting replaced and put in something that is nearly as
PR for the missing module menu item: #21032
always stable and ready for a release within a short time
So how the heck an alpha or even beta version can be stable and ready for a release within a short time?
By definition alpha and beta are nowhere near production ready or have we also have another definition for alpha and beta in this project?
I'm confused
So how the heck an alpha or even beta version can be stable and ready for a release within a short time?
If you look at our staging (J3) branch, it is basically production ready even when not tagged at all. "Alpha" doesn't mean it is broken (it may of course but doesn't have to). It means that the API may still change. "Beta" also doesn't mean it is broken, but it is "Feature Complete" and we don't expect any API changes anymore. RCs are then when we don't expect any changes anymore to the stable release except when we detect some new bugs, languages are usually also frozen at this point.
See https://en.wikipedia.org/wiki/Software_release_life_cycle.
4.0-dev is a development branch so the rule doesn't apply, our staging branch should be always in a state that we can make a release in a short time frame. If we have a 4.0-staging branch, then the rule will apply.
I would say that as soon as the automated tests pass then this should be merged. its too big and unwieldy a pr to really comment on anything else right now. Especially as we know its not complete.