Users who can't read small print will normally use the browser built in methods for zooming and style sheet control. A couple years ago it was popular to use something like styleswitcher from A list apart. In my opinion it is just extra work that isn't supported across alot of browsers.

You could turn on theme switching in XOOPS and have a few variations of your theme to choose fom in the same manner.

I think there are even some Ajax methods floating around.

I recommend that you just allow users with visual impairments to use their own browser controls. Most methods you deploy will conflict with the browser settings anyway.

Start Here

jobsjoseph: That link will give you everything you need to get started. Once you download xoops, you also find instructions there. Don't be intimidated. It looks complicated, but the developers really made it easy. You literally upload the files and send your browser to your website. It is that easy.

The hardest part is creating a database and user using your webhost's conrol panel.

Good luck.

Yes, you can create an accessible site in Xoops. It is not easy. Most CMS systems you come across are not going to be easy to validate according to accessibilty standards.

The problem is our history, I mean among all CMS. When these systems were created, it was standard practice to use tables and such for layout. Even browsers can't agree on the standards, yet. So, don't expect the moon no matter which CMS or system you choose.

I have used probably every CMS around for one thing or another. I can tell you that XOOPS is going to be the best CMS to learn if you are attempting one for the very first time. This goes for installation, maintenance, and design.

A CMS uses modules or extensions, they all have their own treminology, for adding the various functions. Many of these are also not coded to generate standards compliant output.

When you design your main theme, you can make sure your "wrapper" is compliant, but cleaning up the content from modules and core functions can be a pretty big chore. It can be done, but it usually means writing a template for every module in most CMS systems.

Good luck.

I think most web designers find themselves in the same situation you are in now. How do you let users update their own websites? There are a few options:

1. A CMS like XOOPS!

A CMS is primarily used as a community portal designed to let visitors interact with each other and to let a number of writers publish content. Many CMSs can be configured via plug-ins to perform a variety of functions from a personal website to a full e-commerce site. The downside of a CMS is that it might be too much to manage for the website owner.

2. A BLOG like Wordpress

A blog is a great way for individuals or small organizations who just need a simple way to publish news and content. Most BLOGS have a very user friendly interface for regular updates.

3. Web editors like Contibute

Contribute is nice for static content only. Use this when publishers do not have the web server resources to install a database required for a CMS or Blog.

A great place to start reading is actually the Wikipedia. Search for CMS, blogs, and websites. That should be your first stop in my opinion.

Edit: Never rely on posts in message boards when trying to choose a CMS. Most users of any CMS are fiercely loyal and will defend it to the grave. Every CMS has its advantages and disadvantages. As a designer, your best bet is to take a look at the template system and an example template. If it looks like something you can design around, then give it a shot. Once you learn one CMS system, you will be able to then compare it to others and make better judgements.

I just read your question again. I think I misunderstood it and gave you a long answer. In admin under general preferences you have an option to choose which module loads at startup. I think it defaults to NEWS. Just pick NONE from that dropdown list. If you want to add some content to the new blank homepage, you can do so by creating a custom block that only displays on the homepage. Make sure you set group permissions so anonymous users see your new custom blocks. That's what I did for my start page.

Sorry, I gave a long answer that first time. I misunderstood.

I have seen this question come up alot in all the CMS systems I have used. People get too reliant on modules and information stored in a database. If you have static content such as an About Us page that you want to display, you don't need HTML wrappers or a special module. If it was a normal website you would just create a new page with the same menu items as your index.html page. You can do the same thing here. Just make a copy of the index.html file in your theme folder. If you are using a documented theme, you should see a comment line that says "Display center blocks" or something similar. Just replace this entire section with normal html static content. Name your new index.html file to aboutus.html or whatever applies to your page and add a link to this page in your main menu. This is much easier than other methods if you just need a page or two of extra content.

edit- I realized the menu portion probably is not a beginner thing to do. You are not stuck with the automatically generated module menu. You can create a custom block in the admin menu and design your own menu. You just add the same links that you want to your custom block plus any extra links you want such as our about us example. When your custom menu is working just turn off the display option for XOOPS main menu block in the blocks admin.

Skyrider,

The admin section can be accessed directly. In your case use http://www.odps.net/xoops/html/admin.php then change your general preferences back to the default theme. I'm new myself, I ran into that snag earlier. Also, I noticed your path is a bit long. Normally, you would install the contents of the html folder in your web directory, not the whole folder. That will shorten your URL. You also don't need a XOOPS folder. You can install the contents of of the HTML release folder directly into your web folder at your ISP. It makes for easier troubleshooting when those URL's are shorter.

Thanks, Bender. I hate Opera. It never breaks gracefully. I don't know what the problem was. The news module is a bit buggy in that spot. It uses single quotes when you view source and throws crazy style stuff in with news item image. I worked around it I think.

Thanks for the comments, guys. I'm not sure about making any more themes, Michael... this one is enough to keep me busy. I just wanted an original theme for my own website, and it was just something I had to try. Just to see if I could do it.

I enjoy making the graphics... I just hate the code.

Okay, revision number one. I think I pretty much decided to stick with that grey background you suggested. What do think of the content now, did I overdo the gold or the borders?

Be brutal... let me know what doesn't look right.

McPherons.com

Thanks...

Well, thanks for the kind words. I have to say kudos to the core developers. All I did was change some html and css. Everything was so well documented it was easier than designing a normal website. So, far I have been able to find a reference in these forums for everything I wanted to do. Seems like a great support community in XOOPS so far. I'm glad I installed it.

The only real difficulty so far is figuring out what all is possible. There is no real reference for the XOOPS and SMARTY stuff. It would be nice to have a list all the tags and variables that are possible. Like some of the HTML and CSS sites out there.

Anyway, changing that background to gray made me feel a whole lot better about the look. That is really what I needed. It saved me some work experimenting with those crazy module templates. I still say there has to be a more simpler or at least a more organized method.

Thanks again for the comments.