Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: [wiki] textbook css
Such a move to docs.textpattern.com requires only changed DNS record (unless I’m overlooking something). The wiki itself would not have to be moved to a different server.
Offline
Re: [wiki] textbook css
@wet: Keeping things on topic is what I’ve been trying to do since day one.
@maniqui: If I may… TxB = MW + (architectured + skind) + (content0 / contentcn), where…
c = community
n = “Please note that all contributions to Textbook are considered to be released under the GNU Free Documentation License 1.2 …If you don’t want your writing to be edited mercilessly and redistributed at will, then don’t submit it here.”
@zero: Converting the syntax is a good first step, but I don’t understand the emailing you for a link part. If you don’t mind me saying, why not directly reseed the TextBook pages with the corresponding edited content at your end? That would be the path of least confusion and in true spirit of collaboration. If you don’t want to go that far, then let me ask this: Did you rewrite every textbook page? If not, can you give a list of what pages were changed so that other helpers at least know where to focus? That would be helpful.
Last edited by Destry (2008-09-28 00:03:40)
Offline
Re: [wiki] textbook css
@rudd: I don’t believe I have any access to creating sub-domains on .com just .net, so someone with super DNS powers would have to change that. I could be wrong the new box is quite different from Robson, and not being a regular textdrive user means I don’t have an overall sense of what is available to me.
I’m assuming .com is also on txp.textdrive.
Shoving is the answer – pusher robot
Offline
Re: [wiki] textbook css
Yes.
Offline
Re: [wiki] textbook css
New skin is implemented at TxB proper.
I have not yet catered conditional comments to IE6, but I’ll get around to it. Hopefully nobody is losing sleep over that.
There’s some back-end organization stuff I’d rather tend to first, as well as get the overall structure of content in place so others can more easily run with things, including a couple help articles geared to translation of pages using templates and categories.
Also, I don’t think it will be necessary to use the two-character country code on translated page titles anymore. That was kind of set up originally without full understand of what is actually possible. It will be nicer, and cleaner to simply add the translation tag to bottom of pages as normal to create the mirror, but then translators can simply use a clean translated title without the two-character prefix. This requires an edit in the database, which is not yet done. I’ll confirm later but it’s not a high pri at the moment (need to make a list, I think).
Also, I’m going to rely on Patrick to do any domain aliasing that is wanted for URLs. Right now there’s a hodge-podge of versions used and it would be nice to settle on one in the hard coded menus and stuff. Are we still aiming for “docs.textpattern.com” ? I won’t edit anything until it’s working that way.
Make use of the flags …that helps wiki readers.
Offline
Re: [wiki] textbook css
On this page, I see “Category:Tags”. Is there any way to make that show “Tag reference” instead, because my brain has trouble not processing that as “category tags” which is something entirely different ;)
Offline
Re: [wiki] textbook css
That’s more an architecture issue as opposed to CSS. At any rate, you can change a link label to the category page (like in the left navigation), but you can’t change the category title itself or you lose the inherent function it provides. Two of which are, 1) auto-alphabetizing tag pages and 2) working with the PDF Book extension (not yet installed) which allows printing all pages in a given category as a single PDF document. I would think the latter alone is more than sufficient argument for having the category.
We can change the category name to “category:Textpattern Tags” (seems to say the obvious though in a wiki about Txp) and put a sentence under the category title: “This category constitutes the Tags Reference. All tags are described on pages alphebetized below.”
Readers should see the apples from the oranges easy enough, and when they see they can print the whole works in one shot, they might even celebrate.
Last edited by Destry (2008-10-06 22:01:28)
Offline
Re: [wiki] textbook css
People are complaining on alphabetical tag list missing.
I would give some priority to that issue.
I was looking for the alphabetical tag list on zero’s dokuwiki textbook forprovisory linking to it on the above thread, but it seems it is offline.
Also, I don’t want to sound like I’m complaining, but so, is the new skin an “official”/“community” decision?
It’s ok for me and it’s good to see thing just happening/moving forward.
Also, I like it, although I have some observations to do.
Offline
Re: [wiki] textbook css
There seems to be something that is forcing all the urls to lower case which I think is making all the old links not work. I can’t track down what it is though. All the old content is still there though. Destry, did you run cleanupCaps.php ?
Shoving is the answer – pusher robot
Offline
Re: [wiki] textbook css
Please take Tags Reference discussion here.
Last edited by Destry (2008-10-07 09:17:33)
Offline
Re: [wiki] textbook css
maniqui wrote:
I don’t want to sound like I’m complaining, but so, is the new skin an “official”/“community” decision?
maniqui, you and I both know there is no such thing as “community decision.” That’s just a horse by committee. :)
It’s ok for me and it’s good to see thing just happening/moving forward. Also, I like it, although I have some observations to do.
The design received favorable reviews when it was first introduced (and we might chalk your favorable comment as another plus mark). There’s been ample time for feedback and collaboration since then, and none was given. Look forward to your comments nonetheless.
The new skin was primarily intended to bring the wiki into better conformance with the .com style guide and to provide a layout that makes it better to improve a sense of wiki content organization.
The masthead is not final. It will be changed to adopt the masthead from the new .com design when that’s done and realized. That can be made to integrate easy enough.
As you said, we are actively moving things forward, which offers incremental benefit to users now rather than waiting until the end of time for the impossible perfect wiki.
Offline
Re: [wiki] textbook css
ruud wrote:
On this page, I see “Category:Tags”. Is there any way to make that show “Tag reference” instead, because my brain has trouble not processing that as “category tags” which is something entirely different ;)
Sorry, ruud. It was late and my brain was upside down. We can change the category name to category:Tags Reference, is that what you mean? That seems to be an effective compromise that retains category functionality and improves clarity.
Offline