An update to that is coming. Short answer is we have to generate a new mid-size for all of the Completed Build images and that takes some time.
We've had several requests for those 4 links to be moved back by the search bar and that change is coming.
We're working on a fix for that, but can you let us know which browser and OS you're running?
Can you provide details about what you don't like about the comment formatting?
Hmm, can you point me to a page that is giving you this issue? The highlight color we're using is not the default color and it does blend into the page more so than the header and footer, so perhaps that is what you're noticing. Increasing the contrast of the highlight color is an easy tweak, I can look into that. If however you're completely unable to select text then that is a bug and something I'll also look into.
The experience on tablets and phones will improve. We’re working on ways to show more content when the screen dimensions limit the available space. We’re also working on improving the logic around what columns we prioritize per component type.
Same color scheme with a couple very slight shifts in tone. Last site didn’t have a dark mode but this one will soon. It’s one of the main features I have lined up to add next.
We tightened up the spacing in the part list page. Your comments are constructive so please feel free to share more if you see other areas we can continue to fine tune the experience.
I just wrapped up adding back in part reviews, completed builds using this part, compatible parts, and build videos with this part to the product pages. Those should show up any min now.
They’re coming, I’m working on adding them back in now. Thanks for the feedback!
Yes. We built CyclingBuilder in tandem with the work we did on the new responsive templates and I've been working lately on getting PCPP up on the same templates. Still ironing out styling as well as finishing out some pages that CyclingBuilder doesn't have yet (Completed Builds, Blog, etc) but it's coming along nicely. :)
The ability to compare products will be included in the new responsive templates which are coming soon: https://pcpartpicker.com/forums/topic/312357-disabling-the-mobile-version-of-the-site
I saw that topic when you posted it a couple weeks ago. What you were seeing tied exactly into our reasoning to explore a new typeface approach. The typefaces we were using via Google's Font service regularly gave us headaches. Most of the time they'd display fine and then all of a sudden they'd be bolder in some cases or only on certain characters or even partially bold on half of a character. Those bugs were symptomatic of using that service and those fonts and so we made the decision to move to a local font stack.
While font rendering has improved, the sizing is something we'll continue to massage and improve. The previous typefaces were different enough in x-height and form that simply pointing to a new font family didn't mean the job was complete. I spent time adjust font sizes in various areas in effort to maintain parity with what we had before as well as aiming for optimal legibility given the new typefaces in use. My goal is to continue to iron out the details as I continue to comb through templates and receive feedback.
Ah yes. That is the way Georgia draws numbers: Wikipedia Type Specimen In your example of the partlist however I have a pending update coming which renders these in sans-serif, which will look a lot better.
You'll see Roboto on devices using Android. Is that the case for you? If not then it might be something I need to look into.
Part names and prices have always been bold. It's possible they just stand out a bit more than with the previous font. Can you give me an example of the higher/bigger numbers you're referring to?
If you're on Windows it's "Segoe UI" for the sans-serif. If you're on MacOS it's "San Francisco" for the sans-serif. Both are native to the platforms. The serif font is Georgia.
The beauty of using system ui fonts (i.e. OS specific typefaces such as Segoe UI for Windows, San Francisco for MacOS, etc) is they're drawn specifically for those environments. The cleanliness you're seeing is a result of this approach. Thankfully the system ui fonts are all sans-serif and very similar in stature and form. </typographynerdout>
The header change is actually a bug on my part. I just fixed it internally so I public update will be coming shortly. I'm working on fixing the spacing on the quote blocks as well. Good catches!
I emerge from my design compound only when pixels are abused or the justification for white space is challenged.
Very astute of you to notice uberlizard! Yep, we pushed up font changes earlier today. The previous font stack gave me too many "head slamming into desk" headaches when trying to solve browser rendering bugs. The new stack uses system ui fonts, ones specific to the OS, which allows optimal font rendering for everyone. Changing fonts might appear to be a simple code switch, but required going through all of our templates and CSS declarations to make sure everything displays correctly. If anyone finds an issue please let me know.
Which version of MacOS are you using? I'm trying to see if I can reproduce this issue on my end.
I'd have to look at the individual photos to see. I leave the shutter speed up for the camera to decide and dial in the aperture I want. Most of the photos are taken at f5.6.
I used to shoot with a Nikon DSLR but got tired of juggling multiple lenses. One of the things I love about the X100T is it's size and that it's a fixed lens system. The size entices me to carry it around more frequently. The fixed lens limitation forces me to be more creative with my shots and I love not having to worry about bringing along other lenses. My wallet appreciates that as well.
Not sure, I've never used the camera on a Note 4/5.
Thanks MannyPCs. I've been taking the photos lately for our builds and use my FujiFilm X100T. I make some minor adjustments in Lightroom before submitting them for use in a build. Glad you like them!
I've been working with another staff member lately on a brand-new, responsive front-end system that we intend to rollout. One of our goals with this is to create much more continuity from a user-experience standpoint with the site, no matter which screen you access it from. This doesn't replace a native app experience, which as Boyscout mentioned is something we're working on and serves unique purposes. We still have a fair amount of work to do to get the responsive framework finished and in place, but I'm very excited about it!
I'd just like to add that squashing this bug provided much needed sleep to all of the Philip's employed at PCPartPicker.
Ah good catch on that. I added code awhile back that addressed this issue originally but looks like there are still some outlying instances. Thanks for the heads-up!
Yep, looks like another font update from Google. I'm currently looking into the issue and a replacement font to hopefully avoid issues like this in the future.
Thanks Jipster, I'm really appreciate your kind words!
No one takes anything of mine within a logo without my knowing it.
Allow me to lay your mind to rest:
The laptop is a standard laptop, so imagine you are looking at it on a flat surface, up and to the left of center. The other portable devices are rotated 90deg in relation to the laptop, screens facing you.
And yes, that is a phone. :)
Pretty sure we could make that available.
Thanks! Lavins and I came up with the concept for the lower-thirds and then I animated them in After Effects. The key-framing isn't too complex. Basically I'm animating the height and position of the yellow line and then the width of the masks which show and hide the text elements. The trickiest parts are making sure all of them are in sync with the custom velocity settings I have for the keyframes. I obsess over those details though. :)
This rig will primarily be used for Photoshop, After Effects, and Cinema4D work, not video editing. We're already shooting in 4K but Blake (Lavins) handles all of that and built his rig to support the beefier files. Any 4K video work I produce in C4D and AE will be short, things such as intros, outros, lower-thirds, etc for our video content. The rest of the graphic work will be focused on still imagery and assets for the site. I opted for the SSDs because of their read/write speed.
Beautiful photography work Laquel!
Thanks for the feedback! This is one of several small improvements we made when doing the major site overhaul and it's great to see it's noticed and useful.
Awesome! :) Since the launch of the redesign we've been working hard on tweaking areas, improving layouts, adding new features, etc and are continuing to do so.
Yep, it has to do with the contents of some comments adjusting the structure of the page and therefore causing issues such as the squished avatars. Long links are typically the culprit. We're aware of the issue and working on a fix. Thanks!
Thank you sir! :)
Yep HTML5, CSS3 and other libraries and languages.
I agree part images help, especially when browsing for cases. It's hard to come up with a way to show part images on the detailed list view and still keep that view tight so you're able to show a lot of parts at once. That's why we have the list view, which now features larger thumbnails. These views are critical to the site so we're continuing to refine them to be the best they can be.
We have an update coming soon that will make deleting saved builds a lot more obvious. Currently if you go to your "Saved Part Lists" page there's an "Edit Description" button next to the title of each list. That will take you to a page with a delete button at the bottom.
We're working on a better solution for this because it's not obvious, but currently you can delete/rename a saved part list by going to the Saved Part Lists section and click on the "Edit Description" button at the top right of the Saved Part List details on the right. On the next page there's a delete button at the bottom and if you click "Edit" next to the Description or General areas you will go to an area where you can change the title.
We've heard reports of this from a few users and are working on fixing the bugs causing it. Which browser and OS are you running?
Yep, this was a bug. We pushed a fix earlier today so should be working for you now. Thanks for bringing it to our attention!
Hey awesome, glad to hear you like M&C!
Making sure that what makes PCPP so great stays great (design, speed, etc) is very important to me. That's a major focus of mine.