Skip to content

Conversation

@dabeng
Copy link
Contributor

@dabeng dabeng commented Aug 8, 2017

Description

This is the sub-task of PTNFLY-2467.

@dlabrecq @dtaylor113 @jeff-phillips-18 @bleathem @LHinson
Based on the PatternFly Showcase Design[1], I've created a PR for updating the header.
The demo link is here: https://rawgit.com/dabeng/angular-patternfly/new-header-dist/docs/index.html#/api

@dtaylor113
Copy link
Member

Hi, top left links seem to be cut off:

image

Also, the "Components" and "Contribute" links don't seem to go anywhere and do not change the 'selected' state from "Getting Started"

image

This PR does not seem complete, customer ready. I'd be hesitant to merge this. Can we add a '[WIP]' to the title of this PR and consider not merging into master but rather to a dev branch until everything is ready?

Thanks,
Dave

@jeff-phillips-18 jeff-phillips-18 self-requested a review August 8, 2017 13:07
Gruntfile.js Outdated
styles: ['node_modules/datatables.net-dt/css/jquery.dataTables.css',
'node_modules/patternfly/dist/css/patternfly.css',
'node_modules/patternfly/dist/css/patternfly-additions.css',
'http://rawgit.com/junezhang/showcase/master/dist/styles/patternfly-showcase.css',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a patternfly based repo this could link to rather than an individuals repo?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Each repo should have it's own get started and contribute pages, specific with details and information for that particular repo. June has already populated the one for Angular 1 here: http://rawgit.com/junezhang/showcase/master/index.html

@jeff-phillips-18 @dtaylor113 does this information look up to date and correct? If so, @dabeng can we introduce this to the angular repo with this PR?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The README file needs some work which will then need to be incorporated into this. :(
I am working on updating it.

@dtaylor113
Copy link
Member

does this information look up to date and correct? If so, @dabeng can we introduce this to the angular repo with this PR?

Hi @LHinson, I'm not sure what you are asking? If this PR is merged it will go into the angular 1 repo, but IMO it is not ready to be merged (pls see my comments above).

@dtaylor113
Copy link
Member

I'm not sure how this PR works with PF Showcase? PF Showcase looks like this:

image

Whereas this PR/ngDoc looks like this:

image

Other than the CSS issues which @dabeng mentions, how do these integrate together? Are they supposed to look exactly the same? PF Showcase masthead title says "PatternFly Showcase", this PR/ngDoc masthead title is "PATTERNFLY ANGUALR" -not the same case/caps

@dabeng dabeng changed the title Update header of angular-patternfly API Docs site [WIP]Update header of angular-patternfly API Docs site Aug 9, 2017
@dabeng
Copy link
Contributor Author

dabeng commented Aug 9, 2017

@dtaylor113 , maybe you need the following processing.

screen shot 2017-08-09 at 11 35 34 am

@dtaylor113
Copy link
Member

@dabeng , thanks! That did the trick!

Currently, I linked an external css file[2], do we need to add an internal css file in this repo?

There are less files here for angular-patternfly, you can add your styles to these, or create another less file. It should be included in this PR.

Couple of questions/issues:

  1. The page June has created, is that "Getting Started" or "Contribute"?
  2. The ngDocs page, is that going to be "Components"?
  3. IMO all the masthead links need to goto appropriate pages before this PR can be merged.

Thanks!

@dtaylor113
Copy link
Member

@dabeng , extra credit if you can solve the 'ANGULAR Error' for the tab title :-)

error

@dtaylor113
Copy link
Member

Hi @dabeng, we just merged #554 which does automatic semantic releasing for angular-patternfly. You'll need to redo this PR's commit message to this format. -thanks

@dabeng
Copy link
Contributor Author

dabeng commented Aug 14, 2017

Hi @dtaylor113 , thanks a lot for your improvement advices :)

  1. I have created showcase.less under "styles" folder of angular-patternfly;
  2. The page June has created is "Getting Started" page.
  3. You are right. The API Docs is going to be "Components" page;
  4. I have updated the masthead links. While , standalone get-stared and contribute pages of angular-patternfly is necessary;
  5. IMO, I think it's also necessary to remove the "#" from the window.location;
  6. I think "extra credit" belongs to another scope, we can fix it outside this PR.

@dabeng dabeng changed the title [WIP]Update header of angular-patternfly API Docs site feat(API docs): update header of angular-patternfly API Docs site Aug 14, 2017
@dtaylor113
Copy link
Member

Hi @dabeng,
Ok, thanks for the update.
I see you updated the PR title/subject to include the semantic release format: "feat(API docs)", unfortunately this needs to be the commit message, not the PR title. You will need to do a 'git rebase -i' to change the commit message. -thanks!

@dabeng
Copy link
Contributor Author

dabeng commented Aug 16, 2017

Hi @dtaylor113 , commit message is modified accordingly.

<span class="icon-bar"></span>
</button>
<div class="navbar-brand">
<a id="logo" title="PatternFly Angular" href="#">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be 'Angular Patternfly'

<div class="navbar-collapse navbar-collapse-pf-site collapse">
<ul id="menu-primary" class="nav navbar-nav navbar-right">
<li>
<a href="get-startted">Get Started</a>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Misspelling. This is a broken link.

<a href="#">Components</a>
</li>
<li>
<a href="contribute">Contribute</a>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a broken link.

<a href="https://rawgit.com/patternfly/patternfly-react/gh-pages/index.html">PatternFly React</a>
</li>
<li>
<a href="http://www.patternfly.org/patternfly-css/">PatternFly CSS</a>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this is the correct link. It takes you to an inner patternfly org page which isn't formatted for stand alone.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This link is the only valid link for patternfly css.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That page doesn't look ready for prime time. Do we have an estimate on when it will be?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeff-phillips-18 sorry, not catch your point about the prime time.
This showcase list is a window for user getting to know what we are addressing in the framework implementation like the below picture.
screen shot 2017-08-22 at 3 13 21 pm

Even though some showcase projects are pretty new, like PatternFly-React, PatternFly-WebComponents, we also want user to see the progress, and welcome any contribution. How do you think about it? also here at @LHinson , want to hear any suggestions?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 with @jeff-phillips-18. The CSS should be linked in the future but we aren't ready yet. It should be removed for now and we can add at a later date.

<a href="">Menu</a>
<ul>
<li>
<a href="get-startted">Get Started</a>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Misspelling

</li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">
<i class="fa fa-th-large" aria-hidden="true"></i>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

aria-hidden=true and should have an sr-only span for "Patternfly Showcases"

Gruntfile.js Outdated
ngdocs: {
options: {
title: 'Angular Patternfly Documentation',
title: 'ANGULAR',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be 'Angular Patternfly'

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry Jeff, if do that, the heading will become "Patternfly - Angular Patternfly", Don't you feel it will be wired?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should end up as simply "Angular Patternfly", whatever that takes.

@jeff-phillips-18
Copy link
Member

jeff-phillips-18 commented Aug 16, 2017

the showcase.less file should be in misc (which is not less ready) not in styles. Putting it in styles will add it to the distribution and these styles should NOT be in the distribution.

@jeff-phillips-18
Copy link
Member

Not sure that I believe fixing:
image

is extra credit. It seems caused by this PR.

@dtaylor113
Copy link
Member

@jeff-phillips-18, unfortunately not. I see "Error: Page Not Found" in our published ngDocs

@dabeng
Copy link
Contributor Author

dabeng commented Aug 18, 2017

Hi @jeff-phillips-18 , I have moved showcase css code to folder misc and updated the details you mentioned above 😊

@jeff-phillips-18
Copy link
Member

Also, I don't believe this is a feat. No reason to bump the release for this. IMO, this is a chore since there are not distribution changes.

<a href="https://patternfly-webcomponents.github.io/components.html">PatternFly-WebComponents</a>
</li>
<li>
<a href="https://rawgit.com/patternfly/patternfly-react/gh-pages/index.html">PatternFly React</a>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see different formatting for the names

  • Patternfly-ng
  • Patternfly-WebComponents
  • Patternfly React
  • Patternfly CSS

These should either be the repo name:

  • patternfly-ng
  • patternfly-webcomponents
  • patternfly-react
  • patternfly-css

Or the titles:

  • Patternfly NG
  • Patternfly Web Components
  • Patternfly React
  • Patternfly CSS

@dabeng dabeng changed the title feat(API docs): update header of angular-patternfly API Docs site chore(API docs): update header of angular-patternfly API Docs site Aug 21, 2017
@LHinson
Copy link
Member

LHinson commented Aug 22, 2017

Add this comment inline above but will add here too...

The PatternFly PatternLab CSS should be linked in the future but we aren't ready yet. It should be removed for now and we can add at a later date. This is for the CSS.Next initiative.

@dabeng
Copy link
Contributor Author

dabeng commented Aug 23, 2017

@dtaylor113 , please review again.

@dtaylor113
Copy link
Member

Hi @dabeng, I notice a weird 'white-out' effect when I move the mouse pointer off of the app launcher icon:

image
image

@dtaylor113
Copy link
Member

Hi @dabeng, I don't know if GitHub is acting up at the moment but none of the links in the app. launcher seem to work:

  1. patternfly-ng hangs with "Loading..."
  2. web-components does go to another page, but masthead is white?
    image
  3. patternfly-react results in "No server is currently available to serve your request".

Again, I don't know if GitHub is acting up or if these landing pages aren't quite done yet.

@junezhang
Copy link
Member

@LHinson @jeff-phillips-18 Okay, got it. I will remove the css part from the list.

@junezhang
Copy link
Member

junezhang commented Aug 25, 2017

@dtaylor113 Thanks for pointing the "white-out" bug, I've fixed this bug on here - http://rawgit.com/junezhang/showcase/master/index.html
@dabeng please help to update. Thanks.

@dabeng
Copy link
Contributor Author

dabeng commented Aug 25, 2017

Hi @dtaylor113 @jeff-phillips-18 , I have updated PR according to your advices. Please review.

FYI, @dtaylor113 , regarding external links, I got the following snapshot, they looks great. Maybe the issue you mentioned above stems from internet or network agent.
screen shot 2017-08-25 at 2 02 15 pm
screen shot 2017-08-25 at 2 02 34 pm
screen shot 2017-08-25 at 2 02 56 pm

FYI, @jeff-phillips-18 , I have removed all unready links from the navigation bar.

</button>
<div class="navbar-brand">
<a id="logo" title="Angular Patternfly" href="#">
PATTERNFLY-<span class="secondary-logo" ng-bind-template="<%= title %>"></span>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need the all caps PATTERNFLY here? Is this the design across all the showcases?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes @jeff-phillips-18 , this is the uniformed design across all the showcases.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So are other components PATTERNFLY - Patternfly NG, and PATTERNFLY - Patternfly Web Components? Seems redundant.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeff-phillips-18 It should be PATTERNFLY-NG, PATTERNFLY-REACT, PATTERNFLY-WEB COMPONENTS, PATTERNFLY-ANGULAR. so here <%= title %> the title should be ANGULAR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This repository has been around far too long to start calling it PATTERNFLY-ANGULAR. It has been known as Angular Patternfly and should remain that way.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeff-phillips-18 yes, we discussed it before. sorry for forgetting it.
so here the name should be ANGULAR PATTERNFLY, does it make sense?

<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">
<i class="fa fa-th-large" aria-hidden="true">
<span class="sr-only">PatternFly Showcases</span>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should use pfApplicationLauncher.

<a href="https://rawgit.com/patternfly/patternfly-ng/master-dist/dist-demo/#/">PatternFly NG</a>
</li>
<li>
<a href="https://patternfly-webcomponents.github.io/components.html">PatternFly WebComponents</a>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WebComponents should be "Web Components" to match the page it directs you to. The page it directs you to is titled simply "Web Components". Not sure who is responsible, but I would expect that page's title to be "Patternfly Web Components"

<a href="https://rawgit.com/patternfly/patternfly-ng/master-dist/dist-demo/#/">PatternFly NG</a>
</li>
<li>
<a href="https://patternfly-webcomponents.github.io/components.html">PatternFly WebComponents</a>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WebComponents should be "Web Components"

@dabeng
Copy link
Contributor Author

dabeng commented Aug 27, 2017

Hi @jeff-phillips-18 , If I use directive pfApplicationLauncher, could you tell me which file I put the following code in?

    $scope.navigationItems = [
      {
        title: "PatternFly NG",
        href: "https://rawgit.com/patternfly/patternfly-ng/master-dist/dist-demo/#/"
      },
      {
        title: "PatternFly Web Components",
        href: "https://patternfly-webcomponents.github.io/components.html"
      },
      {
        title: "PatternFly React",
        href: "https://rawgit.com/patternfly/patternfly-react/gh-pages/index.html"
      }
    ];
 
    $scope.label = ' ';
    $scope.isDisabled = false;
    $scope.isList = true;
    $scope.hiddenIcons = false;

@jeff-phillips-18
Copy link
Member

You would just use the patternfly version, not necessarily the Angular directive. I'm not sure you could get our directives to work at this point in the ng-docs template.

You could try if you like by adding a file in the misc directory as a controller for the navbar and put those settings in there (including this new js file in the 'scripts' portion of the ngdocs settings in the Gruntfile). Then setting the controller for the nav and using the directive. It would be interesting to get this working as it could lead to further changes to the page and more that we could control.

Changing to the simple Patternfly version of the application launcher is probably plenty though as there isn't much need here for any additional logic in the controller.

However, there may be some adjustments necessary as I'm not sure how well the application launcher will work outside of a PF horizontal or vertical nav bar. It should so you may need to file some issues and do some workarounds until it is fixed. This is a good test for its adaptability 😉

@dabeng
Copy link
Contributor Author

dabeng commented Aug 29, 2017

Hi @jeff-phillips-18 , I have applied patternfly application launcher in the new header.

@jeff-phillips-18
Copy link
Member

image

This is what I meant by needing some adjustments. The dropdown list is too far right (partially off screen), the arrow should be centered on the trigger.

.showcase header .navbar-utility .applauncher-pf .dropdown-menu {
margin-top: 0;
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dabeng you missed one piece of css code here

.dropdown-kebab-pf .dropdown-menu.dropdown-menu-right::after,
.dropdown-kebab-pf .dropdown-menu.dropdown-menu-right::before {
right: 10px;
}

@dabeng
Copy link
Contributor Author

dabeng commented Aug 31, 2017

Hi @jeff-phillips-18 @junezhang , I have updated showcase.css and got the following snapshots:
screen shot 2017-08-31 at 12 28 49 pm
screen shot 2017-08-31 at 12 29 01 pm
screen shot 2017-08-31 at 12 29 07 pm
screen shot 2017-08-31 at 12 29 16 pm

@jeff-phillips-18
Copy link
Member

I'm not seeing this fix when I build/run.

@dtaylor113
Copy link
Member

Sorry, what are the differences between the screenshots?

@junezhang
Copy link
Member

@dtaylor113 I think the difference between the screenshots is in different browsers, what they are looking like.

@junezhang
Copy link
Member

junezhang commented Aug 31, 2017 via email

@dabeng
Copy link
Contributor Author

dabeng commented Sep 1, 2017

@jeff-phillips-18 , maybe you can clean up your browser cache or directly review the build/run results on this address -- https://rawgit.com/dabeng/angular-patternfly/new-header-dist/docs/index.html#/api

@dabeng
Copy link
Contributor Author

dabeng commented Sep 1, 2017

Hi @dtaylor113 , I listed snapshots in order to demonstrate that patternfly application launcher menu has the same styles in different browers 😊

Copy link
Member

@jeff-phillips-18 jeff-phillips-18 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dtaylor113
Copy link
Member

Hi @dtaylor113 , I listed snapshots in order to demonstrate that patternfly application launcher menu has the same styles in different browers

Hi @dabeng, ok, thanks for the explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants