Archetype

@dredurr Hi Deandre, thank you very much for your comment. We created the video as a first pass at some onboarding but have some plans for some more integrated guides as to what to do and why when first landing on the site. We also had ideas for a 'Typeschool' that can teach more about the underlying best practices Archetype is based on. If you'd find any of those things useful would be very keen to hear your thoughts

@moyicat Hi Samantha, thank you very much for your feedback. The text currently sits in the middle of the lines due to the way CSS line-height works, it adds padding above and below the text to achieve the desired spacing. There are some fiddly work arounds to try and set the text to the baseline but we wanted to keep things as simple as possible with this first version. I'll let @jamiegilman wade in here if required as he is the front-end expert. Thank you again for the comment, just the kind of feedback we need. If you have any other thoughts do please let us know

@martinollivere @jamiegilman Yay so happy that you want to look into it. Check out https://github.com/jakegiltsoff/... . I like their approach for baseline alignment with SASS mixins.

@moyicat @jamiegilman That's great, thanks for sharing

@moyicat @martinollivere Thanks for your input Samantha, and for the Sassline link, it's very interesting. The difficulty with aligning directly to the baseline of the grid is that the cap-size of the font family is required for the calculation, which is different for each font family and isn't available from the Google fonts API. It could be that we provide an input field for the user for the cap-size of the font family, and in the same way as Sassline, the user would tweak this to get the right value. It's an interesting feature we'll certainly consider, especially if we have more similar feedback. Thanks!

@jamiegilman @martinollivere Yup definitely more complicated to allow that ... I think a dynamic slider would be a nice UI for people who are not familiar with the cap-size concept.

@milesroxas I came here to ask the same question. Shouldn't 16px be the equivalent of 1em, since it seems to be the default browser font size? The only explanation I could figure out (since I couldn't find one reason documented anywhere) was that it makes typography sizes easier to convert from ems to px. If 10px = 1em, then 1.6em = 16px, 2.5em = 25px, and so on. If 16px = 1em, then 1.6em = 25px (which is not so easy to deduct), 2.5em = 40px. Do you see what I see? One would stop needing the px to em convertors. Or I may be getting to the wrong conclusion, but I can't find any more information on why 1em should be set to 10px.

@milesroxas @mauricio_gonzalez1 Hey, you can now set the root font size now so it's not fixed at 10px - we had a lot of feedback on this. It's in the modular scale settings. Hope that's helpful...

@likalo_llc Hi there, thank you very much indeed, please tell them to get in touch with any feedback they might have after using it. Much appreciated

@nimrodgavish_ Hi Nimrod, thank you kindly for your great feedback. One of the features we are looking into doing next is adding the ability to use fonts that you currently have on your machine so hopefully this would be a valuable addition for you. Also I appreciate the UI feedback, we'll be tweaking bits and bobs over time and that's just the kind of input we need to improve things so thank you. I'll let @jamiegilman answer your CSS question as he is the front-end developer on this project and I am a mere designer

@nimrodgavish_ Hi Nimrod, thanks for your input! The CSS does indeed provide the spacing between different HTML elements you may have set up. This is done using the adjacent sibling CSS selector and calculating the margin-top of the following element. For example, if you wanted to close the gap under an h1 where an h2 follows, the CSS output would be h1 + h2 { margin-top: -3rem } (or whatever the correct calculation is for your settings, which is dependent on the margin bottom of the h1). The CSS output is fairly crude at the moment as a first version, but we will discuss improving the output to group common styles, and perhaps provide as Sass syntax also. Do let us know if you have any problems or would like to see further improvements. Thanks

@richardsison Hi Richard, thanks for that feedback, we'll look to change the UI so the 'coming soon' link is visible at all times and not just on hover to avoid that happening in future. If that export feature is something you are keen on we'll let you know when it's up and running. If you have any other thoughts please do let us know, all feedback is very much appreciated

@martinollivere thanks for getting back to me. I definitely would like to be informed when it's up! Cheers. Does the sketch export create text styles or just a document? Would be good to be able to many the styles before exporting. Only other future idea would be having an account with projects. Awesome start though!

@richardsison This is great to hear as those are the 2 features we are going to be working on as a priority (export to sketch and saving projects). We'll be sure to let you know when these are ready to try out. Also in answer to your question we're just scoping out exactly what we want from the Sketch export. When you said above 'good to many the styles before export' what were you referring to? This would be great to know as we spec this up. Thanks again for your time

@martinollivere Whoops… was on the train when I wrote that. Bloody autocorrect. What I meant to say was "name the styles before exporting". So if you could create extra styles, and name them that'd be awesome.

@richardsison that makes more sense :) Great, thank you again Richard, I've added that to our list