[#229] - Add project short title, set standard site title, project name cleanup
- Closed
- 27 Nov 2013
- Medium
- Build: master
- # 229
- Diff
- joomla:projects
- Success default The Travis CI build passed Details
User tests: Successful: Unsuccessful:
In another move aimed for better consistency across the j.org network, I've reworked the main title displayed in the page header some. It will now always show as "Joomla! Issue Tracker" with the ability to append to it, used for the tracker pages. To keep the title from running too long, I've added a short_title field for the projects table and use that to display a unique appendix for the trackers. So now we display "Joomla! Issue Tracker - CMS" instead.
Point 2 with this is cleanup of the project names and aliases, ultimately aimed for a better experience. "Joomla! CMS 3 Issues" is shortened to just "Joomla! CMS" and its alias shortened the same.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2013-11-27 00:30:54 |
That was a quick merge 
Sorry :) I'm all about cleaning things up ;)
Thanks,
David Hurley
On Nov 26, 2013 7:34 PM, "Nikolai Plath" notifications@github.com wrote:
That was a quick merge [image:
—
Reply to this email directly or view it on GitHub#229 (comment)
.
Can definitely look at shortening the base title again, I just decided to go with the "unofficial official long title of this sucker" LOL
Just a small concern: Maybe, at some point, we can also host a feature tracker, an idea tracker etc.. so maybe we can change the title to just "Joomla! Tracker " ?
So while we're at it - I do also believe that the "proper" name for our project should be JTracker instead of JIssues - including the repo.
Also Issues should be treated as Tickets or Items in variables, tables etc. Note that the button already says "New Item"
But yes, that's just semantics and no release blockers... speaking of which
I'm all about cleaning things up ;)
Could we clean things up and either merge those open PRs or postpone them for after 1.0 ?
Yes please. In fact, I'd like to run through the open PR's and merge them in today if they're ready.
I want to keep progress moving FAST on this since the CMS is so slooowww :)
I have no issue with rolling with JTracker, including renaming the repo. Or dealing with the semantics of things (though they are called issues here on GitHub, just saying).
I want to keep progress moving FAST on this since the CMS is so slooowww :)
All my on this
(though they are called issues here on GitHub, just saying).
Yes sure - I mean the feature tracker (as well as the security tracker we are planing) are not supposed to be handled by GitHub (excluding parsing comment texts) ?
I have no issue with rolling with JTracker...
OK, be prepared - feel free to rename the repo when you feel lazy ;)
That'd be also a cool base title for the page... J!Tracker
A better experience sounds great ;)
Just a small concern: Maybe, at some point, we can also host a feature tracker, an idea tracker etc.. so maybe we can change the title to just "Joomla! Tracker " ?