Ken,

great module.

I've implemented _part_ of what I am guessing this module will be doing as a 2nd roundhousekick of the Chuck module. Well, that one previews main HTML elements only, though.

In any case, would like to see what you have in mind and help if I can.

cheers.

Comments

markabur’s picture

Version: » 7.x-1.x-dev

Yes, this looks great. It actually helps solve a problem I've been thinking about lately, how to show clients what markup we intend them to use when we hand over the site.

agentrickard’s picture

Patches and documentation welcome. The API needs some work, but the structure is all here.

We also have some UI questions about how to display elements without disrupting the display of those elements.

Do either of you want CVS access?

markabur’s picture

Sure, why not? :-) Kinda wish it was git access but here we are!

agentrickard’s picture

@markabur

You need to apply for CVS access first. http://drupal.org/node/59

We'll see about using GIT as well, but I prefer to maintain code on d.o.

sun’s picture

Just wanted to leave a quick note that the Drupal core markup team is already working on a project/module that seems to be very similar. Even some of the code looks partially almost the same. However, I'm not yet sure whether I understood the purpose/goal of this project, so I can't really tell whether there is room for joining forces.

apaderno’s picture

FYI, markabur is now co-maintainer of this project.

markabur’s picture

Thanks folks, co-maintaining is new for me so I'm sure I'll have a lot of questions and generally not know what the heck to do at first. :-) And @sun yeah it would be good to see what they're working on; I'll dig around a bit.

agentrickard’s picture

@sun Is there a project link?

agentrickard’s picture

Since @markabur is new to project management on d.o., I dialed back his access to CVS commits.

@markabur See http://drupal.org/project/styleguide/cvs-instructions for basics.

agentrickard’s picture

@sun

The purpose here is to give site admins / themers and clients instant access to common theme items for proofing. Think of them as visual tests to prevent a site from launching without, say, a custom theme addressing table spacing.

irakli’s picture

Ken,

CVS access would be great, if you don't mind.

Thanks

agentrickard’s picture

Done.

Note that I am being very generous and trusting here, and not at all possessive of the code. We now have 5 maintainers with commit access, and 4 with release access. So, some guidelines:

-- I have not integrated my workflow to GIT yet, so expect to do everything in CVS. We should open a new issue to discuss GIT.

-- I branch code like Drupal does. HEAD is new features / current release. No need to branch right now unless someone backports a DRUPAL-6--1-0 release.

-- I always keep a detailed CHANGELOG, which is in CVS now. Use it, please.

-- There is a styleguide.api.php file. It needs love. Give it some.

-- We need a README and help docs.

geerlingguy’s picture

I would like to work on a D6 backport. I may also work on docs...

agentrickard’s picture

@geerlinguy is the newly minted D6 maintainer and now has CVS access.

geerlingguy’s picture

Thanks! I'll get to work on this in a week or two, once I get another small project complete.

squiggy’s picture

I would like work on this module. Would you mind adding me as a maintainer? Or should I start with patches?

Everyone I have talked to who does design or front end development for Drupal loves the idea of Style Guide.

agentrickard’s picture

How about some patches / reviews first and then we'll promote you?

I'm really looking for an active maintainer, as no one is really doing much here.

squiggy’s picture

Yes, this is something I am interested in actively maintaining. I'll start submitting patches. :)

agentrickard’s picture

Awesome.

I will review and commit quickly :-).

chrisjlee’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.