What would you like to see more Documentation on?

Quote from: kongondo at Jul 15, 2009, 05:38 PM

Quote from: BobRay at Jul 15, 2009, 05:28 PM

GetResources could use some examples.

Wanted to suggest the same but then thought Shaun was referring to Revo per se and not 3rd party elements/components? (ye, I know, opengeek’s the author of getResources, but it’s still 3rd party - not part of Revo, right?).

Correct, it is a 3rd party component (3PC). I’ll be providing more examples (including RSS feeds, Ajax request handlers, etc.) in the next release of getResources, along with some additional features. I’m also working on some supporting components, like getPage (for paging).

How to Upgrade an existing site.
What are the main issues you might experience while upgrading.

Quote from: splittingred at Jul 15, 2009, 01:04 PM

http://api.modxcms.com/ - Like such? This is a bit out of date, but we’ll have it updated for the beta-2 release.

The look & feel is really discouraging.
Is it impossible to integrate the Documentation in the MODx site design?

We’ll be looking into that. Creating phpDocumentor themes is not that easy, apparently.

The new doc is awesome. I was telling me how good the extjs docs is presented and you choose a similar way.

nice move!

It’s the ExtJS theme for phpDocumentor in fact!

If your still taking requests...

1. Creating Template Packages / adding to revo package manager
2. User management
3. Multi/Shared install scenarios (Common core (How would this work with cpanel?), multi domains, common shared resources..)

Actually if I could just get documentation on the first item I would be trilled as I want to get some of my templates going on Revo and manual install is getting annoying... (guess im hooked on package manger!)

Quote from: AMDbuilder at Jul 21, 2009, 01:29 PM

1. Creating Template Packages / adding to revo package manager

Right now, there’s a tutorial on building a build script:

http://svn.modxcms.com/docs/display/revolution/Creating+a+3rd+Party+Component+Build+Script

It’s going to be harder to simplify the process because of a few things - your Templates probably aren’t *just* Templates; they may have TVs, or use other Snippets. Are those going to be packaged in with it?

The build script tutorial goes pretty in depth to packaging. What specifically are you needing more help on?

2. User management

This is a known need as stated in the thread first post. We will definitely be working on Security subjects as we move forward in the documentation.

3. Multi/Shared install scenarios (Common core (How would this work with cpanel?), multi domains, common shared resources..)

For multi-site via domains and such:
http://svn.modxcms.com/docs/display/revolution/Contexts

I think stating certain, specific scenarios that you’d like more documentation on with this topic would help focus the documentation efforts. It’s hard to generalize in this subject.

Quote from: mjm at Jul 15, 2009, 09:59 PM

How to Upgrade an existing site.
What are the main issues you might experience while upgrading.

We’ll be ironing out these issues before RC1; as well as providing a tool for upgrading old 0.9.6.* sites. In the meantime, you can read the Upgrading page:

http://svn.modxcms.com/docs/display/revolution/Upgrading

BobRay also has a page (albeit a bit out of date, still referencing 0.9.7) on migrating, as well:
http://bobsguides.com/migrating-revolution.html

Quote from: splittingred at Jul 21, 2009, 01:50 PM

Quote from: AMDbuilder at Jul 21, 2009, 01:29 PM

1. Creating Template Packages / adding to revo package manager

Right now, there’s a tutorial on building a build script:

http://svn.modxcms.com/docs/display/revolution/Creating+a+3rd+Party+Component+Build+Script

It’s going to be harder to simplify the process because of a few things - your Templates probably aren’t *just* Templates; they may have TVs, or use other Snippets. Are those going to be packaged in with it?

The build script tutorial goes pretty in depth to packaging. What specifically are you needing more help on?

2. User management

This is a known need as stated in the thread first post. We will definitely be working on Security subjects as we move forward in the documentation.

3. Multi/Shared install scenarios (Common core (How would this work with cpanel?), multi domains, common shared resources..)

For multi-site via domains and such:
http://svn.modxcms.com/docs/display/revolution/Contexts

I think stating certain, specific scenarios that you’d like more documentation on with this topic would help focus the documentation efforts. It’s hard to generalize in this subject.

I’ve looked over that guide a few times and well it just seams overly complicated to add a template and a few chunks (template = html, css, images, and some JS in rare cases). I was hoping for a simpler guide or just an example template where I could see what needs to be changed.. (granted if it’s more than changing a file or two...)

As for some examples I already noted one, but to expand that some...

How would I setup a shared core on a cpanel server? Also how would it need to be setup so I could share common components between sites. ex: wayfinder
The goal is to add resources on each client cpanel account and use a DB under their account, but access a shared core and components...