Format CSI
Steven Heynderickx wrote on 10 Nov 2009 14:49
Can we describe a format for the correct refferal to CSI's
I will do it here, but I need some input.
So up till now I think it is like this
If I would like to use the "CSS elegant code brackets"
I need to insert the following syntax in to my page:
[[include :csi:include:css-brackets]]
For now there is only ONE site wich has the CSI's: csi.wikidot.com
Naming the possible classes that are in the include:
??? suggestions
Comments: 7
page revision: 3, last edited: 12 Nov 2009 12:31
1) The page http://csi.wikidot.com/package:7 ("CSS elegant code brackets") has no connection to the page of the include it self beeing http://csi.wikidot.com/include:css-brackets
How about
and both pages have "(_)css-brackets" as a tag.
2) Every include should be placed in a [[div class="includename"]], so that if CSS or javascript or other stuff is needed it can be adressed with this unique name.
3) the site http://modules.wikidot.com/ needs to disappear
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
We have two types of CSIs today:
We can't try the second case because the software does not support it yet. It will, soon.
The package and include:css-brackets are properly linked together, there is no need for an info section. The package can include many CSS fragments. I asked this already here: one, or many CSS fragment per package?
Alternatively, we could put CSS CSIs onto css.wikidot.com in an include category. That might be cleanest.
Finally (there are many options and it's not clear which is best yet), the design sketch for CSIs proposes that we can extract code blocks from a page, meaning we can combine a CSS fragment with description on one page.
My ideal design for CSS fragments is:
But ideal designs that depend on non-existing functionality tend to lead to frustration…
Conclusion: do nothing more with this until we get more software support in Wikidot, then use gradually (not too widely) until we know what the best model is.
Portfolio
I am trying be formulate something general I was not focussing on CSS … never mind I'll search in your design things and keep quiet for a while… but you understand this gets me excited in a wikidot-kind of way (nothing more ;-$)
BTW I would not put CSS-related CSI's in CSS.wikidot.com
ONE place for all CSI is IMO the best… you could of course make a CSS section in the CSI.wikidot.com site and CSS.wikidot.com kan link to this.
I did not say that it was not linked right. But lets say you look at the code of some page and you see [[include :csi:include:css-brackets]] than I would find it simple and logical that with this information I could find the info about that include beeing: csi.wikidot.com:includeinfo:css-brackets .
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
How about this syntax:
[[include :csi:css:code-brackets]]
[[include :csi:module:clock]]
[[include :csi:content:legal]]
… not bad.
I think for CSS code, single pages with description + codeblock CSI is the nicest and we should wait for this.
Distinction between content and modules… that's a nice split.
I'm hoping Michal will give us a 'rename' function that patches up CSI backlinks.
Portfolio
Okay?
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Yes. I've invited you to the blog site, go ahead and replace all design content with a redirect to here. I'll change the template to hide comments.
Portfolio