Good Grief

[marvl]

You folks have a pretty decent concept for your CMS, and the design looks very clean.  That's the good news.  However, the documentation sucks to high heaven, and the admin/default site leave a ton to be desired...

(1) So I install the product and have this nice sample site to play with.  The home page has this wonderful footer with a gazillion links in it... except I don't want this garbage there: it belongs on a documentation page.  If I inspect the page's generated source code I can see the garbage.  But I cannot find anywhere in the admin area where it exists to be modified, or better yet, deleted.

(2) Where in God's name do you keep the CSS files for the site, and how do I edit them?  IF I could find them I could at least muck with them in Bluefish.  I'm not a big fan of using grep and/or find, and it seems to me these are a central component of the product that should be readily accessible.

(3) Did I mention the documentation sucks?  It was clearly "written" by a developer with a drinking problem and no sense of direction.

But, rants aside, this is the most promising CMS I've looked at so far.  WordPress is a hack, and many of the others deserve a merit award from Rube Goldberg.

Any pointers/help appreciated.  Thanks.

[Wishbone]

This post falls under rule #3 on "How not to ask for help"

http://forum.cmsmadesimple.org/index.ph ... 661.0.html

Code: Select all

Rule #3. Insults. "This code is so crappy. I don't know why anybody would even try using it." When I read this, I lose all interest in trying to help, and figure that you can take your problem and shove it.

Did you happen to read the default content of your CMS install, btw? It's a good read.

[spike]

Look under the Support tab - you'll find lots of docs in there my lad - keep you going for a week or two.
As for the Stylesheets - try looking under Stylesheets in the Admin. Some things you've just gotta do on yer own.
gruss - spike (A happy user)

[marvl]

This post falls under rule #3 on "How not to ask for help"

http://forum.cmsmadesimple.org/index.ph ... 661.0.html

Code: Select all

Rule #3. Insults. "This code is so crappy. I don't know why anybody would even try using it." When I read this, I lose all interest in trying to help, and figure that you can take your problem and shove it.

Did you happen to read the default content of your CMS install, btw? It's a good read.

And this post falls under the "Not Helpful" umbrella. Feel free to generously coat with Vaseline and  insert in any convenient orifice.  It's an insult to offer an accurate assessment of the product?  Aw shucks, don't cry  little boy.

[jmcgin51]

This post falls under rule #3 on "How not to ask for help"

http://forum.cmsmadesimple.org/index.ph ... 661.0.html

Code: Select all

Rule #3. Insults. "This code is so crappy. I don't know why anybody would even try using it." When I read this, I lose all interest in trying to help, and figure that you can take your problem and shove it.

Did you happen to read the default content of your CMS install, btw? It's a good read.

And this post falls under the "Not Helpful" umbrella. Feel free to generously coat with Vaseline and  insert in any convenient orifice.  It's an insult to offer an accurate assessment of the product?  Aw shucks, don't cry  little boy.

marvl - if you have something constructive to contribute, we're open to suggestions.  If you are here only to offer an "accurate assessment" (the merits of which are at the very least debatable, but not necessarily invalid altogether), and then sit back and bask in the heat of your flame, we're not interested, and you deserve at least wishbone's response.  A read through the default content would do you a world of good, if you're sincerely interested in learning this software.  It would answer your first two questions for sure, and would save you from becoming another "developer with a drinking problem", if it's not too late already.  If you're not interested in learning, then you're welcome to continue on your quest for a content management system that better suits your needs and your target learning curve.

Comments like "the documentation sucks" don't help anyone.  They just make you look like you don't have anything useful to add but you just want to whine and wait for someone else to do the heavy lifting.  If you don't like the documentation (and which documentation are you referring to - the default content, or the wiki, or the APIdoc, etc.??), feel free to pitch in or offer constructive suggestions for improving it.  After all, this is an open-source community-driven project.

I would strongly suggest that you take a step back and examine your attitude if you think this is a community in which you might be interested in participating.  I think I can safely say that your earlier post probably raised the blood pressure of anyone reading it - not because of the content, but because of the way you presented it.  And your latest response was simply uncalled for and one of the most immature things I've read anywhere on the web.  Similar future posts are not likely to be well-received.

[Wishbone]

Marvin,

If you need to insult us after two of us have given valid input to a relatively simple issue, I question your 20+ years of website development claim on your website.

http://marvl.net

Have a nice day!

[Dr.CSS]

Sounds like a great way to "Lose Friends and Alienate People", come on here and start criticizing a bunch of stuff you obviously haven't researched, like reading the default content...

1), 2) http://multiintech.com/defaultcontent/i ... tylesheets...

3) Not even going to go there...

[Jeff]

Since you are so quick to criticize, I hope to see you write a very lengthy and well documented set of introductory instructions that we can add to the our wiki.

Remember this project including documentation is based on users contributions.

[RonnyK]

First check the template of the page that you are referring to. These templates are in a way, meant as documentation, hence the recommendation to KEEP the default content somewhere available.

In the footer of that template are {menu} calls that drive the menu in the footer area.

Second, the CSS files are linked to that page-template, so when clicking the CSS icon on the right side of the template used, in Layout->Templates, you will see the linked stylesheets.

Ronny

[M@rtijn]

@RonnyK: You're just too kind. After such a bad first impression from marvl, you're still willing to help him out?

Just shows genuine good people still exist, but I would have spend my usefull comment on somebody who is willing to listen.