[documentation] Prep for 4.7 announcement help
Charlie Lowe
cel4145 at cyberdash.com
Sat Apr 1 16:04:39 UTC 2006
Could this be a good opportunity to create a 4.7 FAQ page as the first
place that people should go to when considering installing or upgrading
to 4.7? The new changes listed below could be one, "What are the major
differences between 4.6 & 4.7?" question, with each item linking to a
fuller explanation. Here's a tentative list
- Where do I download 4.7?
- Where do I download additional modules for 4.7?
- Where do I download additional themes for 4.7?
- What are the 4.7 system requirements?
- How do I install a new 4.7 site?
- How do I setup a multisite configuration in 4.7?
- How do I create or modify a 4.7 theme?
- How do I upgrade a 4.6 site to 4.7?
- What are the major differences between 4.6 & 4.7?
- What are the most common installation and upgrade issues with 4.7?
- Where can I post my support questions for 4.7?
- Where do I post bug reports?
- How can I keep up with security updates for 4.7?
Each FAQ question should have an anchor. Then at the first sign in the
forums of problems with one of the items listed below, we can link
directly to that question. This might help to limit the number of
support questions from the same person regarding all the new changes and
features. Also, having short lists in a FAQ with links to fuller
explanations is more scannable (and thus more likely to be read) than a
larger individual "What you need to know about 4.7? page.
Steven Peck wrote:
> Ok folks….. 4.7 is getting ready to come out and RC1 is going to have a
> whole new class of folks adopting it who have been waiting. Now it's
> been a while and a lot has changed. A lot more then any release I have
> remembered and some of the changes are seriously impacting depending on
> your perspective. So what does this mean for us? We need notes, one
> liners, gotcha's and some history stuff on the why's so we can avoid the
> 'why didn't you tell me' scenerios or repeating the same answer over and
> over and just provide a link.
>
> Off the top of my head I've come up with a few areas we need stuff on.
> Some there is existing starting points, others there are just knowledge
> in passing. We really really really need this. Please add more area's
> that I don’t have here and if anyone wants to write up something feel
> free. It doesn't even have to be polished just a starting point.. The
> issue chx raised about session ID's yesterday needs to be addressed
> too. Without these write ups, there will be angry mobs with pitchforks
> and torches coming to the castle.
>
> Thanks fo ryour help.
>
> base_url change is one that comes to mind. (morbus's write up should
> serve as a base for that)
> filter change to areas like the mission statement (need
> docs/alternative/examples to html in mission)
> blocks (tout improvements)
> revisions (tout improvements)
> free tagging (what and how it works)
> user greeting messages (effect of upgrade on custom messages)
>
>
>
> ------------------------------------------------------------------------
>
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/
More information about the documentation
mailing list