Guide Pages

Guide Pages

Timothy Foster 17 Jun 2010 23:55

I'm trying to compile a list of all possible topics that can be covered in the Guide section of the site. I want to categorize them into the three categories you see on this page later, but it would be better if we knew what categories we wanted first.

I've got the following so far:

• Primer (just an intro with syntax)
• Selectors (Type, Class, and ID)
• Selectors (Descendant, Child, Universal, Adjacent Sibling)
• Attribute Selectors
• Pseudo-classes/elements
• Declarations
• Making a Theme in Wikidot
• Font
• Background
• Lists and Tables
• Element Blocks
• Positioning
• Wikidot's page structure
• Theme Engineering
• Header
• Side bar
• Top bar
• Wikidot Tags
• Forum
• Content Blocks
• Multiple Wikidot Themes
• Media Types
• Browser Compatibility
• @import
• Colors

Are there any others, or are some of these redundant?

---

Timothy Foster - @tfAuroratide
Auroratide.com - Go here if you're nerdy like me

Re: Guide Pages

Ed Johnson 18 Jun 2010 00:43

The only thing that jumps out at me would be a "Creating a New Wikidot Site". I think the "default" method for creating a site from the "Get a new wiki" link in our account manager is really dated now.

I step-by-step guide that explains the different methods for starting a new site and then linking to the other topics you've outlined would be a nice addition to this site.

-Ed

---

Community Admin

Re: Guide Pages

Timothy Foster 18 Jun 2010 14:42

This is a good idea. I'll probably also put this in the top bar as a main idea.

Also, I'm wondering if it is worth making a sandbox or not for people to test out CSS stuff. What do you think?

---

Timothy Foster - @tfAuroratide
Auroratide.com - Go here if you're nerdy like me

Re: Guide Pages

Ed Johnson 18 Jun 2010 15:07

A sandbox is a good idea. Have you seen the "Try It" editor at w3schools? It would be cool if we could have something that functions like that. The css module might be a way to implement it.

And to clarify, I think the "Create a new site" guide should focus on the CSS and have limited instruction on other Wikidot features since the main focus here is on CSS.

I'm sorry I haven't been able to spend more time here helping out. Once I get a couple of big projects behind me at work, I should be able to start contributing more.

-Ed

---

Community Admin

Re: Guide Pages

Timothy Foster 18 Jun 2010 16:59

I have seen the Try It, and it is fantastic. Unfortunately, I have no idea how to implement it here since it uses form data and ASP which I don't know how to operate. The easiest way would be to create another site called css-sandbox or something and use Data Forms to allow the editing of CSS for particular pages.

Yes, that makes sense. As I don't know all of the ways a Wikidot site can be made, I would probably leave that page up to someone else.

It is fine (: In fact, I'll be gone the next two weeks, so you won't see much contributing from me until July after tomorrow.

---

Timothy Foster - @tfAuroratide
Auroratide.com - Go here if you're nerdy like me

Re: Guide Pages

leiger 19 Dec 2010 23:46

A clone module works cross-site too, so that means you can put the clone module directly on css.wikidot.com for the default-template. That way, you can say "click this button to get another new site!".

Can't get any easier than that! ;-)

I always use the blank-template, but it's not exactly the best choice for new Wikidot users.

---

~ Shane (Wikidot Community Admin - Volunteer)
Wikidot: My Blog, Wikidot Editor, Official Docs
Work: ZoomPlanner (built for freelancers/small business)
Other: YouTube (gaming channel)

Re: Guide Pages

David Lilienfeld 25 Jun 2010 02:09

Perhaps I'm missing something here, but wouldn't a link to the existing "Try It" editor take care of what you're trying to do?

Re: Guide Pages

Ed Johnson 25 Jun 2010 03:57

Perhaps, but that particular editor gets pre-populated with whatever topic you're viewing on the W3Schools site.

Since we're trying to make this Wikidot-specific, it would be slick if we could have our own version that is specific to the Wikidot page elements. For example, taking the user to a page that has a #side-bar or #top-bar and displaying CSS to play with that is relevant to those elements.

-Ed

---

Community Admin

Re: Guide Pages

Timothy Foster 30 Nov 2010 21:13

158 days later, I find myself perplexed by this problem and took another go at it. Since Form Data adds weird symbols, it is impossible to use it for defining CSS, so sticking to the old way, I came up with something on the Selectors page. It's far from perfect, but it is a start.

It allows for the user to play around with CSS with relevant fore-content in it. However, it can lead to a ton of pages being created on another site (probably not a problem, seeing that Wikidot's own sandbox gets at least 1 spam page every hour), and the largest problem is that leaving the page without messing with it pops a confirmation message by Wikidot, asking if the person really wants to leave the page (since a page is technically being edited).

I'll also have to add functionality so that it can be more Wikidot-oriented rather than just being a CSS general tester.

---

Timothy Foster - @tfAuroratide
Auroratide.com - Go here if you're nerdy like me