Difference between revisions of "Geeklog.net Redesign"
m (re-save to fix character issue.)
|Line 19:||Line 19:|
= Components =
= Components =
== Pages ==
== Pages ==
Revision as of 14:06, 10 January 2013
State reason for redesign here.
If you would like to help out, a good starting point is reading about the process another CMS went through redesigning their website. See: A Tour of the Redesigned Drupal.org
We also suggest that you join our Development Mailing List and introduce yourself. This list is the best place for any questions or discussions related to the Geeklog.net redesign.
Below is a list of proposed changes/ideas to the current Geeklog.net website.
When adding a new idea, please keep these things in mind:
- Include you name in brackets at the end of your idea.
- At the moment these are mainly point form ideas. As they develop we will be creating new wiki pages for each individual idea.
Also, when adding an idea, please consider volunteering your time to help develop it!
- Convert database and tables from collation latin1_swedish_ci to UTF-8
A list of proposed pages....
- What is the purpose of the homepage?
- I think we should showcase Geeklog more and explain why you should use Geeklog for your website while still making it easy for visitors to find support, plugins etc. (Tom)
- Take away ideas from GSOC Mentor's Summit 2011:
- Top of page navigation is not used very frequently and is often not seen by users.
- Design consisting solely/mostly of text is intimidating and not user friendly.
- Three column design appears too cluttered. One or two column design is preffered.
- "Screencast" videos are popular among non-developers. Questionable whether having the videos prominently displayed.
- Prominent download button preferred.
- Keep content for developers (perhaps labeled "contributors") separate from content for users ("site developers"?).
- Feel free to copy from other open source projects' web sites (with their permission...)
- Mixed feelings about whether and how prominently case studies and example sites should be featured. Definitely recommended not to commit to a timeline (such as "site of the week") for fear of being unable to keep such an update schedule.
- Since Geeklog 1.9.0 will support child topics should we add, delete or move the topics around? (Tom)
- Here is the propsed new topic structure:
- Geeklog.net (formerly Server)
- Summer of Code
- Archive (Private)
- AptitudeCMS (Private)
- Bugs (Private)
- Developers Only (Private)
- Maybe a short history of Geeklog with a list of Geeklogs current team members. The list could include: (Tom)
- A photo
- Their role
- A short blurb about them
- Contact link or information
- This page could list a number of ways community members could get involved. This can include Documentation, Theme development, Coding, Supporting Community members, and Financially. (Tom)
- As discussed on the mailing list it looks like we may not offer Bounties since they really have not worked out. (Tom)
- Add these points (reworded) to the "For Developers" section to help avoid any issues when developers work on a bounty. (Tom)
- A Geeklog team member(s) (which we will list somewhere) needs to green light the project and accept responsibility for adding it to Core if they approve the code submission. This probably should be done in the notes of the feature request so it is public and is easy to find.
- If a final patch is submitted then in the notes of the feature request the developer should state the bounty has been finished and he/she now wish to receive the bounty.
- In a reasonable amount of time the Geeklog team member should reply stating if it was accepted or rejected and the reasons why�
- Geeklog is only responsible for paying bounties they specifically sponsor. If all or part of the money for a bounty is sponsored by other parties it is the developers responsibility to collect the money once the submission for the bounty has been accepted by the Geeklog Team.
Theme ideas here ...
- Create a bounty on Geeklog.net too have someone step forward to develop a theme based on our design goals. (Tom)
- Use a website like 99designs.com to advertise our theme bounty. (Tom)
The new forum layout. The sentence after the Category or Forum topic is the description. The information in brackets contains the old topic and other information.
General Discussions - Lets discuss Geeklog.
- General Geeklog Discussions - General discussion about anything related to Geeklog.
- You and your Sites - Introduce yourself and/or show off your Geeklog site. (Previously My Geeklog Site)
- Geeklog Related Sites: Post sites related to Geeklog. (Previously Sites)
- Off-Topic - Post anything, news, jokes, anything unrelated to Geeklog allowed.
- Feedback - Give feedback or post suggestions. (same as Feedback)
Support - Need help?
- General Support - Geeklog and install support. (Combining General Help and Installation)
- Plugin Support - Help and support with any Geeklog plugin. (Previously Plugin Help)
- Theming Support (previously Themes)
- Documentation, Tips & Tricks - Post instructions, tips and tricks for beginners. (non wiki related, or maybe a sticky topic pointing to the wiki for beginners)
Extensions - Information on non-core Geeklog extensions.
- Plugins - Announce your Plugin and talk about it's development and features.
- Themes - Announce your Theme and talk about it's development and features.
- PHP Blocks - Announce your PHP Block and talk about it's development and features.
- Cool Hacks - Announce your Hack and talk about it's development and features.
Development & Coding - Information on developing Geeklog and it's core components
- GL 1.x - General discussion for developers on Geeklog.
- Plugins - General discussion for developers on Geeklog Core Plugins.
- Themes - General discussion for developers on Themes bundled with Geeklog
- GSOC - Google Summer of Code discussions.
International Support & Translations - Support and information for Geeklog in other languages. (List of a bunch of languages other then English, e.g. Dutch, French, Japanese, Chinese, German, etc. Maybe sticky topic in language pointing to support site. Moderator from support site)