Is there any way how I can run Penpot app (for e.g. using Docker what works for me) locally where I can debug changes in code? By this I mean if there is some approach like when I run Penpot help, where I can see every change in code when running locally.
I saw that you have new Penpot site. Do you plan update also help center based on new designs? I’m offering you my coding experience so if you plan to change your Help site with same visual designs as Penpot site, I can code your Help center based on that.
I can do it without prepared designs (using your design foundations), but I’m not sure if this is something you would like to do. If this approach is also welcome, I can create changes based on your new Penpot site. Feel free to contact me - or can I be more active?
About the first one. Yes, of course. If you clone the repository of Penpot you can run ./manage.sh run-devenv and a development environment using docker containers will be up and running. The terminal it will open is a Tmux with 4 windows: 0- gulp 1- frontend 2-exporter 3-backend. So if you’re doing frontend development just change with “Ctrl+b 1” and you will see the compilation results.
About the topic 2. At the Help Center we will update the illustrations for the categories (user guide, faqs, etc) probably today. Nothing else is in our minds, as the rest of the look & feel (colors and typography) is still in line with the new web aesthetics.
If you have more specific proposals to update the Help Center we’d love to know about them and the reasons behind so we can have a clear idea before coding anything.
Thank you for reply @myfunnyandy. What I meant is changing for example color shades based on your main page, swap typography setting (line-heights, letter spacing, sizes, weights etc.) and font family (Source Sans Pro vs. Work Sans), small graphic details like border radiuses, button sizes etc.
Much clearer now, thaks for the explanation. I’ve discussed this with the design team and as long as changes are constrained to look & feel following the aesthetics of the new website and maintain content and structure we will feel confortable with your approach.
So yes, please go ahead preparing those changes, we’d love to see them.
Added new gray palette from Penpot site (I kept old one) and applied to (border, header, inputs, texts color)
Search input update: larger radius, border color, icon color and vertical alignment, inner padding, placeholder typography settings (kerning, indented from the left side)
Menu - font size change to 16px, font weight changed to Medium (500) - everything according to Penpot web, Added blu effect according to Penpot page
Cards (User guide, FAQ’s etc.) - changed border, inner spacing, description text darker gray from new palette, removed green border and shadow effect on hover (it’s softer then on Penpot page, because here it looks little bit aggressive)
Advice tag in Card (WIP) - try different approach, that fit more to rest of the page and does not look like buggy button. Please feel free to advice any changes here - it’s a bigger change.
Github section - change font size from 17.6 to 16px, changed dashed top/bottom borders color to new gray medium
Pre footer - changed dashed border color
Changed font size for leading intro text from 24px to 20px (because Work Sans have different propositions)
Polish typography settings (maily paragraph spacing because of new font)
Intro section cards (e.g. Quick Start, Interface) - align to the grid (see screenshot below)
And few more changes, that I will describe on PR if you agree. There you can see screenshot and video from updated version. Feel free to comment anything that you think should be changed. There is more things to improve (mobile version, heading settings in articles etc.) but I would like to start with this and confirm, if it add value for you.
There is screenshot and video from Homepage and detail:
Great and subtle job @ondrejkonec and great summary too. Having a reasoned, comprehensive list of changes helps us a lot to be able to accept them.
About the “WIP” tag, I like the new approach. Funny thing is that I was thinking on removing it as the purpose of it seems to be outdated. We’ve launched this documentation with very few information and we felt that this was neccessary to indicate that we kwen that a lot of content were still missing, and the situation is more than a bit different now.
About the search box, have you tried to write something there? It displays a list with the predicted results that had suffered some missalingments in the past. It might worth to check it this time.
Please go ahead with the PR, we’d love to publish those changes.
As it no longer serves its initial purpose you can remove the WIP tag. If it’s any inconvenience for you we can do it ourselves, of course.
Don’t worry about the search list, we’ll check that case when reviewing the PR. And I’ll be happy to keep discussing you more proposals. The Help Center has a lot of room for improvements at smaller/mobile sizes, so bugfixing sounds great.