Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates to layout/theming #118

Closed
wants to merge 9 commits into from

Conversation

MyNameIsCosmo
Copy link
Contributor

@MyNameIsCosmo MyNameIsCosmo commented Nov 24, 2017

  • Initial changes to front page theming for better readability.
  • Added a "Recently Added" feature of 6 items below Featured Robot.
  • Sort listings alphabetically
  • Ribbon for robot category for easier category recognition

changes

@MyNameIsCosmo
Copy link
Contributor Author

There's more updates coming.
I'll submit another pull request sometime tomorrow, and any desired features can be cherry-picked upstream.

Copy link
Member

@tfoote tfoote left a comment

Choose a reason for hiding this comment

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

Thanks for these suggestions. I've commented on several of them that look good. You closed this and mentioned that you're looking at making some more suggested updates. Is that still pending?

_site
node_modules
_drafts
localtest_config.yml

# Temporary Files
Copy link
Member

Choose a reason for hiding this comment

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

These os/system specific things I recommend adding to your global git config instead of adding them to all projects.

{% if post.title == site.featured_robot %}
<a href="{{ post.url | prepend: site.baseurl }}"><span>Featured</span></a>
{% endif %}
<a href="{{site.baseurl}}/category/{{post.main-class}}"><span>{{post.main-class}}</span>
Copy link
Member

Choose a reason for hiding this comment

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

We used to have this on all posts but the number of ribbons seemed overwhelming so we reduced their usage.

</span>
<div class="box-body">
<!-- <meta itemprop="datePublished" content="{{post.date | date_to_xmlschema }}">
<time itemprop="datePublished" datetime="{{ post.date }}" class="date">{{ post.date | date_to_string }}</time> -->
{% if post.vendor %}
<span class="post-vendor">
{{ post.vendor }}
Copy link
Member

Choose a reason for hiding this comment

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

Adding a vendor is a great addition. I'd like to do this in a way that we can generate cross references for vendors with listings of their robots. This might want the ability to have a small vendor profile with a sentence, link, and logo.

Copy link
Contributor Author

@MyNameIsCosmo MyNameIsCosmo Nov 28, 2017

Choose a reason for hiding this comment

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

I'm working on 2 forks for this repo:
sensors.ros.org - http://wiki.ros.org/Sensors to Jekyll GH-Pages
vendors.ros.org - List of contractors, distributors, educational, manufacturers, and vendors for ROS-related products and services

This would help organize and add to the collective knowledge of various companies, components, sensors, and robots in the ROS ecosystem.

What are your thoughts on this?

Copy link
Member

Choose a reason for hiding this comment

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

It would be great to capture that information. However I'm not sure that spreading it out over several domains makes sense. That seems like it will start to become a maintenance burden. We already have a Sensors category. If there are sensor specific templates we can relatively easily customize those for the category. And similarly for the vendors, they're going to be closely coupled to the robots here so separating them out would just significantly increase the likely hood of broken cross references. And for both I don't think we're at much risk of having colliding namespaces between any of these categories so I'm not worried about the URLs. We could push the vendors into a namespace lie /vendor/*.

@@ -4,5 +4,20 @@ <h1 class="logo">
<img style="height: 33px" src="/assets/img/ros_robots.png"/>
</a>
</h1>
<table id="topnav-table">
<tbody><tr> <td valign="middle">
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 definitely something we should add.

Copy link
Member

Choose a reason for hiding this comment

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

This seems to disappear when on small screens and overlaps when at itermediate widths:
image

It would be great to push it up above the site content like we do with the other sites instead of interleaving it.

Copy link
Member

Choose a reason for hiding this comment

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

Cross referencing #116


<H2>Recently Added</H2>
Copy link
Member

Choose a reason for hiding this comment

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

I wasn't aware of the limit: option this opens up lots of new capabilities for the home page.

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 testing this out and the limit doesn't seem to be rendering correctly with incorrect number and range of box items appearing. I think there's potentially an issue with the randomization logic for the main listing.

@MyNameIsCosmo
Copy link
Contributor Author

Yep, still working on some updates. I have looked over your comments, and will make some amendments later today based on your feedback.

I ran into a problem with the Liquid SaSS converter.
Finally found my issue; still working on a slight workaround for the lighten() and darken() sass functions to properly color the borders based on the background color. Partly due to the version of some liquid packages installed in my docker container.

I updated the docker file to use the same version packages as GH-Pages.

Should be pushing some more updates tonight, and reopening this pull request.

@MyNameIsCosmo
Copy link
Contributor Author

Ended up branching off the colors work, as I could not figure out the correct SaSS layout.
Attempts at using darken and lighten in scss did not bode well in initial tests.
I will alloc more time to some other GH issues when I get a chance.

Feel free to select which commits you'd like to see merged upstream.
Here's how the latest layout looks like:
robots-ros-org

Reopening this PR.

@MyNameIsCosmo MyNameIsCosmo reopened this Nov 29, 2017
{% endif %}
</ul>
</div>
<div class="post-container-icon">
Copy link
Member

Choose a reason for hiding this comment

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

I merged the box reformat with adding the category link back.

tfoote added a commit that referenced this pull request Dec 5, 2017
tfoote added a commit that referenced this pull request Dec 5, 2017
@tfoote
Copy link
Member

tfoote commented Dec 5, 2017

Thanks for all the contributions. I've merged many of them manually and ticketed a few of the remaining ones that I had some request for changes on. With the noteable conflicts, I'm going to close this PR. If you have more suggestions or want to revise some of the existing ones please open a new PR.

@tfoote tfoote closed this Dec 5, 2017
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.

2 participants