nickberens360
"Copy" functionality not working
Doesn't seem to work locally, or on the web demo. I'm using the latest version of Chrome if that's helpful at all.
Also, a couple of other questions that I'm curious about...
1. Is it possible, on initial load, to display the first category automatically? When I go to Atomic Docs locally, I get the sidebar of categories and a blank starting page. It isn't until I click a category that it displays anything.
2. Is it possible to write SCSS within the SCSS files, but show vanilla CSS on Atomic Docs? I don't think someone consuming a design system is going to be looking for the SCSS output to build whatever they're building (let's say a web page). They're going to be looking for the CSS output. I can see a use case for displaying both SCSS (for Developers) and CSS (for consumers), if that's possible.
@ryanaltvater The copy feature is flash based so it's basically useless at this point lol. In the upcoming version it's js based however.
-
As far as the initial page loading the first category, yes this is a good idea. I have stopped adding new features to this version however and will only work on fixing bug issues until the new version.
-
Honestly I don't really see value in having the compiled CSS shown. Can you provide a use case for the need for it?
Thanks for checking out the project
@nickberens360 Oh, nice! When is the new version coming? Is there any way that I can get a beta test of it? I'm part of a new team over at Red Hat and I'm leading the charge on starting a design system for said team. I'd love to be a part of the latest and help provide feedback (even in beta form).
As for a use case, I tried to explain that in my initial question. Basically, a design system is something that is consumed. It's built by Developers so that someone else that's not a Developer can understand, consume, and implement code on the fly without the need of a Developer. Our design system will be used across teams (Red Hat and 3rd-party agencies) that have the ability to create pages within our CMS on their own. Some of the pages that we build will already have the full CSS file called on the page, opening up the ability to use our DS code. Some of the pages that other teams build may be a mixture of our DS patterns and 3rd-party patterns. Finally, some of the pages may just borrow a single pattern or component on a page. It wouldn't make sense for that page to call an entire CSS file for just a single pattern/component when you could just add that snippet of SCSS/CSS to your own SCSS/CSS files (if you're a Developer) or add it to an inline CSS field within a CMS (if you're not a Developer). My suggestion for displaying both SCSS and CSS would be to accommodate all situations and environments, whether there's a Developer or not and whether they're using SCSS or not.
@ryanaltvater Ahhh ok gotcha. Most people seem to have been using atomic docs on a project by project basis and mostly as a dev resources. I can see how a compiled tab would be useful. I'll definitely add to my list for the next version.
As for a time frame for a beta release, it's probably going to be a little ways out. I'll certainly keep you in the loop though. Thanks!