Search options (Page 6 of 8)

Well it depends how large the changes are to PunBB's template. If it could be done with CSS and minimal HTML, then you could just add the changes to whichever CSS style you want and leave the HTML template alone. You could even change the HTML template, then hide parts of the HTML using CSS with display:none and have parts of the page appear only while using certain styles ... CSS is wonderful.

If the CSS is broken up into multiple files based on what people would commonly want to edit vs. what they'd goof up on, then it would be fine. For example, we could have the colours separate from the positioning/framework. We could also create multiple versions with background colours and heading graphics, for people who want a phpBB style with gradient background images specified in another CSS file and a tutorial to modify the gradients and CSS to fit anyone's website.

I feel like doing a ... typo correction

"Any beta?" (I don't expect a yes; I just felt like asking.)

Looks fine in Firebird/Mozilla ... but I don't have time to test/debug in IE right now, sorry. Try adding style="padding: 0; margin: 0;
overflow:auto;" to the iframe tag ...

I would re-do the graphics on page 4, all the arrows clutter the page and make it harder to understand.

As a general comment for the overall guide, it's very technical, dissecting the exact PunBB layout with no CSS examples. Many people just come to PunBB with a colour scheme and want to know how to change the colours and design of the board to fit their existing site.

Instead of describing the PunBB page and what CSS rules will control parts of the page design, why not show a sample CSS file and give a tutorial on altering the CSS file or creating a new one from scratch, based on an existing website design/colour scheme? That would make it easier for people to understand the CSS and make the guide smaller and more useful. (This existing guide could perhaps be a Technical Appendix to the tutorial for those interested in further customizations)

I've mixed feelings about a PunBB portal derivative. While it might help someone launch a site quicker, would you really want a full CMS? Outside of perhaps an FAQ page, a weblog/news page and perhaps polls, what would you really need from PHPNuke?

Perhaps a modified weblog/news page based on a PunBB forum might be useful, but there are so many others out there that already support trackbacks/linkbacks that it would make a PunBB one useless.

Why not just link together an existing FAQ page and PHP polling script with b2 or Movable Type (for news/blogs) and integrate the design with PunBB ... If you needed a full CMS with article posting and comments, then just use one. But then it depends on the topic and goals of your website and the purpose of your forums/CMS.

Once we've CSS, that will be no problem ? and entirely up to the end-user/implementer ;)

Congratulations

Indeed, as Tantek Çelik recently posted.

I was using definition lists. But I changed my mind because although they could be more semantically correct, they don't look as good in Lynx and some older browsers. It's easy enough to be semantically correct for some of the HTML, but sometimes the more practical "what looks better" will win. As an example: Should I use a nested list to explain the nested relationship of the breadcrumbs, or just leave them as text in a paragraph tag under the header?

Also, it's amazing how the web design community keeps sharing different techniques. While doing this website, I stumbled upon this very problem and found nearly the same solution on my own, but with the other extensions in that post's comments, I may try tweaking the technique further ... and test it on a Mac ...

It's occurred to me that if we added complete XHTML/CSS support to 1.2, myself and ps21 will have to make some major changes to the style guide =p Then again, it would probably be easier to just start again from scratch. I've SnagIt 7 for the screenshots ;)

I know that. Kennel said it might be a good alternative. All I was suggesting was that perhaps we could shove a few tables into my barebones layout and remove the layout CSS, then call that a compromise for the 1.1 code, with an option to remove the tables for those who want a pure CSS layout. (It's just another suggestion, of course. I see nothing wrong with pure CSS myself, just for those who still want a few tables, we could offer both.)

The name is a gaming alias. I made the CSpotkill.com forums for a few (47+) friends I met while playing a game called Counter-Strike. From there, I started modding PunBB and so registered as "CSpotkill" on these forums. My real name's Louis (pronounced like in french, lu-ee).

That reminds me of one more mod that must be written for PunBB ? the addition of email protection javascript, or perhaps just replace symbols with textual equivalents, like the ASP.NET forum does (I think it was the forum; maybe it was the blogging software).

As for other mods I'm working on, I'm developing  an error reporting feature for them. It will let me give better support for any issues that may crop up and to fix bugs faster.

It just occurred to me that while we're doing major redesigns of the PunBB interface and re-writing huge chunks of PunBB, it might be good to look at the debugging "features", such as sprinkling in plenty of assertions and possibly adding error reporting with a database of support articles ... What do you use for testing PunBB, Kennel? [If you're curious, I've been reading a huge 600 page book on debugging, so it's on my brain]

CSS could solve this. Every post is a separate item, so if one post extends past the standard width of the page, the rest will stay inside the page. You just haven't seen it in my PunCSS page since I've only posted the same post, 6 times ;)

It sounds nearly exactly like what I did, except with a barebones table still inside the HTML. Maybe if you come up with something similar to my PunCSS, we could code PunBB to have this way as default, with a table-less design as another option in the admin interface, for those who want complete control over the design with CSS or those who want true standards compliance?