Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#31 2004-12-16 14:35:05

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,415
Website

Re: [wiki] User Manual

That’s what I was (am) using, but still no go. Same error.

EDIT: Maybe I’ve reached my quota ;)

Hey, it works again. Never mind, I guess.

EDIT: Well it seems to be a hit or miss situation. I’m trying to edit the first post of this thread, but can’t get into it (same error). I do seem to be able to edit this post though. Strange. Maybe because that other post is so far up the chain, and on another page? (naw)

Last edited by Destry (2004-12-16 14:44:36)

Offline

#32 2004-12-16 15:45:58

Remillard
Plugin Author
From: Lenexa, KS
Registered: 2004-05-16
Posts: 169

Re: [wiki] User Manual

This is happening with Textpattern Resources and a few other spots on Textdrive. It’s funny (strange funny, not ha-ha funny) that it’s only on one particular section “Tips”. Individual articles will load, sans CSS, but the entire section generates the 412 Precondition Error. With the individual articles, if the css source is viewed, it shows that there was a 412 Precondition Error on fetching the CSS code. All other sections view normally!

Offline

#33 2004-12-16 15:47:19

Remillard
Plugin Author
From: Lenexa, KS
Registered: 2004-05-16
Posts: 169

Re: [wiki] User Manual

Oh, as far as where the MediaWiki is stashed, there’s really not much that’s on the current one that can’t be duplicated. If it moves, now would be a very good time :). Textpattern.net seems like a good name though somehow ;-).

Offline

#34 2004-12-16 15:58:09

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,415
Website

Re: [wiki] User Manual

OK, this is a test. I’m trying to add about four paragraphs of text that address <em>TextBook</em> structure and presentation, but I can’t do it, I get that same damn error. But let’s see if this little bit of text goes through…

EDIT: Well, not only did it go through, but I can edit too. So it seems there might be a problem with large blocks of text (large posts)?

EDIT: Certainly the capability is there, as I’ve edited the header post several times before to keep it updated, and obviously it was quite a large post to begin with. Strange. That’s about all the clues I can give.

Last edited by Destry (2004-12-16 16:02:23)

Offline

#35 2004-12-16 16:01:47

Remillard
Plugin Author
From: Lenexa, KS
Registered: 2004-05-16
Posts: 169

Re: [wiki] User Manual

I have a sneaking suspicion it might be specific words, or word combinations.

Offline

#36 2004-12-16 16:16:04

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,415
Website

Re: [wiki] User Manual

That wouldn’t explain why I can’t edit a couple of typos in the header post. All that content is already there.

Can’t edit certain posts, can’t add certain new posts. I don’t know why, but it sucks.

Anyway, I hate talking about it here, would rather keep this thread focused on the subject of <em>TextBook</em>.

Last edited by Destry (2004-12-16 16:18:23)

Offline

#37 2004-12-16 16:28:07

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,415
Website

Re: [wiki] User Manual

Remillard: Yeah, I noticed yesterday the wiki was pretty slow to turn over after I made a small edit to notes or something. And yeah, I think the textpattern.net domain as Dean proffered would be more logical, semantically speaking.

Offline

#38 2004-12-16 16:31:07

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,415
Website

Re: [wiki] User Manual

Since I can’t seem to enter a larger-like post, I’ll try and add things in coherent sections, this one on <em>TextBook</em> structure, one on wiki thoughts, and one more on presentation.

<strong>Comments on <em>TextBook</em> Structure:</strong>
There’s been dialogue in this thread and in the current <em><a href=“http://textpattern.net/wiki/index.php?title=Main_Page”>TextBook</a></em> manual development wiki that the proposed structure of the manual needs filling out; putting more advanced topics near the end, and keeping the first several chapters focused as the new users area. Dandy, but I especially feel that the new users are the primary focus here, so those chapters should be fleshed-out first (see my user page in the wiki about my <a href=“http://textpattern.net/wiki/index.php?title=User:Destry”>motivation and contributions</a>); though where current resources already exist for advanced topics, we should certainly edit them in.

I recall that I had seen another thread somewhere in which another structure had been worked on with community feedback. It might be good to look at that one and use it to build on here. Problem is, I’m having a devil of a time finding it. It’s not critical, but it might be helpful…anyone no what I’m talking about? Can you make that thread known, please?

EDIT: (Well, so far so good on adding the section posts.)

Last edited by Destry (2004-12-20 17:59:43)

Offline

#39 2004-12-16 16:41:27

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,415
Website

Re: [wiki] User Manual

<strong>Comments on <em>TextBook</em> Development Wiki:</strong>

Suggestions are requested about how to first oganize the wiki so it’s not inhibiting anyone’s basic productivity. The fewer auxilary pages the better. Maybe all that needs to be there is the manual TOC right on the first page, a help directory (a single page of topics), the “user” pages, which I think might be good for contributors to talk about what they are willing/capable of contributing, and of course the content component pages as they are added/linked from the TOC. Strip out all the other MediaWiki crud (if possible) so it’s not distracting. These are just ideas; the point is to make it as user-friendly as possible, however much we can do so.

<strong>Comments on <em>TextBook</em> Presentation:</strong>
It would be cool to start getting input on a style guide that will result in a couple of sharp and tight CSS files for the manual, one for web display and one for print display. The style guide would be important to have done <strong>before</strong> the CSS files, obviously, so there’s a clear roadmap about how to write the CSS rules. As mentioned in the write-up (this thread’s head post), the only requirement would be a look and feel that represents Textpattern’s current branding. Otherwise, nothing but CSS fun. Maybe start by offering suggestions about layout, fonts, colors, etc. A <em>TextBook Style Guide</em> should probalby be started in the wiki to better see how it’s filling out and for reference.

One note on the presentation stuff though…Remillard has indicated that MediaWiki is a bit complex as far as the styling aspect goes, and the files themselves are pretty buried and locked-down, so the details are still unclear about whether or not the wiki is styled or some other platform. Maybe the answer is to simply use the wicki for getting the meat and potatos of the manual in place (content only), and then move the refined content components into a TxP install somewhere that is dedicated strictly to the <em>TextBook</em> manual (which I think was an idea of Alicson’s). Seems it would be much easier to organize and style a TxP install than a wiki. Dean has suggested <em>textpattern.net</em>, so maybe that would be the place for it too. Thoughts?

Last edited by Destry (2004-12-16 17:28:32)

Offline

#40 2004-12-16 23:31:06

alicson
Member
Registered: 2004-05-26
Posts: 465
Website

Re: [wiki] User Manual

i’m still for the idea of using mediawiki (whatever works best for collaboration) for development, and then putting the polished (could be further polished and updated forever afterward) version together on a Textpatterned site.

i do think there’s a very good way to have the existing and pending articles on the Resources site (having to do with plugins, mods, tips, and other more advanced Textpattern-things) be cooperative with the TextBook.. but i’m not sure quite how to nicely achieve that with separate databases (someone else may think of a way). that would be more for the intermediate and advanced topics anyway, so perhaps it’s not something to be thinking about at this point..

my biggest immediate thought? i’d like to hear the various, however brief, comments and thoughts of other Textpatterners; those who might be perusing this thread and may or may not be interested in the subject… whether or not they’re interested, i’d like to hear why/what their observations are thus far.

is the next step to figure a style guide then? well… offhandedly, i’d suggest focusing on building the actual content and fleshing out the existing outline and seeing how things really start shaping with that.. the style may be better figured when the material is more developed.

what were you guys thinking as next steps? — but let’s not focus too much on the methods and processions of development, such that we aren’t concentrating on building the actual project at hand. *edit: not by any means was this meant as chiding; was mostly thinking to myself about projects in general and how many of them go. this one, particularly after a quick glance at the wiki just now, is quite definitely moving. :)

see you guys in the wiki soon

Last edited by alicson (2004-12-16 23:35:11)


textpattern.org :: find and share Textpattern resources
docs.textpattern.io :: Textpattern user documentation

Offline

Board footer

Powered by FluxBB