Hi,
STW is not official source of docs, but it's the best we have, and there
were some people (some of which you'd call power users - guys who follow
me on twitter, read my blog, who shold generally be up to date with
stuff) asaaking me about stuff (why it's not working, why it's different
in docs than in reality) because they ended up going to the old docs site.
So I got rid of the link from the main site, to direct people to STW.
The API site should be dropped immediately IMO. It hasn't been updated
since RC3 at least and is largely out of date.
Using - I'm not sure how much valuable information is there that hasn't
been migrated to STW yet, but I suspect getthing the migtration done is
less than a day worth of work.
Probably similar thing with the old doco, which (at least for Windsor)
has been mostly migrated.
I've been apelling for help with this several times, yet if you take a
look at the logs, hardly anyone ever does anything towards the migration :/
Krzysztof
On 1/09/2010 4:37 AM, Henry Conceição wrote:
Got it.
Well, I think that the subdomain is smaller issue here. Each section
structures the docs in its on way and layout is very "basic", wich
imho turns stw in usability disaster. I did a quick lookup on the
analytics report, and people don't go further than home or the search
page.
Also, the links were changed only on the home page. If the user has a
bookmark or access the docs from the project page he'll still see the
old docs.
And that takes us to a bigger problem, imho. Now we have at least five
different sources of documentation:
- main web site
- stw
- using
- api
- forum
And if we look at the main site, stw and using we'll see that each
instance has unique, duplicated and stale articles.
My suggestion the tackle this is:
- return stw to staging
- move all the content on using to stw and deactivate it
- finished the migration of the docs from main web to stw
- do some clean-up, and define/apply some standards to the sections
- conect main web site and stw, turning it in the official documentation source
- fix the layout
For the layout stuff, I'm inclined to hire some designers (courtesy of
Castle Stronghold) to listen the team ideas and come up with
something.
Cheers,
Henry Conceição
On Tue, Aug 31, 2010 at 2:29 PM, Jonathon Rossi<[email protected]> wrote:
Not that I am aware of. I think Krzysztof has chosen to do it because
that documentation is much more up to date than the main site.
Since that is the case we should really plan how we are going to get off the
stw subdomain otherwise we'll turn things into a mess with things on the
main site, stw and using.
2010/9/1 Henry Conceição<[email protected]>
Did I missed the discussion about promoting stw wiki as the main
source of documentation?
Cheers,
Henry Conceição
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to
[email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
Jono
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups "Castle
Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
