How do I add space between blog entries on the main page?

[girlunstoppable]

On my main blog page, I've noticed that my posts look a little
cramped. I'd like to be able to add a larger margin between blog
posts, but I have no idea where to begin. Can someone give me
instructions on how to do this?

[Michael Heilemann]

Create a custom style, and add .post {margin-bottom: XXpx} where XX is
the distance you want.

> --
>
> You received this message because you are subscribed to the Google Groups "K2 Support" group.
> To post to this group, send email to k2-su...@googlegroups.com.
> To unsubscribe from this group, send email to k2-support+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/k2-support?hl=en.
>
>
>

--
/ M

[roguewave]

As someone that is invesing a lot of time, but is not a programmer,
I'd like to use this post as a point of discussion. I'm VERY grateful
for all the support & the superior work done by everyone. I would love
to see a wiki or some sort of roadmap so I can learn more & eventually
help others, as I have recieved help. Using this post, I still don't
understand what needs to be done in order to effectuate the change. A
small line of code and the palce where it goes might be a small
investment by the keepers of the flame to educate us newbees and bring
us along so one day we can be helpful to others. I asked many
questions re K2 in the general WP forums months ago & was treated with
such disrespect that I gave up. When I noticed that K2 1.0 was birthed
& that there was a seperate support group, I took the plunge again.

Is there a way to create a working road map of the code, almost like a
Talmud, that can have explanations of what the code does & that can be
commented on. A way to build a real time experience so that us non
programmers can design & show others how they can dip their toes into
K2 & WP. I've shown others my work in progress. They are anxious to
join the fray, but without a real referenced road map that has
explanatory power to the uninitiated, I fear that vast audience tis
saddled with canned themes, most of which will be defunct in months or
a year, might just give up.

In the end, I stand in awe of the product, the dedication & the
empowerment you offer. Don't take it for granted that the new users
are aware of what you assume we should now. I have read many books in
the past months, but nothing really compares with undertaking a blog
with K2 and trying to get it right. With all the talent here, I should
think we can assemble some written material that gives folks a road
map & suggestiions so they can be contributors to this wonderful
community. I'm not looking for a handout. I will do the work, but we
need a bit more contextual help. As in the above querry: "Create a

custom style, and add .post {margin-bottom: XXpx} where XX is the

distance you want". I don't know where it should be (if that's even
important), should that be a seperate style sheet or part of
style.css? Again, I'm all gratitude, but I just know there are any
more folks like me that want to learn & contribute. Tell us & teach us
how. Thanks, Ben
> .

On Jan 2, 3:00 am, Michael Heilemann <heilem...@gmail.com> wrote:
> Create a custom style, and add .post {margin-bottom: XXpx} where XX is
> the distance you want.
>

[Michael Heilemann]

Thanks for taking the time to write this.

Documentation and code-accessibility is a really hard thing to get right, and so far we (me, really) haven't necessarily been too good at providing the needed transparency.

Because of this, K2 isn't necessarily the best place to start if you're just getting your feet wet. It's a comprehensive template that does a lot of rather advanced things and to understand it all takes quite a bit of time. In turn I don't think any of us devs really expect newcomers to be able to use it to its full extent out of the box. For instance, where other themes aimed more at new people would use a GUI to select colors, we've opted to use CSS files instead. This requires some prior knowledge, but given that knowledge, offers a lot more flexibility.

This is unlikely to change anytime soon.

We'll soon start work on optimizing our CSS and class/ID structures to clean up some of the cruft that has settled over the years, and we'll probably also spend time on writing more thorough documentation and reference texts.

But at the end of the day K2 is a mixture between a theme and a framework, and as such it's aimed more at people like ourselves, who know their JS from their CSS, rather than as a starting point for new bloggers.

For more options, visit this group at http://groups.google.com/group/k2-support?hl=en.

--
/ M

[roguewave]

Michael, thanks. I think I'm up to the task. In reference to this
suggestion "Create a custom style, and add .post {margin-bottom: XXpx}
where XX is the distance you want." Where in the style.css file is the
best place to put the new style? I'd like to place it where it is
associated with other functions that are similar. Also, where does one
change the colors for the comments ? Lastly, I know there is sunction
in the style.css that allows for allowing only 1 post on the forst
page and also allowing comments only about that post. Where do I look
to implement that? I have photographs & photographic essays to
present, where I need the first page to be devoted only to those
images & rge comments & replies to follow. All the older posts would
be available on the second column. Thanks again for yourt ime &
consideration. Ben

> > k2-support+...@googlegroups.com<k2-support%2Bunsubscribe@googlegrou­ps.com>

> > .
> > > > For more options, visit this group athttp://
> > groups.google.com/group/k2-support?hl=en.
>
> > > --
> > > / M
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "K2 Support" group.
> > To post to this group, send email to k2-su...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > k2-support+...@googlegroups.com<k2-support%2Bunsubscribe@googlegrou­ps.com>

> > .
> > For more options, visit this group at
> >http://groups.google.com/group/k2-support?hl=en.
>
> --

> / M- Hide quoted text -
>
> - Show quoted text -

[Eric Marden]

On Jan 2, 2010, at 6:19 PM, roguewave wrote:

> Michael, thanks. I think I'm up to the task. In reference to this
> suggestion "Create a custom style, and add .post {margin-bottom: XXpx}
> where XX is the distance you want." Where in the style.css file is the
> best place to put the new style?

These are the best resources to answer those questions :)

http://code.google.com/p/kaytwo/wiki/K2CSSandCustomCSS

http://code.google.com/p/kaytwo/wiki/K2ChildThemes

- Eric Marden
__________________________________
http://xentek.net/code/wordpress/
tw: @xentek

[Eric Marden]

> K2 isn't necessarily the best place to start if you're just getting
> your feet wet. It's a comprehensive template that does a lot of
> rather advanced things and to understand it all takes quite a bit of
> time.

> This is unlikely to change anytime soon.
>
> We'll soon start work on optimizing our CSS and class/ID structures
> to clean up some of the cruft that has settled over the years, and
> we'll probably also spend time on writing more thorough
> documentation and reference texts.
>
> But at the end of the day K2 is a mixture between a theme and a
> framework, and as such it's aimed more at people like ourselves, who
> know their JS from their CSS, rather than as a starting point for
> new bloggers.

I've been a web developer for over 12 years, and it took me longer
than I'd care to admit to unravel all of K2's secrets, and eventually
join the development team. With that said, I second Michael's
statements above and will be helping to produce better documentation
as we move forward this year. There are many questions that come up
time and again on the list (search the archives) where I've provided
the same links to our documentation:

http://code.google.com/p/kaytwo/wiki/K2CSSandCustomCSS
http://code.google.com/p/kaytwo/wiki/K2ChildThemes

And sometimes a snippet of CSS to get people started.

You'll still need to be familiar with the tools of the trade when
working with a theme framework and wanting to do more than just some
simple edits, but in the long run there are 3 levels of K2 proficiency
as I see them, and would like to structure future docs around these
foundations:

Level 1 - K2 Options
There are many customization tools in the options page K2 places in wp-
admin that will allow you to make it yours.

Level 2 - K2 CSS
Here you can changes sizes, colors, fonts and the like, and with a bit
of ingenuity some of the structure and layout of the page. You'll need
to be familiar with CSS, especially the 'C'ascade.

Level 3 - K2 Child Themes
Here you'll need to know enough PHP to know how to modify HTML code
that has PHP embedded in it. We've done our best to make it possible
to override almost anything you want, in a very clean fashion, using a
Child Theme. That way you can customize 99% of the theme, but still
inherit all the K2 awesomeness baked in over the years.

Either way, if you have specific questions post them here and one of
us will try to give you an answer that will help you get productive
quickly, but don't expect to be handed a bunch of code you can just
copy and paste. :) We all have responsibilities out of K2 and devote
as much time as possible to both improving this theme, as well as
supporting it.

Thanks!