Talk:Main Page

From e107 Wiki
Jump to: navigation, search

Contents

Categories

Any category suggestions? Streaky 19:57, 1 April 2006 (CST)

'Security' added - for pages related to security tips, howtos, and pages with security concerns as part of their topic. Streaky 21:34, 1 April 2006 (CST)

Translation

Hello great e107 community! ^_^
I've started the translation for the front page, hope I'll be able to put even more pages in french.. And that other languages will follow.
We should discuss about a policy on the traductions, as I know some really good e107 related sites that have pretty good information for a database like this one.. What I mean is that, as a policy, first language should be the 'english', if someone (a french guy like me for exemple) want to add some stuff to this knowledge base, he should first put it in english, then add the traduction. That, to always have one (not ten) "template" for other languages to reproduce... I don't know, that's an idea.

Discussion about the translation of the wiki are moved here

I'm with you, just trying to figure out the best way of handling multiple languages in mediawiki, carry on as you are though, i'll change stuff over when i've figured out what I'm doing :) Streaky 05:53, 6 April 2006 (CDT)
Use of muliple language in Mediawiki is NOT yet simple, I've tried on other wiki and it's a big mess to put up. You may want to wait for a version multi-language friendly, now you'll need to add fr.wiki.e107.org , de.wiki.e107.org , etc. to make it work in the way it's at the moment (a big rush for not much)
Check this article [1] , it's the best explanation i've found yet.

CSS Classes

A big help (for me) would be a list of core classes, their uses and their relationships. Does this make sense? Most of my time atm is spent working out (and remembering) what css class is doing what to a theme and whether it's core or custom. Maybe analysing other peoples work is not the best approach to learning themeing. I'm working from the basic templates atm as I'm guessing that working from a nearly clean slate is the best approach. It's less confusing although I guess very basic; i.e. table structure etc.

No access to make relevant changes

As I'm not an admin, I need one to do it :

  • go to Mediawiki:Sidebar and change the help redirect to :Category:Help
    • There is presently 2 "link" to help pages, not really helpful for "I don't know where to seek" users.
  • Could the page :Category:Traduction be unlocked? (or at least changed to Translation)
    • I would like to put more information on how to create/upgrade language pack but isn't able to add link to any information page..

Thanks --Daddy Cool 18:31, 6 July 2006 (CDT)

transduction is different to translation. transduction refers to the method of including templates in a wikipage. with regards to help, on mine i just whacked a redirection on one of the help pages. depends what namespace you want your help files to be under. i think the Help: namespace makes most sense. Kevstar 22:38, 25 July 2006 (CDT)

Better look for the front page

I've just added a little table in the front page so people looking for help could rapidly find what they are looking for, I think we should work on those section linked to answer the most common question and be able to create a functional web to the different query the user are looking for.

We should also make a little something to that front page that is not 'good looking' (well, not anoff I think). I've started this Help:E107 Handbook some time ago and I was wondering to do something like that for the front page.

What are your thoughts about this? --Daddy Cool 13:06, 11 November 2006 (CST)


Like the general concept of the front page, but suggest a slightly different ordering to reflect the most likely order in which people will need bits.

Definitely start with 'I need help' section.

Then the 'Administration' and 'Howto' sections - not sure which order would be most appropriate.

Then a separate 'User Perspective' section.

Then come the bits which relate to modification of E107 - theming, then shortcodes, then development (for coders).

And somewhere we need a 'general' bit for things such as history, major changes between revisions, roadmaps and so on.

--Steved 10:38, 18 November 2006 (CST)

I'm with you on this ;)
What do you think of :
1-Help section 2-general for things such history, changes, etc.
3-Admin 4-Howto
5-Modding e107 (Theme) 6-Modding e107 (plugins) <- Where we could put developed info about every plugins
7-Modding e107 (Plugin writing) 8-Modding e107 (Shortcodes)
9-Development
ps. I don't see what's going to be into 'user perspective' ?


By 'user perspective' I mean 'how to use an E107 site which has already been set up'. So, for example:

  • BBCode explanation (which is partially there - one I wrote for my users)
  • How to post in the forums
  • How to upload files
  • How to register on a site

I realise some of this type of information will be very site-specific, but we can at least help with the widely-used parts.


I think your suggested order is fine. Section 2 doesn't really fit anywhere in particular, so how about we leave it where it is with an opening section saying 'you probably don't need to read all of this'?

The Admin section needs something about plugins, but I think it right that plugin installation, configuration and use should have its own section.

Big issue which we need to address is the ability to upload graphics - they would help a lot in some places.

--Steved 08:17, 24 November 2006 (CST)

Agreed ^_^
For images, we should ask Streaky to make this possible, but I don't know the space the server have... For now, you can display external images by putting directly a link without putting into bracket..--Daddy Cool 09:29, 24 November 2006 (CST)


Some of the classification seems to have gone a bit wrong. A lot of what I would regard as 'administrator' stuff seems to be indexed under 'user'. Needs another look. --Steved 13:02, 5 December 2006 (CST)


I've started a 'dummy' front page here: http://wiki.e107.org/index.php?title=Main_Page_alt so that we can experiment. I've tried to order things to reflect the likely requirements of a new user - who is presumably going to start with installation and basic setting up, and may never really get to the later sections. Some uncertainty as to the best order for the later sections, and I'm not sure where to put things like the change history and so on. Not finished yet - any comments? --Steved 08:11, 6 December 2006 (CST)

Handbook

OK, so I actually wrote some code quite a while ago to output pages of the wiki into a PDF and create a book like structure.. Now, I've not really had a chance to make many changes recently, but do we think the wiki has a large enough number of quality pages to start putting such a thing together *and* if so.. Can we start putting together a list of such articles somewhere? My suggestion would be maybe a category for book-included pages. Also on the same note.. We should probably have a list of pages that's quality maybe needs improving a little. --Streaky 12:24, 15 November 2006 (CST)

I personnally think that the wiki needs alot of work before getting it into a pdf. But the idea to make a template called maybe : {{Ready to print}} based on a 'if' {{Ready to print|ok}} ->puts an inbound category, else (if no ok) puts a little banner message with 'Needs to be better look before publishing, please help here..'
I don't know, I try to think of a simple template, that wouldn't be hard to had everywhere... (maybe in the handbook template.. but then, how to act on it??...).... Still, this is a question that must be answered only if there's a large number enough pages.... (worked too much today, sorry if i'm not-understandable !gasp )--Daddy Cool 15:46, 18 November 2006 (CST)

some of us don't know what you're talking about!!!

I get the gist, but I definitely agree that the Help section needs to be improved. I learned how to program using BASIC & FORTRAN - so I understand the logic. But I can't figure out how to ask a QUESTION on this site!

I would STRONGLY recommend a BEGINNERS page that really WAS FOR BEGINNERS! Currently, I have an e107 site my brother set up and am loving it! But I don't know how to make it the best it can be. WHAT needs to be done, yes... HOW TO - not a clue. and you guys ain't helping!

Add a dictionary of terminology; not everyone speaks computerese. The language and slang changes frequently, even if you do try to keep up.

thanks for listening, ladyvix607


What is this?

Websites for you to check out to help your site become great

delete? --cryptide 15:22, 29 July 2008 (CDT)

Hack is a bad choice of terminology

Since recently, the how to make a plugin is documented with the indication 'hack'. Plugin writers do not create hacks, they create plugins.

A hack is a change on one or more of the e107 distributed core files.

A plugin is an independent additional software package of (integrated) functionality to e107.

--Nlstart 02:36, 8 August 2008 (EDT)