Thứ Ba, 21 tháng 5, 2013

PROJECT TEAMS


The Joomla Project is comprised of many teams, each with a general areas of responsibility in accordance with our overall project mission/vision. Below is an outline of the teams and their areas of responsibility.

Joomla Leadership Team

The Leadership Team consists of leaders from Production Working Group and Community Working Group.
Responsibilities: Responsible for overall management of project and the community.

Production Working Group

Create software that is free, secure and of high-quality—encompasses everything that goes into the final product, not just code but also documentation, internationalization and localization efforts of all types.
Leaders: Chris Davenport, Mark Dexter, Sam Moffatt, Ron Severdia and Andrea Tarr
Responsibilities: Core code development, patches, Joomla Labs, Joomla Bug Squad, localization, internationalization, Joomla Documentation, security, Google Summer of Code

Community Working Group

Provide the structures and community management necessary to create an online community that is enjoyable and rewarding to participate in, nurture and support online communities of users, provide support and information to users, and facilitate communication between users and the Production Working Group.
Leaders: Brad Baker, Isidro Baquero, Peter Martin, Olaf Offick and Sander Potjer.

Open Source Matters

Legal, financial and other organizational needs of the Project that fall outside of the two Working Groups.
Board of Directors: Leonel Canton, Mike Carson, Ofer Cohen, Alice Grevet, Paulo Griiettner, Thomas Hampton, Dianne Henning, Sandra Ordonez, Paul Orwig, Jacques Rentzke, Marijke Stuivenberg, Radek Suski, and Sarah Watz
The Community Oversight Committee's primary responsibility (according to Article IV of the OSM bylaws) is to appoint and remove members of the OSM Board of Directors.
Members: Brad Baker, Chris Davenport, Louis Landry, Sam Moffatt, Wendy Robinson

Joomla Leadership Team


Joomla Leadership Team

The leadership of Joomla consists of three teams:
  • Production Leadership Team (PLT): responsible for coordinating the production of the Joomla CMS and Platform, including code, documentation, and localization.
  • Community Leadership Team (CLT): responsible for all Joomla websites, forums, and user groups.
  • Open Source Matters (OSM): responsible for managing all legal and financial affairs for Joomla and also the Joomla demo sites.
You can access the mailing lists of these teams using the following links:
Members of the PLT and CLT are listed below. See the OSM Website for a list of the OSM Board members.

Michael Babker

Michael BabkerLocation:  Clarksville, Tennessee, USA
Timezone: GMT – 6
Position: Production Leadership Team 
URLhttp://www.babdev.com/
Forum Profilembabker
Twitter: @mbabker

Michael has been developing using Joomla! since 2010, coming to the Bug Squad shortly after the first 1.6 Beta. In the time since, he has gone from being a user of the product with no programming experience to writing code for the CMS and Platform, either in the form of extensions or core contributions.
Suprisingly, developing code is just a hobby for him. His day job sees him work in the IT field primarily in help desk and network management roles, skills he brings back to his Joomla contributions while interacting on the tracker or mailing lists. Always seeking a challenge and learning, Michael holds an Associate of Arts in Information Technology with a concentration in Web Design as well as other technical certifications spread throughout the IT field.
When not paying the bills or writing code, Michael can be found enjoying the scenery wherever he's at in the world, seeking   new challenge, and all in all enjoying life.

Brad Baker

ImageLocation: Sydney, NSW, Australia
Timezone: GMT +9
Position: Joomla Community Leadership Team
URL: www.joomlatutorials.com
Twitter@xyzulu
Born and raised in South Africa, now living in Australia's biggest city, Sydney.
Brad has years of experience in the web hosting industry. As well as running his own local Web hosting and design business, he has been working for Rochen (www.rochen.com) for a number of years. He's been associated with the project since 2003, and brings his good humor and expertise to the ever-growing Joomla fold. Like many of us, he has succumbed to the hazards of the job and, after years of wearing out keyboards, his handwriting is illegible and spelling deplorable without the use of a spellchecker.

Isidro Baquero

Isidro BaqueroLocation: Seville, Spain, Europe 
Timezone: GMT +1
Position: Community Leadership Team
URL: http://www.gnumla.com
Forum Profilehefesto
Twitter: @isidrobaq
Born and living in Seville, south of Spain, Isidro met web technologies for the first time while studying telecommunications engineering in the early 2000s. He was so cautivated by the www that he finally left his studies to work full time as a web freelancer (site building, webmaster, community manager, english to spanish translations).
Related with Joomla since Mambo days, he owns a blog about Joomla in spanish (www.gnumla.org). He started collaborating actively with the Joomla project during early 2010, when joined the moderator team as local moderator for the spanish forum. After that, he continued to increase his involvement, joining JPeople community managers team and the JCM as Spanish editor during 2010, and becoming JPeople Communications Manager during 2011. Also, during the summer of 2011, he joined the Joomla Tweet Team and the Spanish Translation Team.

Ruth Cheesley

Ruth CheesleyLocation: United Kingdom, Europe
Timezone: GMT
Position: Community Leadership Team
URL: www.viryatechnologies.com 
Forum ProfileRCheesley
Twitter: @RCheesley
Ruth has always been a passionate supporter of free and open source software, and came across Joomla! in the early days when asked to design a website during her time as IT Technician at a school, and the rest, as they say, is history! She now runs a business - Virya Technologies and Virya Software - which specialises in Open Source technologies including Joomla! website design, management and extension creation, and Linux server management. Her personal area of interest lies within search engine optimisation and helping websites to recover from poor SEO practices. Ruth also founded Joomla! User Group Suffolk and is on the team for Joomla!Day UK events.
When she's not in front of a computer screen she can be found lurking in the countryside assessing young people completing their Duke of Edinburgh's Expedition or hunting out geocaches. She's also training for ordination with the Triratna Buddhist Community and is a field hockey goalkeeper.

Chris Davenport

ImageLocation: Shrewsbury, Shropshire, United Kingdom
Timezone: GMT
Position: Documentation Working Group Coordinator
Born 1958, Chris first began programming on a DEC PDP8 in 1975. He gained a degree in mathematics in 1979 and, after a brief spell as a mathematician in the aerospace industry, got sucked into the rapidly growing computer industry. Chris has developed software at all levels from assembly language upwards, on everything from microprocessors to mainframes, and has learnt through hard experience the value of good, disciplined commenting and thorough documentation. "Documentation is as much a part of the finished product as the code itself."
He discovered Mambo in 2003 while searching for a content management system for an intranet project. Although impressed by the product itself, he felt that the lack of documentation was a major weakness. Rather than complaining, he set about trying to fix the problem by writing his own and was soon recruited to the Documentation Team. He switched to Joomla as soon as the split occurred and is now responsible for developer documentation.

Mark Dexter

Mark DexterLocation: Seattle, Washington, USA
Timezone: GMT – 8
Position: Production Leadership Team, Bug Squad Coordinator
Forum Profiledextercowley

Mark started writing software in the 1970s on punch cards and, for 28 years, co-owned and ran a company that develops software for construction companies. During this time, he did everything from design and development to support, training, and documentation.

After retiring in 2007, Mark decided to learn more about open source software. After becoming the webmaster for a small non-profit organization, he discovered Joomla and started using version 1.5.2 in early 2008. He made the mistake of pressing the Help button and discovered that most of the help documentation hadn't been written yet. So he volunteered to write documentation and has continued to learn about Joomla and try to contribute to the project.

In the Joomla project, Mark is currently a Bug Squad Coordinator, a Development Coordinator, and the Administrator for the Joomla Student Outreach Program (JSOP). He has been a moderator on the forums, a member of the Documentation working group, and the Administrator for the 2009 Google Summer of Code program. He also has written four extensions.
Mark is especially interested in the area of automated testing using PHPUnit and Selenium. Mark has found the Joomla community to be incredibly friendly and welcoming and is excited about helping to make Joomla even better.

Peter Martin

Peter MartinLocation: Nijmegen, The Netherlands, Europe
Timezone: GMT +1
Position: Community Leadership Team
URL: www.db8.nl 
Forum Profilepe7er
Twitter: @pe7er
Like millions of others, Peter's computer career began in 1984 with the Commodore 64. Ten years later he got hooked to the Internet during his studies Marketing and Mass Communication. When plain HTML wasn't sufficient anymore he learned PHP/MySQL. In 2003 Peter discovered Mambo CMS but only got actively involved in the Joomla community in 2005 when he started helping other users at Joomla forum. Peter has been a forum Moderator since 2006 & Global Moderator since 2007.

Peter is an avid music collector, especially vinyl records, he loves art house movies and facts (trivia). Peter has his own business db8 (founded in 2005) which offers Joomla website implementation, support and development of Joomla extensions.

Olaf Offick

Olaf OffickLocation: Galway, Ireland, Europe
Timezone: GMT
Position: Community Leadership Team
URL: http://www.learn-skills.org
Forum Profileooffick
Olaf is an Internet Engineer (M.Sc.) working in Galway, Ireland. He is the founder of Learn Skills, a company providing high quality Learning Management Systems (LMS / LCMS / VLE) and Educational Materials to businesses, schools and government organisations. In the Joomla community, Olaf is working in the Joomla Global Moderator Team and the Joomla Forum Administrator Team.

Sander Potjer

Sander PotjerLocation: Weesp, The Netherlands, Europe 
Timezone: GMT +1
Position: Community Leadership Team
URL: http://www.sanderpotjer.nl
Forum Profilezanderp
Twitter: @sanderpotjer
Sander’s Joomla passion started back in 2005 by building a Joomla website for his rowing team. Next to his studies Architecture at Delft University of Technology Sander is a Joomla freelancer working on all kinds of Joomla projects.
The involvement with the Joomla community started back in 2008, as co-founder of the local Dutch communitywww.joomlacommunity.eu. In a short period they established a solid community with an active team of volunteers. The volunteers contribute by providing news, translations, documentation, forum support and by organization the Joomla User Groups (14 in a small country!) and the yearly Dutch JoomlaDays.
He is chairman of “Stichting Sympathy,” a Dutch foundation founded in January 2011 that covers all Joomla activities and promoting the Joomla project in The Netherlands.

Nick Savov

Nick SavovLocation:  Iowa, USA
Timezone: GMT – 6
Position: Production Leadership Team 
URLhttp://www.ostraining.com/
Forum ProfileNickSavov
Twitter@NickSavov
Nick Savov has been involved with Joomla for about two and a half years and web related work for only three years. He's a quick learner and enjoys learning new things by applying himself until a goal is accomplished. During his time with Joomla, he's been involved in a lot of areas of the project including documentation, Joomla Bug Squad, marketing, communication, and helping out on the developer mailing lists and the forum.
One of his favorite parts about Joomla is meeting other people in the community, getting to know them better, and working with them to accomplish common goals. He especially loves helping others to learn something new, to solve problems, and to contribute to the Joomla core.
Nick's employed at OSTraining, as the Director of Sites, where he's helped answer thousands of Joomla-related questions. As part of the job, he also gets to work with Joomla and Joomla-related products throughout the day. Having those opportunities and his colleagues as co-workers has made the position a dream job for him.

Ron Severdia

Ron SeverdiaLocation: San Francisco, CA
Timezone: GMT -8
Position: Production Leadership Team
URL: PlayShakespeare.com
Forum Profileseverdia
Twitter@severdia
Ron Severdia is CTO of Metrodigi, a leading eBook company in the San Francisco Bay Area and has directed interactive branding projects—from websites and brand identities to interactive campaigns—for clients such as HP, Verizon, Electronic Arts, Yahoo!, Visa, Walmart.com, eBay, and Apple. His prior experience includes stints as a Senior Designer and then Creative Director at Young & Rubicam, DDB, Glow, and Landor Associates. Fluent in several languages, he worked for seven years in Europe, where he won a Euro-Effie award for his creative work with Schweppes.
Ron has been using Joomla since 2006 to build sites for companies, large and small, including a worldwide branding site for Citibank. He is a member of the Kunena Forum team and he authored the Using Joomla book for O'Reilly Media. He is the founder of the Joomla-based Shakespeare site, PlayShakespeare.com.

Andrea Tarr

Andrea TarrLocation: Belchertown, MA
Timezone: GMT -5
Position: Production Leadership Team
URL: Tarr Consulting
Twitter@Tarrconsulting
Andy started programming when she was a librarian back in the late 70s. She took home a self-study guide to the IBM System-32/34 and wrote the first computerized circulation system in the state of New Hampshire.
She became deeply involved with Joomla as part of the Google Summer of Code 2009 and wrote the accessible Administrator template Hathor.
Now Andy uses Joomla with her clients because it gives clients a maintainable website that is easy to customize and extend. She specializes in understanding the customers' business needs and using her analytical & programming skills to fulfill those needs. She is the author of PHP and MySQL 24-Hour Trainer.

MISSION, VISION & VALUES


In 2008, the Joomla Project wrote the following statement to reaffirm its overall mission, vision, and project goals.

Mission

Our mission is to provide a flexible platform for digital publishing and collaboration.
(View commentary below)

Vision

In our vision, we see:
  • People publishing and collaborating in their communities and around the world
  • Software that is free, secure, and high-quality
  • A community that is enjoyable and rewarding to participate in
  • People around the world using their preferred languages
  • A project that acts autonomously
  • A project that is socially responsible
  • A project dedicated to maintaining the trust of its users
(View commentary below

Key Values

  • Freedom
  • Equality
  • Trust
  • Community
  • Collaboration
  • Usability
(View commentary below)


To further clarify the items outlined above, the following commentary is provided.
 

Mission (with commentary)

 
Our mission is to provide a flexible platform for digital publishing and collaboration.
 

Commentary:

We felt strongly that the mission statement should be short and succinct; the inspiration being the Subversion mission statement: "To create a compelling replacement for CVS."
 
The word "provide" is used because it can be taken to imply "design," "develop," and "distribute" as well as leaving the possibility of providing "software as a service" capabilities.
 
The word "platform" is used to emphasise not only that the Joomla CMS can be extended, but also that we will most likely release the Joomla Framework as a separate platform at some point and might develop a non-CMS application on top of it.
 
The word "digital" is used in preference to words like "Web" or "Internet" because many users run Joomla on an intranet with no Internet connection. A use case we kept in mind was of a school in Africa which has a network of PCs and uses Joomla to disseminate information to students, but which has no Internet connection.
 
The words "publishing" and "collaboration" were carefully chosen. "Publishing" seems an obvious choice given that Joomla is a CMS, but "collaboration" was chosen to try to express the kind of applications that we might provide on top of the Joomla Framework. With our sites and events we also provide platforms for communication and collaboration so those things are part of carrying out our mission too.
 

Vision (with commentary)

 
In our vision, we see:
 
People publishing and collaborating in their communities and around the world; 

Commentary:

Notice that we use the word "people" here and not "users." Users might be thought of as those who build and run a Web site, but by deliberately avoiding that term we broaden our vision to include everyone, including site visitors, but perhaps even those members of the community who never come into contact with the software at all but are affected by those who do.
 
Notice that "publishing and collaborating" is taken directly from our Mission Statement. Our mission is to provide a platform for publishing and collaboration and our vision is that people will be empowered by that platform to publish and collaborate.
 
The word "communities" is deliberately vague in that it could refer to the community of people who visit the user's Web site, the Joomla community, or indeed other communities too. The plural is used because people invariably belong to multiple overlapping communities.
 
The words "and around the world" hint at people being able to go beyond their local communities, however we define "local," to reach out around the world. Perhaps they are publishing to a global audience or perhaps they want to invite new collaborators into their community from around the world.
 
 
Software that is free, secure and of high-quality;

Commentary:

"Freedom" is one of our key values, but the use of the word "free" here deliberately exploits the ambiguity in the English language between "free as in freedom" and "free as in no charge." Translators of this vision statement will need to be aware that both meanings are intended.
 
The words "secure" and "high-quality" were added in response to feedback at the Core Team Summit.
 
 
A community that is enjoyable and rewarding to participate in;

Commentary:

This statement is not only a recognition that a community is essential for the future of the project, but also that it must be of a certain character, namely "rewarding and enjoyable to participate in."
 
Participation is important since the entire project hinges on it. Although the community could be thought of as including people who do not participate in any meaningful way, it is those who participate that are key to the success of the project. It follows that the community must be attractive enough for people to want to participate in it. This is a statement of our belief that if we can make the community "rewarding and enjoyable to participate in," then people will be attracted to it and will remain a part of it.
 
Of course, it doesn't say how to make the community rewarding and enjoyable to participate in because that is not an easy question to answer. It may be different things to different people and it may change over time. The community itself learns how to best reward its members.
 
 
People around the world using their preferred languages;

Commentary:

Again, "people" instead of "users."
 
The word "using" should be thought of as including activities such as installing and maintaining a Web site as well as site visitors actually using the Web site.
 
The words "around the world" and "preferred languages" are used so that languages are not thought of as being geographically localized. It should be possible for someone to use the software in their preferred languages no matter which country they find themselves in.
 
The plural "languages" is used here as people might have multiple preferred languages.
 
Our key value of "equality" makes it clear that just making the English version downloadable anywhere is not sufficient—it must be downloadable anywhere in the user's preferred langauge. Once downloaded and installed, it should also support people working in multiple languages.
 
 
A project that acts autonomously;

Commentary:

The word "project" is used here instead of "community" as only the project can make decisions. The exact boundaries of the project are ill-defined but could include Working Group members, for example, as they are often closely involved in decision-making.
 
That we should remain an organization that can make decisions autonomously is important to allay fears that we might "sell out" the project to some commercial operation.
 
 
A project that is socially responsible;

Commentary:

The words "socially responsible" echo Google's mantra "do no evil." Society could mean just "the community," but it could also refer to society in general.
 
The responsibility can be negative, meaning that there is a responsibility to refrain from acting, or it can be positive, meaning that there is a responsibility to take action.
 
An example of the project acting in a socially responsible manner is the work done by the forum moderators in ensuring that the forum is "rewarding and enjoyable to participate in." This is achieved through constant vigilance and upholding the forum rules.
 
 
A project dedicated to maintaining the trust of its users.

Commentary:

This is a recognition that anyone who is part of the community, even if only as a user of the software, places some degree of trust in the project and that is something that the project should strive to live up to.
 
One of the most important aspects of that trust is the recognition that project participants can't just think of their own individual interests, or even the interests of a collective, when making decisions.
 

Key Values (with commentary)

 
Freedom
Equality
Trust
Community
Collaboration
Usability
 

Commentary:

"Freedom" was chosen as our topmost value for many reasons. We want to give people the freedom to build Web sites with which to publish their ideas. We want to give people the freedom to collaborate with others in their own language. And we want to give people the freedom to use, copy, modify, and distribute the code and protect those freedoms using the GNU/GPL. We also want to provide people with the freedom to be a part of the community and to participate in the future development of the project.
 
"Equality" was chosen as our second key value for many reasons. Naturally we want to ensure that the community is open to everyone regardless of race, sex, age or religion. We want to ensure that everyone has the opportunity to download the software regardless of their geographical location, which includes being aware of issues such as limited bandwidth. We want people to be able to use it in their preferred language, whatever that may be, so internationalization and localization are important too. We must also consider accessibility, both of our Web sites and of the software we produce.
 
"Trust" is a necessary foundation for the project. For example, it should be possible for people to trust that the project will deliver on its promises; that people in our Working Groups should be able to trust each other. Indeed, the project and the community exists largely because of a web of trust.
 
"Community" was chosen as our next key value because we are fundamentally a community project and would be unable to achieve anything without the community. Furthermore, the tools we provide are often used in the context of building communities. A sense of community should pervade everything we do. What we do, we do as a community.
 
"Collaboration" is another theme running through the project. Joomla lets people collaborate—to say work together on things—which is not necessarily part of community. Also, other things we do, such as in Joomlacode and the documentation wiki, encourage collaboration as do all of our work processes. The GPL in general encourages people to work together and the applications created by the project and even the project's culture encourage this.
 
"Usability" is a key value because we want everyone to be able to make use of our software, our documentation, our forums, and all our other sites. By making usability a key value, we hope to guide decision-making towards wider use and greater participation.

VOLUNTEER CODE OF CONDUCT


This document outlines the Code of Conduct for all persons volunteering their service to the Joomla Project as a Core or Working Group Member or part of Open Source Matters. It covers your behaviour as a member of the Joomla community, in any forum, mailing list, Wiki, Web site, IRC channel, install-fest, public meeting or private correspondence. If you cannot agree to any of these principles, then volunteering in the Joomla Project is not for you. Accepting the role offered assumes acceptance of these principles:

Be Considerate

You are working with others as a team so be considerate of how your actions or contribution affects your colleagues and the community as a whole.

Be Respectful

Treat one another and members of the community with respect. Everyone can make a valuable contribution to Joomla. We may not always agree, but disagreement is no excuse for poor behavior or poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect the members of Joomla community to be respectful when dealing with other volunteers as well as with people from outside projects and initiatives and with users. Avoid becoming involved in flame wars, trolling, personal attacks, and repetitive arguments. Take the matters "outside" (off-list, etc) if it helps resolve the situation, and do not use communal methods of communication to be a vehicle for your private "wall of shame."

Be Collaborative

Joomla is free software and about collaboration and working together. Collaboration reduces redundancy of work done in the free software world, and improves the quality of the software produced regardless of whether you are writing code or performing some other task.
When you disagree, consult others. Disagreements, both political and technical, happen all the time, and Joomla is no exception. Disagreement, debate and constructive criticism is often how progress is made and are a necessary part of doing complex work in a team. The important goal is not to avoid disagreements or differing views but to resolve them constructively. Above all, avoid making conflicts about the work into personal conflicts. Debate should never include reference to someone's nationality, gender, religion or other personal characteristics. You should turn to the community and to the community process to seek advice and to resolve disagreements. There are also Working Group Coordinators and Team Leaders who may be able to help you figure out which direction will be most acceptable.
When you are unsure, ask for help. Nobody knows everything and nobody is expected to be perfect. Asking questions avoids many problems down the road and so questions are encouraged. Those who are asked should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum. Off-topic questions, such as requests for help on a development mailing list, detract from productive discussion.

Step Down Considerately

People on every project come and go, and Joomla is no different. When you leave or disengage from the community, in whole or in part, we ask that you do so in a way that minimizes disruption to the Project. This means you should tell people you are leaving and take the proper steps to ensure that others can pick up where you leave off.

Be Available

Check your e-mails regularly and answer them promptly—even if it's "I'll get back to you."

Be Honest

Sometimes the hardest thing to say is "no" or admit you've forgotten do something. Be honest with each other and yourself with regards to what you say and what you can realistically commit to.

Follow the Rules

Volunteers are expected to uphold Joomla's licensing and trademark requirements including, but not limited to, compliance on their own or affiliate Web sites and extensions. Make sure you have sought the appropriate approvals for domain name, name and logo usage prior to volunteering and that any extensions you distribute comply with the Joomla license.
All work contributed to the Project, whether code, documentation or other material, must observe the appropriate licenses as set down by the Core Team and Open Source Matters.
Some Workgroup members represent the Joomla Project in specific areas, but you should not speak on behalf of the Project or present yourself as an official representative of the Project unless you are specifically authorized to do so, and you should never state your opinions as the official policies of the Project.

Exercise Discretion and Confidentiality at Appropriate Times

Depending on your role, you will be privy to various levels of information. As a volunteer you are expected to keep site access details (such as logins, FTP details, etc.) secure at all times. Information contained within private forums (for example, about serious security matters, legal cases, or personal details), private mailing lists, chats or other mediums is also to be kept confidential even after you have discontinued your service. Breaches in the area of privacy and confidentiality are taken very seriously by the Project.

Conflict of Interest

When using Project resources or making decisions within your team, workgroup or the concerning Project's policy positions, you must do so based only based on the best interests of the Project and its user community. If you have a situation or affiliation that might constitute or lead to a conflict of interest or might be perceived by a reasonable person in the community to be a conflict of interest, disclose this to your Team Leaders or the team as a whole. If appropriate, after discussing with your team, you should remove yourself from specific decisions or discussions in which you may have a conflict of interest.

The Fine Print

Members of the Community Oversight Committee (Core Team) and the board of Open Source Matters are governed by additional guidelines and requirements and, where a conflict exists, these take precedence over this Code of Conduct.

The Last Bit

This Code of Conduct has changed over time and will continue to develop, but was originally derived, with permission, from the Ubuntu CoC.

Taking the website temporarily offline


There may be occasions when you will make your Joomla! website completely unavailable to visitors[1] for a short time. There is a simple switch in the Administrator back-end that enables you to take your website offline very quickly. It can be returned to service at a later time just as easily.

To take your Joomla! website temporarily offline

To make your Joomla! website unavailable to visitors, replacing it with a simple message, do this:
  1. Log in to the Administrator back-end. To learn how to do this read: Logging in or out of the Administrator back-end.
  2. Click on the Global Configuration button in the main Control Panel or click the Site  Global Configuration menu item Joomla 2.5 orSystem  Global Configuration in Joomla 3.x.
  3. There are so many configuration options that they need to be divided into separate groups or tabs. The Site tab, it should be the default first view displayed, if not click on the tab.
  4. Find where it says Site Offline and change the radio button from No to Yes Joomla 2.5(see the screenshot below) or click the Yes button in Joomla 3.x.
  5. Optional: Change the Offline Message to give your visitors some explanation about why your website is unavailable.
  6. Click the Save toolbar button to implement the new settings:
    • The Save toolbar button will save your changes and but leave you in Global Configuration.
    • The Save and Close button will save your changes and return you to the Administrator Control Panel..
  7. You should see a message confirming the settings have been changed.

Joomla 2.5

Global-config-25-site-offline.png

Joomla 3.x

Global-config-3-site-offline.png

To put your Joomla! website back online

Repeat the steps above and making sure the site offline switch is set to off.

Advanced

Note that you can display a customized page during the time that your site is offline. To do so, create a file called "offline.php" and place the file in the home directory of your template. For example, if you are using the rhuk_milkyway template, the offline.php file would go in the directory "<Joomla! home>/teamplates/rhuk_milkyway/".
  1.  unavailable to visitors
The site may site be parsable by bots and searh engines and other direct call methods

Using the htaccess method (cpanel)

You can limit access to certain resources of your website by password protecting the directories they are in.
To password protect directory with CPanel Hosting Control Panel:-
Login into your CPanel and click on Password Protect Directories
Once you click on Password Protect Directories, you will see a list of directories
Click on the directory that you wish to password protect
Fill in a Username and Password at the bottom of the page, and click Add / modify authorized user
Once user created successfully, just click “Go Back”
Now, Check the Directory requires a password to access via the web
Fill in Protected Resource Name, actually this is just the message that will show in the login window then, Highlight the user you just created from the Active Users list and click on Save button below the Protected Resource Name
To ensure you directory has been password protected, launch you browser and visit the folder, if browser prompt you to login, your directory has been protected by password!

Joomla! Administrators



As a website administrator you might be concerned about the visual appearance of a website but will pass responsibility for making changes and improvements to a web designer. Similarly, when changes to functionality are required you will contract a web developer to do the necessary work. As a website administrator you are responsible for the day-to-day operation and maintenance of the website. Activities might include ensuring that the site is properly backed up; managing user access; possibly installing extensions. You will also have responsibility for maintaining the security of the website.

Joomla! Administrator's Manual

Note from the Doc Team: The intention is that the list of topics you see below should be goal-orientated and not a "feature list" for the Administrator back-end. The items should address real and common activities that an Administrator will need to perform from time to time. Please feel free to help us by adding items you think should be included or amending items already present if you think they can be improved.