<noinclude><languages /></noinclude>
[[File:Joomla logo.png|100px|right]]
<translate>

Contributing to the Joomla Project is easy and you can give as little or as much time as you want. Anyone can contribute on any level, not just developers.
</translate>

<translate>

If you think working with Joomla! is fun, wait until you start working on it. We're passionate about helping Joomla! users make the jump to becoming contributing members of the community. All participants and future participants are expected to comply with the [[S:MyLanguage/Volunteer Code of Conduct|Joomla! Code of Conduct]].
</translate>

<translate>
==Helping the Joomla! Project== 
There are many ways you can help with Joomla:
</translate>

<translate>
=== Production Department Teams=== 
</translate>

<translate>
* Report bugs and request features in our [https://issues.joomla.org/ trackers]. Please read the article [[Filing bugs and issues]] for details on how we like our bug reports served up.</translate>
<translate>
* Submit patches for new or repaired behavior. Please read the [[S:MyLanguage/Using_the_Github_UI_to_Make_Pull_Requests|Patch submission guidelines]], for details on how to submit a patch.</translate>
<translate>
* Join the [https://forum.joomla.org/index.php developer forums] and share your ideas for how to improve Joomla!. We're always open to suggestions, although we're likely to be skeptical of large-scale suggestions without some code to back it up.</translate>
<translate>
* Join any of the [https://volunteers.joomla.org/departments/production Production Teams] and bring your personal expertise to the Joomla! community. More info about the different working groups can be found there.</translate>
<translate>

* Contribute to documentation about Joomla by creating a JDocs account and editing the Joomla Documentation Wiki.</translate>
<translate>

* Contribute to [https://crowdin.com/project/joomla-cms Joomla's Translations on Crowdin]</translate>

<translate> Should you have any questions on any of the above items, join the regular [[Bugs & Fun @Home]] events running each Saturday.</translate>

<translate>
=== Other Departments and Teams === 
</translate>
<translate>

If coding is not your area of expertise, there are many other aspects of the project in need of assistance. Visit the [https://volunteers.joomla.org/ Joomla Volunteers Portal] to find out more.</translate>
<translate> Some ongoing ways you can help:</translate>
<translate>

* Submit news about Joomla!. We syndicate all Joomla!-related news on our [https://www.joomla.org/announcements.html announcements portal]. If you have some Joomla! news that you would like to share with the community, please submit your short story, article, announcement or review there.
</translate>
<translate> * [https://magazine.joomla.org/ Joomla Community Magazine] is published on the 20th of each month, and is always happy to receive new contributions from authors.</translate>
<translate> * [https://community.joomla.org/user-groups.html Find a local Joomla User Group] and get involved at the local level.</translate>

<translate>
==Getting Started== 
</translate>
=== <translate>Ways to Contribute to Joomla</translate> ===
<translate>

Joomla! is an open source project and contributions from the community are essential to its growth and success. To see how you can get started see [https://www.joomla.org/contribute-to-joomla.html Contribute to Joomla!]
</translate>

=== <translate>Create a Joomla Identity Portal Account</translate> ===
<translate>The [https://identity.joomla.org Identity Portal] serves as a Single-Sign-On provider for a number of Joomla project sites and tools. With your account, you will be able to log in to various connected websites, including the [Mattermost|Mattermost] communications tool used by the community.</translate>

<translate>The Identity Portal is also the central location to manage your personal data within The Joomla! Project. It's where you also update the details for your [https://volunteers.joomla.org/joomlers Joomla Volunteer Profile].</translate>

<translate>To create your account, visit the [https://identity.joomla.org Identity Portal] and click on Register. Once you've created and activated your account, the first time you log in you'll be prompted to consent to a variety of policies in order to use the various connected services.</translate>

<translate>Once you have an Identity Portal account, you can then access services that use the Identity Portal SSO, which includes the [Mattermost|Mattermost] communications platform.</translate>

<translate>
==Project Tools== </translate>
<translate>

Joomla uses a range of tools to help manage the community.</translate>
<translate>

* [[Mattermost|Mattermost]] - Mattermost the tool that all Joomla teams use for communications.</translate>
* <translate>[https://identity.joomla.org Identity Portal] - Create your account to use Mattermost</translate>
<translate>
* [[GitHub|GitHub]] - Joomla's code base is managed using GitHub</translate>
<translate>

* [[Crowdin|Crowdin]] - Official Translations for Joomla language packs as well as many other aspects of the project are managed in Crowdin.</translate>

<translate>

[[Category:Joomla! Community]]
[[Category:Working Groups]]
[[Category:Volunteer Engagement]]
</translate>

Portal:Participating in the Community

2023-02-20T07:05:07Z

Partic: Glip > Mattermost

<noinclude><languages /></noinclude>
[[File:Joomla logo.png|100px|right]]
<translate>

Contributing to the Joomla Project is easy and you can give as little or as much time as you want. Anyone can contribute on any level, not just developers.
</translate>

<translate>

If you think working with Joomla! is fun, wait until you start working on it. We're passionate about helping Joomla! users make the jump to becoming contributing members of the community. All participants and future participants are expected to comply with the [[S:MyLanguage/Volunteer Code of Conduct|Joomla! Code of Conduct]].
</translate>

<translate>
==Helping the Joomla! Project== 
There are many ways you can help with Joomla:
</translate>

<translate>
=== Production Department Teams=== 
</translate>

<translate>
* Report bugs and request features in our [https://issues.joomla.org/ trackers]. Please read the article [[Filing bugs and issues]] for details on how we like our bug reports served up.</translate>
<translate>
* Submit patches for new or repaired behavior. Please read the [[S:MyLanguage/Using_the_Github_UI_to_Make_Pull_Requests|Patch submission guidelines]], for details on how to submit a patch.</translate>
<translate>
* Join the [https://forum.joomla.org/index.php developer forums] and share your ideas for how to improve Joomla!. We're always open to suggestions, although we're likely to be skeptical of large-scale suggestions without some code to back it up.</translate>
<translate>
* Join any of the [https://volunteers.joomla.org/departments/production Production Teams] and bring your personal expertise to the Joomla! community. More info about the different working groups can be found there.</translate>
<translate>

* Contribute to documentation about Joomla by creating a JDocs account and editing the Joomla Documentation Wiki.</translate>
<translate>

* Contribute to [https://crowdin.com/project/joomla-cms Joomla's Translations on Crowdin]</translate>

<translate> Should you have any questions on any of the above items, join the regular [[Bugs & Fun @Home]] events running each Saturday.</translate>

<translate>
=== Other Departments and Teams === 
</translate>
<translate>

If coding is not your area of expertise, there are many other aspects of the project in need of assistance. Visit the [https://volunteers.joomla.org/ Joomla Volunteers Portal] to find out more.</translate>
<translate> Some ongoing ways you can help:</translate>
<translate>

* Submit news about Joomla!. We syndicate all Joomla!-related news on our [https://www.joomla.org/announcements.html announcements portal]. If you have some Joomla! news that you would like to share with the community, please submit your short story, article, announcement or review there.
</translate>
<translate> * [https://magazine.joomla.org/ Joomla Community Magazine] is published on the 20th of each month, and is always happy to receive new contributions from authors.</translate>
<translate> * [https://community.joomla.org/user-groups.html Find a local Joomla User Group] and get involved at the local level.</translate>

<translate>
==Getting Started== 
</translate>
<translate>

That's all you need to know if you'd like to join the Joomla! development community. Remember, Joomla! is an open source project and contributions from the community are essential to its growth and success. To see how you can get started see [https://www.joomla.org/contribute-to-joomla.html Contribute to Joomla!]
</translate>

<translate>
==Project Tools== </translate>
<translate>

Joomla uses a range of tools to help manage the community.</translate>
<translate>

* [[Mattermost|Mattermost]] - Mattermost the tool that all Joomla teams use for communications.</translate>
<translate>

* [[GitHub|GitHub]] - Joomla's code base is managed using GitHub</translate>
<translate>

* [[Crowdin|Crowdin]] - Official Translations for Joomla language packs as well as many other aspects of the project are managed in Crowdin.</translate>

<translate>

[[Category:Joomla! Community]]
[[Category:Working Groups]]
[[Category:Volunteer Engagement]]
</translate>

RingCentral (Glip)

2023-02-20T06:45:44Z

Partic: Removed information on signing up. Added link to new Mattermost JDoc page.

Mattermost

2023-02-20T06:44:45Z

Partic: Creating Mattermost JDOC for inclusion in other onboarding items.

<noinclude><languages /></noinclude>
<translate>

[https://joomlacommunity.cloud.mattermost.com/ Mattermost] is the official Joomla communications platform.
</translate>

[[Category:Volunteer Engagement{{#translation:}}]]

Joomla User Group Past Presentations

2022-12-16T13:17:42Z

Partic: Corrected youtube address

<noinclude><languages /></noinclude>

{{:Joomla_User_Group/TOC/<translate>
en</translate>}}
<translate>==JUG Past Presentations== </translate>
<translate>

The purpose of the Joomla User Group Past Presentations page is to have a place where Groups can link their slides, banners, flyers or other media to share with other groups. The goal is that newer JUGs or JUGs that need to come up with a topic can view these files and get ideas and talking points for their meetings.</translate>

<translate>

Please upload your slides or files to Google Drive or Slideshare and then link them from this article in the table. If you have never posted to Joomla! Docs before then make sure you save the text first before attempting to link. It's a spam protection operation. There are a number of examples while in edit mode to help you. The |- gives you another row. Each field has a | in the front of it. Do not worry about the translation tags. They will be added by the translation folks later.</translate>

{{-}}
{| class="wikitable sortable"
|-
|<translate> '''Your Name'''</translate>
|<translate> '''Your JUG Name'''</translate>
|<translate> '''Presentation Name'''</translate>
|<translate> '''Link to Presentation'''</translate>
|-
|Jennifer Gress
|JUG Bay Area
|Migration from 2.5 to 3
|http://www.meetup.com/es/joomla-bay-area/events/189069482/?eventId=189069482
|-
|Jennifer Gress
|JUG Bay Area
|Working the Business side of Joomla
|http://www.meetup.com/es/joomla-bay-area/events/178466412/
|-
|Jennifer Gress
|JUG Bay Area
|Joomla 3 Features Meetup
|http://www.meetup.com/es/joomla-bay-area/pages/Joomla_3_Features_Meetup/?name=Joomla_3_Features_Meetup
|-
|Jennifer Gress
|JUG Bay Area
|Using Google Tools for Webmasters
|http://www.meetup.com/es/joomla-bay-area/events/45441402/?eventId=45441402
|-
|Jennifer Gress
|JUG Bay Area
|Extension Potluck 2013
|http://www.meetup.com/es/joomla-bay-area/events/147968522/?eventId=147968522 Read this [http://magazine.joomla.org/issues/issue-jan-2013/item/1025-successful-extension-potluck-jug-bay-area-california-usa Magazine Article to learn what an Extension Potluck] is.)
|-
|Various Australian Presentations
|Joomla Australia
|Joomla Australia have a range of presentations from their various Conferences & User Group Meetings (Meeting online since 2020 plus specially recorded ones from prior to 2020) available on their YouTube channel.
|[https://www.youtube.com/@JoomlaAustralia JoomlaAustralia YouTube Channel]
|-
|Add your name here
|Add your JUG name here
|Presentation name
|Link to presentation
|-
|Add your name here
|Add your JUG name here
|Presentation name
|Link to presentation
|-
|Add your name here
|Add your JUG name here
|Presentation name
|Link to presentation
|-
|Add your name here
|Add your JUG name here
|Presentation name
|Link to presentation
|}

__NOTOC__
{{-}}
<div class="row">
<div class="large-6 columns">{{Basic button|S:MyLanguage/Joomla_User_Group_Speakers|<translate>

Prev: Joomla! User Group Speakers</translate>|class=expand success}}</div>
<div class="large-6 columns">{{Basic button|S:MyLanguage/Reporting_A_Joomla_User_Group|<translate>

Next: Reporting a Joomla! User Group</translate>|class=expand}}</div>
</div>

<noinclude>
[[Category:User Groups]]
[[Category:Joomla! User Group]]
[[Category:JUG]]
[[Category:Events Department]]
</noinclude>

Joomla User Group Past Presentations

2022-12-16T13:17:00Z

Partic: Added JoomlaAustralia Youtube

<noinclude><languages /></noinclude>

{{:Joomla_User_Group/TOC/<translate>
en</translate>}}
<translate>==JUG Past Presentations== </translate>
<translate>

The purpose of the Joomla User Group Past Presentations page is to have a place where Groups can link their slides, banners, flyers or other media to share with other groups. The goal is that newer JUGs or JUGs that need to come up with a topic can view these files and get ideas and talking points for their meetings.</translate>

<translate>

Please upload your slides or files to Google Drive or Slideshare and then link them from this article in the table. If you have never posted to Joomla! Docs before then make sure you save the text first before attempting to link. It's a spam protection operation. There are a number of examples while in edit mode to help you. The |- gives you another row. Each field has a | in the front of it. Do not worry about the translation tags. They will be added by the translation folks later.</translate>

{{-}}
{| class="wikitable sortable"
|-
|<translate> '''Your Name'''</translate>
|<translate> '''Your JUG Name'''</translate>
|<translate> '''Presentation Name'''</translate>
|<translate> '''Link to Presentation'''</translate>
|-
|Jennifer Gress
|JUG Bay Area
|Migration from 2.5 to 3
|http://www.meetup.com/es/joomla-bay-area/events/189069482/?eventId=189069482
|-
|Jennifer Gress
|JUG Bay Area
|Working the Business side of Joomla
|http://www.meetup.com/es/joomla-bay-area/events/178466412/
|-
|Jennifer Gress
|JUG Bay Area
|Joomla 3 Features Meetup
|http://www.meetup.com/es/joomla-bay-area/pages/Joomla_3_Features_Meetup/?name=Joomla_3_Features_Meetup
|-
|Jennifer Gress
|JUG Bay Area
|Using Google Tools for Webmasters
|http://www.meetup.com/es/joomla-bay-area/events/45441402/?eventId=45441402
|-
|Jennifer Gress
|JUG Bay Area
|Extension Potluck 2013
|http://www.meetup.com/es/joomla-bay-area/events/147968522/?eventId=147968522 Read this [http://magazine.joomla.org/issues/issue-jan-2013/item/1025-successful-extension-potluck-jug-bay-area-california-usa Magazine Article to learn what an Extension Potluck] is.)
|-
|Various Australian Presentations
|Joomla Australia
|Joomla Australia have a range of presentations from their various Conferences & User Group Meetings (Meeting online since 2020 plus specially recorded ones from prior to 2020) available on their YouTube channel.
|[https://www.youtube.com/@JoomlaAu JoomlaAustralia YouTube Channel]
|-
|Add your name here
|Add your JUG name here
|Presentation name
|Link to presentation
|-
|Add your name here
|Add your JUG name here
|Presentation name
|Link to presentation
|-
|Add your name here
|Add your JUG name here
|Presentation name
|Link to presentation
|-
|Add your name here
|Add your JUG name here
|Presentation name
|Link to presentation
|}

__NOTOC__
{{-}}
<div class="row">
<div class="large-6 columns">{{Basic button|S:MyLanguage/Joomla_User_Group_Speakers|<translate>

Prev: Joomla! User Group Speakers</translate>|class=expand success}}</div>
<div class="large-6 columns">{{Basic button|S:MyLanguage/Reporting_A_Joomla_User_Group|<translate>

Next: Reporting a Joomla! User Group</translate>|class=expand}}</div>
</div>

<noinclude>
[[Category:User Groups]]
[[Category:Joomla! User Group]]
[[Category:JUG]]
[[Category:Events Department]]
</noinclude>

GSoC 2022 Project Ideas

2022-04-18T01:39:20Z

Partic: /* Project Description */ Spelling mistake corrected.

{{Top portal heading|color=white-bkgd|text-color=#333|title=
Welcome to Joomla GSoC 2022 Projects Page }}
[[Image:Gsoc2016.png|150px|center|link=GSoC 2020]]

Welcome to the [[GSoC_2022|Joomla Google Summer of Code (GSoC) 2022]] projects page.

If you are interested in participating as a student please review the materials on applying that are available at [https://developers.google.com/open-source/gsoc/faq Google]. We strongly encourage you to ask questions about process and projects on our [https://groups.google.com/forum/#!forum/jgsoc joomla-gsoc mailing list] and join our
[https://glip.com/joomla public Glip / Ringcentral chat tool].

'''''Note: The GSoC 2022 projects are displayed in no particular order'''''

==Project I: Workflow/scheduler ==

===Project Description===
With Joomla! 4.0 and 4.1 two new features were implemented into Joomla!: the workflow and the task scheduler. In this project both features should be combined. Workflow transitions which are then executed by the scheduler when they are scheduled.Therefore the user interface of the articles extension has to be extended + different task/workflow plugins need to be created.
As a student, here is the list of things expected from you as deliverable for the project:
*Deliver an user interface suggestion for com_content how the user interface can look like for pre-defining transition chains.
*Implement the user interface in com_content
*Deliver a task plugin to execute the transitions via the scheduler extension

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Nice to have: Understanding of the Joomla! Scheduler and workflow extension

===Difficulty===
*Medium

===Project Type===
*Large [350 Hrs]

===Mentors===
*Yatharth Vyas
*Tushar
*Benjamin
*Christiane

[[Image:Gsoc2016.png|30px|center]]

==Project II: Guided Tour==

===Project Description===

In Joomla! are certain workflows needed to do certain tasks. Currently, users have to read the documentation if they’re new and want to know how they can achieve different things. This project should implement the functionality of guided tours in Joomla!. A tour is a click-through path which the user can follow to fulfill certain tasks like creating an article. So on the one hand Joomla! core should deliver basic tours for users to use core functionality without the need to read the documentation. On the other hand, it should be possible to create their own tours (e.g. as administrators for system operators), copy and change existing tours or allow 3rd party developers to ship their own tours when their extension will be installed.

The project has a history: https://docs.joomla.org/Guided_Tour

Now we want to make the project ready for the next Joomla Version.

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript

===Difficulty===
*Easy

===Project Type===
*Medium [175 Hrs]

===Mentors===
*Patrick Jackson
*Eyvaz Ahmadzada
*Jatin Salve
*Freyam Mehta

[[Image:Gsoc2016.png|30px|center]]

==Project III: SEO ==

===Project Description===
Joomla! 4.0 is built around a lot of SEO improvements. In this project you should implement additional basic SEO features.
As a student, here is the list of things expected from you as deliverable for the project:
*Review the current Joomla! 4 version and find out existing SEO features
*Define and propose new useful features which we can ship in future Joomla! Versions
*Implement features agreed with your mentor

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Nice to have: SEO experience

===Difficulty===

*Medium

===Project Type===
*Medium [175 Hrs]

===Mentors===
*Christopher Wagner
*Philip Walton
*Shivam Rajput

[[Image:Gsoc2016.png|30px|center]]

==Project IV: Accessibility Plugin ==

===Project Description===
Joomla uses an accessibility Plugin. This Plugin should be forked and re-written completely.

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript

===Difficulty===

*Medium

===Project Type===
*Medium [175 Hrs]

===Mentors===
*Achilleas Papageorgiou
*Viviana Menzel
*Kumar Shivam

[[Image:Gsoc2016.png|30px|center]]

==Project V: Schema.org==

===Project Description===
Currently Joomla! uses inline microdata for adding rich snippets. The drawback of this implementation is that it’s hard coded (can’t be changed from the backend, only by overrides) and it is very generic. With this project, Joomla! should switch to a schema.org JSON+LD implementation which is configurable via the backend (e.g in article, category view).
As a student, here is the list of things expected from you as deliverable for the project:
*Suggest and implement a JSON+LD library
*Implement article/menu/category/… parameter interface to add rich snippets to articles.
*Output the rich snippets dynamically in the frontend

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript

===Difficulty===

*Hard

===Project Type===
*Large [350 Hrs]

===Mentors===
*Niels
*Richard Faith
*Anurag Kumar
*Rishabh Ranjan Jha

[[Image:Gsoc2016.png|30px|center]]

[[Image:Gsoc2016.png|50px|center]]

<noinclude>
[[Category:Google Summer of Code 2022]]
[[Category:Google Summer of Code]]
</noinclude>

GSoC 2022

2022-04-01T07:24:37Z

Partic: Added resources on setting up an environment.

{{Top portal heading|color=white-bkgd|text-color=#333|title=Welcome to Joomla Google Summer of Code 2022 }}
[[Image:Gsoc2016.png|200px|center]]
<noinclude><languages /></noinclude>
<translate>

This page will aim to be a general informational page for students, mentors and others interested in Joomla's Google Summer of Code Program.</translate>

<translate>

{{tip|title=Make sure to check out the [[GSoC 2022 Project Ideas|2022 project list]]}} </translate>

<translate>
== What is Joomla? == </translate>
<translate>
Joomla is a very popular and well known FOSS content management system powering currently around 3-4% of the internet.</translate>
<translate>

Joomla developers are currently working on multiple projects.
* Joomla 4.x was released in August 2021, and this year's GSoC projects are aimed at developing new features or significantly enhancing existing features for the next major release of Joomla 4.x. Joomla 4.x is maintained for bugs, security and feature enhancements.
* Joomla 3.x Version is still being supported, but the focus for this version is bug and security patches only. No new features are being introduced going forward in Joomla 3.x.

Additionally, when you look through [https://github.com/joomla Joomla's Github Repositories] there are many side projects related to testing, performance, and other things.

It's important to note that [https://github.com/joomla/joomla-cms joomla-cms is the primary repository] for the development of the CMS.</translate>

<translate>
== What is GSoC? == </translate>
<translate>

Google Summer of Code is a program run by Google for college students interested in getting a stipend to contribute to Open Source Software. They will spend their summer with improving and writing new features for the project. [https://summerofcode.withgoogle.com/ Visit the Google Summer of Code website to learn more.]</translate>

<translate>

*[https://volunteers.joomla.org/teams/google-summer-of-code-joomla-team Joomla GSoC Team on Joomla Volunteers Portal]</translate>

<translate>
=== GSoC Project Timeline === </translate>
<translate>
Before getting onboard for this year's program, please familiarise yourself with:
* [https://summerofcode.withgoogle.com/how-it-works How Google Summer of Code works]
* [https://developers.google.com/open-source/gsoc/timeline Review the GSoC 2022 Timeline]</translate>

<translate>If you still think GSoC is for you, express your interest in participating in GSoC 2022 as a Contributor by filling in the [https://forms.gle/eiHgWehmWQKE9jBJ7 Joomla GSoC 2022 registration form].</translate>

Once we receive your form, you will receive:
* Some more information on participating in GSoC with Joomla
* An invitation to join Joomla's organisation chat (using RingCentral)
* Be added to a general chanel on RingCentral where we'll interact with all interested students during the application phase.
* Be added to a personal channel on RingCentral where you'll be able to interact with mentors for the project you're interested in.

<translate>
=== Project Proposal === </translate>
<translate>

Please check the [[GSoC Student Application Template]] to understand what we are expecting from your proposal.</translate>

<translate>
===Last years projects:=== </translate>
<translate>

*[https://summerofcode.withgoogle.com/archive/2019/organizations/6743345328553984/ Google Summer of Code for Joomla! 2019]
*[https://summerofcode.withgoogle.com/archive/2018/organizations/6484151049912320/ Google Summer of Code for Joomla! 2018]</translate>

<translate>
== Information For Students == 
</translate>
<translate>

* [[GSoC 2022 Project Ideas|Joomla's project list]]
* [[GSoC Student Selection Criteria]]
* [[GSoC Student Application Template]]
* [https://groups.google.com/forum/?hl=en#!forum/jgsoc Joomla GSoC Mailing List]
* [https://groups.google.com/forum/#!forum/joomla-dev-cms General Joomla CMS Developer Mailing List]</translate>

<translate>
==Information for Mentors== 
</translate>
<translate>

*Want to be a mentor? Please check the [[GSoC Mentor Guidelines]].
*[[GSoC Mentors Selection Criteria]]</translate>

<translate>
==Any questions please do contact the Joomla GSoC Core Team 2022:== 
</translate>
<translate>

*[mailto:shivam.rajput@community.joomla.org Shivam Rajput (Lead and Admin)]
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr (Assistant)]
*Benjamin Trenkle
*Philip Walton</translate>

<translate>
==Related Articles== 
</translate>
<translate>
===Google Summer of Code Articles on the Community Blog=== 
</translate>
<translate>

*[https://community.joomla.org/gsoc-2021.html Joomla GSoC 2021 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2020.html Joomla GSoC 2020 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2019.html Joomla GSoC 2019 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2018.html Joomla GSoC 2018 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2017.html Joomla GSoC 2017 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2016.html Joomla GSoC 2016 blog articles]</translate>

<translate>
===Google Summer of Code Articles on Joomla Community Magazine=== 
</translate>
<translate>

*[https://magazine.joomla.org/all-issues/tags/google-summer-of-code Joomla Community Magazine GSoC articles]</translate>

<translate>== Getting familiar with Joomla==
Not familiar with Joomla, Github and new to Open Source?
You may be best upskilling, getting set up and getting familiar with Joomla before you apply for GSoC.
Visit the [https://www.joomla.org/contribute-to-joomla.html Contribute to Joomla page] to find out all the different ways you can help. You can get familiar with using Joomla by helping with many other aspects apart from coding. Whether it's contributing documentation, adding translations in your language, participating in marketing activities or writing a magazine article, there's many ways to still make a contribution if you're not experienced with coding, bug testing or developing in PHP.
</translate>

<translate>==Setting up your Joomla Development Environment==
Here are some resources for getting familiar with Joomla and installing a Joomla Development environment:</translate>

<translate>'''Beginners:'''

[https://magazine.joomla.org/all-issues/june-2020/github-installing-git Read this Joomla Magazine Article] that walks through the entire process of installing XAMPP on Windows, installing Joomla 4, and adding the Joomla Patch Tester</translate>

<translate>'''Intermediate:'''

[https://docs.joomla.org/Special:MyLanguage/J4.x:Setting_Up_Your_Local_Environment Setting Up Your Local Environment guide on Joomla Docs] assumes you are familiar with the base concepts needed, but has links through to various concepts of setting up your local environment to help.</translate>

<translate>'''Advanced:'''

[https://gist.github.com/ditsuke/4c100e54b24b667406e145d838c08fac Check out Tushar's Github Guide] - This guide assumes you have a local dev environment set up and are already familiar with using Git for development version control.</translate>

<translate>'''Development Tools'''

Joomla developers also have a number of tools that they use, and on RingCentral you will find channels for some of these tools where you can get further assistance with using them to develop in Joomla:
* [https://visualstudio.microsoft.com/ Microsoft Visual Studio]
* [https://www.jetbrains.com/phpstorm/ JetBrains PHPStorm]
</translate>

<noinclude>
[[Category:Google Summer of Code 2022]]
[[Category:Google Summer of Code]]
</noinclude>

Tutorials:Beginners

2022-02-05T11:53:14Z

Partic: Added links to JUG and Joomla Events calendar.

<noinclude><languages /></noinclude>

<noinclude><translate>
This page is a Portal to a list Tutorials aimed at Beginning Joomla! Users, please note the timestamp on the above notice.</translate></noinclude>

<translate>

If you have any ideas, please create redlinks to topics you would like covered under '''Wanted Topics''' below.
</translate>

<translate>==Topics== </translate>
<translate>
*[[S:MyLanguage/J3.0:Getting Started with Joomla!|Getting Started with Joomla! 3]]
**[[S:MyLanguage/J3.0:Getting Started with Templates|Getting Started with Templates]]
**[[S:MyLanguage/J3.0:Getting Started with Categories|Getting Started with Categories]]
**[[S:MyLanguage/J3.0:Getting Started with Articles|Getting Started with Articles]]
**[[S:MyLanguage/J3.0:Getting Started with Menus|Getting Started with Menus]]
**[[S:MyLanguage/J3.0:Getting Started Modules|Getting Started with Modules]]
*[[S:MyLanguage/J3.1:How To Use Content Tags in Joomla!|How To Use Content Tags in Joomla! 3]]</translate>
<translate>
*[[S:MyLanguage/Content_editors|Editing with TinyMCE]]</translate>

<translate>==Wanted Topics== </translate>

<translate>==Video Resources== </translate>
<translate> In addition to the over 700 tutorials in the Joomla Documentation, there's a wide variety of video resources available to help you with learning Joomla.</translate>
<translate> Thanks to the [https://magazine.joomla.org/all-issues/october-2020/where-to-find-the-best-joomla-tutorial-videos Joomla Magazine] there ar a lot of them found. If you know more please add them.</translate>

<translate>=== Joomla's own YouTube channel === </translate>

<translate> The first thing you can do is head over to Joomla’s official YouTube channel, where all tutorials are neatly listed in [https://www.youtube.com/c/joomla/playlists multiple playlists]. Here you’ll find tutorials on all kinds of subjects, from customizing Joomla to patch testing. </translate>

<translate>
Examples are [https://www.youtube.com/playlist?list=PL0Lg2fzcJu1TqH4iC8sfZby_0F02Ib56p Joomla Tutorials] playlist,
[https://www.youtube.com/watch?v=22RXppJjXf8&list=PL0Lg2fzcJu1R3q6aYKX-olfGQm_o6uXyq How to patch test] playlist and
[https://www.youtube.com/watch?v=4JDsdfnlOhE&list=PL0Lg2fzcJu1R8PCZi0wVNE6QYZUqATvpE How to develop an MVC component] playlist.</translate>

<translate>=== Joomla training videos from OSTraining === </translate>

<translate> OS Training provides online training to teach people how to build websites. For Joomla, they developed free classes on five topics: a beginners guide, maintenance, security, creating multilingual sites, and SEO. Each class contains multiple videos. With over 80 videos suitable for various skill levels, the official Joomla training covers most of the tasks you could possibly want to do with Joomla. The videos have been there for quite some time now and some of them may seem outdated, but the basics have remained the same so these tutorials are still a useful resource.</translate>

<translate> Find the free videos [https://www.youtube.com/watch?v=XpBGeHkfXpc&list=PLtaXuX0nEZk_4XIvoPA7O0xT_sYRKnTos here on Youtube].</translate>

<translate> More (paid) Videos on [https://www.ostraining.com/joomla-classes/ OS Training] and there partner [https://www.joomlashack.com/classes/joomla/ Joomlashack].</translate>

<translate>=== Cloud Access === </translate>

<translate> Cloud Access is our partner and service provider for the free joomla.com domains. On their website, they have loads of free tutorials, both video and written.</translate>
<translate> You can find them [https://www.cloudaccess.net/joomla-knowledgebase/92-joomla-3-1.html here] or their [https://www.youtube.com/playlist?list=PLn5i4hx3TuLENWOYNe47PSmbDivJV_Lr_ YouTube Channel]</translate>

<translate>===Tim Davis Basic Joomla Tutorials=== </translate>

<translate> The Basic Joomla Tutorials channel on YouTube features Joomla tutorials and live streams that help Joomla fans and users get more success and enjoyment out of their Joomla sites. Tim Davis, the host, is very experienced in creating videos (his company provides video tutorials for their clients) and good at explaining complex things. The videos look professional and are [https://www.youtube.com/basicjoomla fun to watch].</translate>

<translate>===Eoin Oliver’s Joomla Tutorials=== </translate>

<translate> OK, this one is a true hidden gem and we are really glad we found it: Eoin Oliver provides tips for professional web designers. If you are looking for ways to make your job easier, Eoin Oliver’s channel is the place to go! Eoin has great tips that can save you a lot of work and reduce the number of support requests. [https://www.youtube.com/channel/UCDMDQomkFd-3x-8l2UT3JPg Very interesting]!</translate>

<translate>===Videos from JUGs and Joomla Events=== </translate>

<translate> Several Joomla User Groups have their own video channels where they share the videos from their meetings. Not really how-to’s, but interesting nevertheless.</translate>

<translate>
Various Joomla User Groups, for example Joomla Australia and Joomla London, organise virtual meetups you can join.

* Joomla Australia’s channel has a number of sessions from both JoomlaDay Australia and more recently their virtual Joomla User Group sessions. [https://www.youtube.com/c/JoomlaAustralia Visit Joomla Australia's Youtube Channel].</translate>

* <translate> Parlez-vous Français? Check out the videos from [https://www.youtube.com/channel/UCNTe8CGmY4U_Qpj8YfGQ5qQ/videos JoomlaDay France].</translate>

* <translate> Hablas español? Podcast-channel [https://www.youtube.com/channel/UCBc-rjWEkjTjJegZ2f08hnA Mastermind Joomla] has videos as well.</translate>

* <translate> Spreek je Nederlands? Check out the videos from [https://www.youtube.com/user/JoomlaDagen JoomlaDays The Netherlands].</translate>

* <translate> Parli italiano? On Joomla.it there is a free video course on the [https://www.joomla.it/guide/corso-joomla-3-start.html basics of Joomla] 3.x</translate>

* <translate> J and Beyond, the annual European international Joomla Conference, has made hundreds of interesting videos, [https://www.youtube.com/user/jandbeyondev/videos from presentations and talks on all kinds of topics].</translate>

* <translate>[https://www.youtube.com/c/JoomlalondonUk Joomla! London have a comprehensive range of video session] from their user group over the years. Their sessions often go into an in depth level of detail on technical topics.</translate>

<translate>[https://community.joomla.org/user-groups.html Joomla User Groups] around the world hold a range of events locally and internationally. Check out the [https://community.joomla.org/events.html Joomla Events Calendar] for events that are coming up near you, or follow various groups to find out more about resources they may publish after the event.</translate>

<translate>===More=== </translate>

<translate> Extension developers often have tutorial videos on their website as well. Akeeba, the developer of Akeeba Backup and Admin Tools, has great videos on [https://www.akeeba.com/videos.html how to use their extensions].</translate>

<translate> These are just a few of the tutorial videos available. If you type in [https://www.youtube.com/results?search_query=joomla+training “Joomla training”] on YouTube, you’ll find there are many more to choose from, for all levels: beginner tutorials, developers guides, one-time explanations on how to fix certain errors, and complete crash courses.</translate>

<translate> More can be find in the category below.</translate>
<noinclude>
[[Category:video]]
[[Category:Beginners]]
</noinclude>

Tutorials:Beginners

2022-02-05T11:49:48Z

Partic: Bullet list on Joomla User Group videos; Added JUGL channel

<noinclude><languages /></noinclude>

<noinclude><translate>
This page is a Portal to a list Tutorials aimed at Beginning Joomla! Users, please note the timestamp on the above notice.</translate></noinclude>

<translate>

If you have any ideas, please create redlinks to topics you would like covered under '''Wanted Topics''' below.
</translate>

<translate>==Topics== </translate>
<translate>
*[[S:MyLanguage/J3.0:Getting Started with Joomla!|Getting Started with Joomla! 3]]
**[[S:MyLanguage/J3.0:Getting Started with Templates|Getting Started with Templates]]
**[[S:MyLanguage/J3.0:Getting Started with Categories|Getting Started with Categories]]
**[[S:MyLanguage/J3.0:Getting Started with Articles|Getting Started with Articles]]
**[[S:MyLanguage/J3.0:Getting Started with Menus|Getting Started with Menus]]
**[[S:MyLanguage/J3.0:Getting Started Modules|Getting Started with Modules]]
*[[S:MyLanguage/J3.1:How To Use Content Tags in Joomla!|How To Use Content Tags in Joomla! 3]]</translate>
<translate>
*[[S:MyLanguage/Content_editors|Editing with TinyMCE]]</translate>

<translate>==Wanted Topics== </translate>

<translate>==Video Resources== </translate>
<translate> In addition to the over 700 tutorials in the Joomla Documentation, there's a wide variety of video resources available to help you with learning Joomla.</translate>
<translate> Thanks to the [https://magazine.joomla.org/all-issues/october-2020/where-to-find-the-best-joomla-tutorial-videos Joomla Magazine] there ar a lot of them found. If you know more please add them.</translate>

<translate>=== Joomla's own YouTube channel === </translate>

<translate> The first thing you can do is head over to Joomla’s official YouTube channel, where all tutorials are neatly listed in [https://www.youtube.com/c/joomla/playlists multiple playlists]. Here you’ll find tutorials on all kinds of subjects, from customizing Joomla to patch testing. </translate>

<translate>
Examples are [https://www.youtube.com/playlist?list=PL0Lg2fzcJu1TqH4iC8sfZby_0F02Ib56p Joomla Tutorials] playlist,
[https://www.youtube.com/watch?v=22RXppJjXf8&list=PL0Lg2fzcJu1R3q6aYKX-olfGQm_o6uXyq How to patch test] playlist and
[https://www.youtube.com/watch?v=4JDsdfnlOhE&list=PL0Lg2fzcJu1R8PCZi0wVNE6QYZUqATvpE How to develop an MVC component] playlist.</translate>

<translate>=== Joomla training videos from OSTraining === </translate>

<translate> OS Training provides online training to teach people how to build websites. For Joomla, they developed free classes on five topics: a beginners guide, maintenance, security, creating multilingual sites, and SEO. Each class contains multiple videos. With over 80 videos suitable for various skill levels, the official Joomla training covers most of the tasks you could possibly want to do with Joomla. The videos have been there for quite some time now and some of them may seem outdated, but the basics have remained the same so these tutorials are still a useful resource.</translate>

<translate> Find the free videos [https://www.youtube.com/watch?v=XpBGeHkfXpc&list=PLtaXuX0nEZk_4XIvoPA7O0xT_sYRKnTos here on Youtube].</translate>

<translate> More (paid) Videos on [https://www.ostraining.com/joomla-classes/ OS Training] and there partner [https://www.joomlashack.com/classes/joomla/ Joomlashack].</translate>

<translate>=== Cloud Access === </translate>

<translate> Cloud Access is our partner and service provider for the free joomla.com domains. On their website, they have loads of free tutorials, both video and written.</translate>
<translate> You can find them [https://www.cloudaccess.net/joomla-knowledgebase/92-joomla-3-1.html here] or their [https://www.youtube.com/playlist?list=PLn5i4hx3TuLENWOYNe47PSmbDivJV_Lr_ YouTube Channel]</translate>

<translate>===Tim Davis Basic Joomla Tutorials=== </translate>

<translate> The Basic Joomla Tutorials channel on YouTube features Joomla tutorials and live streams that help Joomla fans and users get more success and enjoyment out of their Joomla sites. Tim Davis, the host, is very experienced in creating videos (his company provides video tutorials for their clients) and good at explaining complex things. The videos look professional and are [https://www.youtube.com/basicjoomla fun to watch].</translate>

<translate>===Eoin Oliver’s Joomla Tutorials=== </translate>

<translate> OK, this one is a true hidden gem and we are really glad we found it: Eoin Oliver provides tips for professional web designers. If you are looking for ways to make your job easier, Eoin Oliver’s channel is the place to go! Eoin has great tips that can save you a lot of work and reduce the number of support requests. [https://www.youtube.com/channel/UCDMDQomkFd-3x-8l2UT3JPg Very interesting]!</translate>

<translate>===Videos from JUGs and Joomla Events=== </translate>

<translate> Several Joomla User Groups have their own video channels where they share the videos from their meetings. Not really how-to’s, but interesting nevertheless.</translate>

<translate>
Various Joomla User Groups, for example Joomla Australia and Joomla London, organise virtual meetups you can join.

* Joomla Australia’s channel has a number of sessions from both JoomlaDay Australia and more recently their virtual Joomla User Group sessions. [https://www.youtube.com/c/JoomlaAustralia Visit Joomla Australia's Youtube Channel].</translate>

* <translate> Parlez-vous Français? Check out the videos from [https://www.youtube.com/channel/UCNTe8CGmY4U_Qpj8YfGQ5qQ/videos JoomlaDay France].</translate>

* <translate> Hablas español? Podcast-channel [https://www.youtube.com/channel/UCBc-rjWEkjTjJegZ2f08hnA Mastermind Joomla] has videos as well.</translate>

* <translate> Spreek je Nederlands? Check out the videos from [https://www.youtube.com/user/JoomlaDagen JoomlaDays The Netherlands].</translate>

* <translate> Parli italiano? On Joomla.it there is a free video course on the [https://www.joomla.it/guide/corso-joomla-3-start.html basics of Joomla] 3.x</translate>

* <translate> J and Beyond, the annual European international Joomla Conference, has made hundreds of interesting videos, [https://www.youtube.com/user/jandbeyondev/videos from presentations and talks on all kinds of topics].</translate>

* <translate>[https://www.youtube.com/c/JoomlalondonUk Joomla! London have a comprehensive range of video session] from their user group over the years. Their sessions often go into an in depth level of detail on technical topics.</translate>

<translate>===More=== </translate>

<translate> Extension developers often have tutorial videos on their website as well. Akeeba, the developer of Akeeba Backup and Admin Tools, has great videos on [https://www.akeeba.com/videos.html how to use their extensions].</translate>

<translate> These are just a few of the tutorial videos available. If you type in [https://www.youtube.com/results?search_query=joomla+training “Joomla training”] on YouTube, you’ll find there are many more to choose from, for all levels: beginner tutorials, developers guides, one-time explanations on how to fix certain errors, and complete crash courses.</translate>

<translate> More can be find in the category below.</translate>
<noinclude>
[[Category:video]]
[[Category:Beginners]]
</noinclude>

Display error messages and notices

2021-11-26T08:55:06Z

Partic: Added alerts - adds a contextual keyword for a synonym of messages.

<noinclude><languages /></noinclude>
<translate>
Errors, warnings, alerts and notices can be displayed from any component, module, plugin or template using the methods outlined below.</translate>

<source lang="php">
// Get a handle to the Joomla! application object
$application = JFactory::getApplication();

// Add a message to the message queue
$application->enqueueMessage(JText::_('SOME_ERROR_OCCURRED'), 'error');

/** Alternatively you may use chaining */
JFactory::getApplication()->enqueueMessage(JText::_('SOME_ERROR_OCCURRED'), 'error');
</source>

<translate>
The second argument to the [http://api.joomla.org/11.4/Joomla-Platform/Application/JApplication.html#enqueueMessage enqueueMessage] function is the type of the message. The default is 'message', but 'error' results in a different style for the message. The message will be displayed in place of a special <tt>jdoc:include</tt> statement in your template. Place the following in your template at the location where you want messages to appear.</translate>

<source lang="php">
<jdoc:include type="message" />
</source>

<translate>
== Message == 
</translate>

<div style="background-color: #dff0d8; color: #3c763d; border-top: 3px solid #d6e9c6; border-bottom: 3px solid #d6e9c6; padding-left: 1em; font-weight: bold;">
Message
</div>
<source lang="php">
JFactory::getApplication()->enqueueMessage('Message');
</source>

<translate>
== Notice == 
</translate>

<div style="background-color: #c3d2e5; color: #0055bb; border-top: 3px solid #84a7db; border-bottom: 3px solid #84a7db; padding-left: 1em; font-weight: bold;">
Notice
</div>
<source lang="php">
JError::raiseNotice( 100, 'Notice' );
</source>

<translate>
== Warning == 
</translate>

<div style="background-color: #efe7b8; color: #c00; border-top: 3px solid #f0dc7e; border-bottom: 3px solid #f0dc7e; padding-left: 1em; font-weight: bold;">
Warning
</div>
<source lang="php">
JError::raiseWarning( 100, 'Warning' );
</source>

<translate>
== Error == 
</translate>

<div style="background-color: #e6c0c0; color: #c00; border-top: 3px solid #DE7A7B; border-bottom: 3px solid #DE7A7B; padding-left: 1em; font-weight: bold;">
Error
</div>
<source lang="php">
JError::raiseError( 4711, 'A severe error occurred' );
</source>

<translate>
== Joomla! 3.x is bootstrapped == 
</translate>
<translate>
Since Joomla! {{JVer|3.x}} uses bootstraped templates, the messages will use the standard bootstrap CSS styles for Alerts.</translate>

<translate>
See: http://getbootstrap.com/2.3.2/components.html#alerts</translate>

<translate>
The general syntax remains:</translate>

<source lang="php">
JFactory::getApplication()->enqueueMessage('Your Message', 'type');
</source>

<translate>
Where '''type''' can be one of</translate>

<translate>
* 'message' (or empty) - green
* 'notice' - blue
* 'warning' - yellow
* 'error' - red
</translate>

<translate>
== See also == 
</translate>
<translate>
* [http://api.joomla.org/11.4/Joomla-Platform/Error/JError.html JError on api.joomla.org]
* [http://api.joomla.org/11.4/Joomla-Platform/Application/JApplication.html JApplication on api.joomla.org]
</translate>
__NOTOC__
<noinclude>
<translate>

[[Category:Development]]
[[Category:Tutorials]]
[[Category:Component Development]]
</translate>
</noinclude>

Help4Joomla

2021-10-28T04:35:40Z

Partic:

==What is Help4Joomla?==
Help4Joomla is a list of people, and tasks they can do. If you add yourself to the list then others (ideally team leaders and department coordinators) can contact you and ask for your help to accomplish something needed.

=== Getting Started ===
In the [https://magazine.joomla.org/all-issues/october-2021/help4joomla-needs-you Help4Joomla article (October 2021 Joomla Community Magazine)] for more information on the Help4Joomla concept.

This continued on from the [https://magazine.joomla.org/all-issues/september-2021/can-you-give-some-time4joomla Time4Joomla article (September 2021 JCM)] that outlines a number of ways you can get involved with self-driven and self-paced contributions to Joomla.

=== Adding where you can help ===
Simply [https://docs.joomla.org/index.php?title=Special:UserLogin&returnto=Help4Joomla log in] and add yourself, your native language and other languages you can communicate in and whether you are active at the moment.

Do not add other people. It's essential that this is a system driven by peoples desire to help out and they give their contact details.

== Help4Joomla Volunteers ==
{| class="wikitable sortable"
|-
! Name !! Tasks & Skills !! Native Language !! Other Languages !! Available to do the task !! Contact details
|-
| Phil Walton|| Proofreading and improving the readability of documents written by none English speakers || English || None || Available || [https://volunteers.joomla.org/joomlers/1702-philip-walton Joomler Profile]
|-
| Patrick Jackson|| Technical writing; Proofreading; SEO; Analytics; Case Studies || English || None || Available || [https://volunteers.joomla.org/joomlers/213-patrick-jackson Joomler Profile]
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|}

''Note that this is an interim solution for recording volunteers looking to Help4Joomla''

<noinclude>
[[Category:Volunteer Engagement{{#translation:}}]]
</noinclude>

Help4Joomla

2021-10-28T04:33:01Z

Partic: Added Time4Joomla & some more sub headings

==What is Help4Joomla?==
Help4Joomla is a list of people, and tasks they can do. If you add yourself to the list then others (ideally team leaders and department coordinators) can contact you and ask for your help to accomplish something needed.

=== Getting Started ===
In the [https://magazine.joomla.org/all-issues/october-2021/help4joomla-needs-you Help4Joomla article (October 2021 Joomla Community Magazine)] for more information on the Help4Joomla concept.

This continued on from the [https://magazine.joomla.org/all-issues/september-2021/can-you-give-some-time4joomla Time4Joomla article (September 2021 JCM)] that outlines a number of ways you can get involved with self-driven and self-paced contributions to Joomla.

=== Adding where you can help ===
Simply [https://docs.joomla.org/index.php?title=Special:UserLogin&returnto=Help4Joomla log in] and add yourself, your native language and other languages you can communicate in and whether you are active at the moment.

Do not add other people. It's essential that this is a system driven by peoples desire to help out and they give their contact details.

== Help4Joomla Volunteers ==
{| class="wikitable sortable"
|-
! Name !! Task !! Native Language !! Other Languages !! Available to do the task !! Contact details
|-
| Phil Walton|| Proofreading and improving the readability of documents written by none English speakers || English || None || Available || [https://volunteers.joomla.org/joomlers/1702-philip-walton Joomler Profile]
|-
| Patrick Jackson|| Technical writing; Proofreading; SEO; Analytics; Case Studies || English || None || Available || [https://volunteers.joomla.org/joomlers/213-patrick-jackson Joomler Profile]
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|}

''Note that this is an interim solution for recording volunteers looking to Help4Joomla''

<noinclude>
[[Category:Volunteer Engagement{{#translation:}}]]
</noinclude>

Help4Joomla

2021-10-28T04:10:55Z

Partic: Updated article link following publication of magazine; Added my record;

==What is Help4Joomla?==
Help4Joomla is a list of people, and tasks they can do. If you add yourself to the list then others can contact you and ask for your help to accomplish something needed. See this [https://magazine.joomla.org/all-issues/october-2021/help4joomla-needs-you October 2021 Joomla Community Magazine article] for more information on the Help4Joomla concept.

Simply [https://docs.joomla.org/index.php?title=Special:UserLogin&returnto=Help4Joomla log in] and add yourself, your native language and other languages you can communicate in and whether you are active at the moment.

Do not add other people. It's essential that this is a system driven by peoples desire to help out and they give their contact details.

{| class="wikitable sortable"
|-
! Name !! Task !! Native Language !! Other Languages !! Available to do the task !! Contact details
|-
| Phil Walton|| Proofreading and improving the readability of documents written by none English speakers || English || None || Available || [https://volunteers.joomla.org/joomlers/1702-philip-walton Joomler Profile]
|-
| Patrick Jackson|| Technical writing; Proofreading; SEO; Analytics; Case Studies || English || None || Available || [https://volunteers.joomla.org/joomlers/213-patrick-jackson Joomler Profile]
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|}

''Note that this is an interim solution for recording volunteers looking to Help4Joomla''

<noinclude>
[[Category:Volunteer Engagement{{#translation:}}]]
</noinclude>

Help4Joomla

2021-10-18T12:06:26Z

Partic:

==What is Help4Joomla?==
Help4Joomla is a list of people, and tasks they can do. If you add yourself to the list then others can contact you and ask for your help to accomplish something needed. See this [https://magazine.joomla.org October 2021 Joomla Community Magazine article] for more information on the Help4Joomla concept.

Simply [https://docs.joomla.org/index.php?title=Special:UserLogin&returnto=Help4Joomla log in] and add yourself, your native language and other languages you can communicate in and whether you are active at the moment.

Do not add other people. It's essential that this is a system driven by peoples desire to help out and they give their contact details.

{| class="wikitable sortable"
|-
! Name !! Task !! Native Language !! Other Languages !! Available to do the task !! Contact details
|-
| Phil Walton|| Proofreading and improving the readability of documents written by none English speakers || English || None || Available || https://volunteers.joomla.org/joomlers/1702-philip-walton
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example
|}

''Note that this is an interim solution for recording volunteers looking to Help4Joomla''

J4.x:Joomla Core APIs

2021-09-22T02:38:08Z

Partic: Added Additional Resources

<noinclude><languages /></noinclude>
<noinclude>{{Joomla version|version=4.0}}</noinclude>
<translate> This page lists the endpoints available in Joomla by example of curl commands.</translate>

<translate> Every URL requires authentication unless designated a public URL. For security in Joomla 4.0.0 we plan to make the default Api Application require a Super User account (as the API Application is brand new), this may get relaxed as the API stabilizes and is well tested in the community. If you are using the basic authentication plugin (currently the only shipped plugin as of Joomla 4 alpha 10) it requires the addition to the curl commands below using --user user_name:password</translate>

<translate> Every URL needs to be prepended with the Joomla host before the path (e.g. instead of <tt>/api/index.php/v1/article</tt> you need <tt><nowiki>http://example.com/api/index.php/v1/article</nowiki></tt>)</translate>

<translate> Any names of properties in curly brackets ({}) indicate the property is a variable that should be substituted.</translate>

<translate> Unless otherwise noted these APIs were introduced in Joomla 4. For more information on the Joomla API Specification (as opposed to this list of URLs and options) please visit the [[S:MyLanguage/Joomla Api Specification|Joomla Api Specification]].</translate>

<translate>

Where end points require the value of {app} the variable currently takes two values, site (front end), or administrator {back end)
</translate>

==<translate>Useful Resources</translate>==
<translate>A number of complimentary resources have been created to introduce Joomla Web Services and assist you with learning how to implement Web Services on your project.</translate>
* [https://github.com/alexandreelise/j4x-api-collection <translate>Postman collection of Joomla Web Services API calls by Alexandre Elise</translate>]
* [https://www.youtube.com/watch?v=lT9qodsvfZg <translate>Youtube: Joomla 4 tutorial: Using the Web Services API with Eoin Oliver</translate>]
* [https://magazine.joomla.org/all-issues/august-2020/joomla-web-services-api-101-tokens,-testing-and-a-taste-test <translate>Joomla Community Magazine: Joomla Web Services API 101 by Patrick Jackson</translate>]

<translate>
== Banners == 
</translate>
<translate>
=== Banners === 
</translate>
<translate>
==== Get List of Banners ==== 
</translate>
curl -X GET /api/index.php/v1/banners
<translate>
==== Get Single Banner ==== 
</translate>
curl -X GET /api/index.php/v1/banners/{banner_id}
<translate>
==== Delete Banner ==== 
</translate>
curl -X DELETE /api/index.php/v1/banners/{banner_id}
<translate>
==== Create Banner ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/banners -d
<source lang="javascript">
{
"catid": 3,
"clicks": 0,
"custombannercode": "",
"description": "Text",
"metakey": "",
"name": "Name",
"params": {
"alt": "",
"height": "",
"imageurl": "",
"width": ""
}
}
</source>

<translate>
==== Update Banner ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/banners/{banner_id} -d
<source lang="javascript">
{
"alias": "name",
"catid": 3,
"description": "New Text",
"name": "New Name"
}
</source>

<translate>
=== Clients === 
</translate>
<translate>
==== Get List of Clients ==== 
</translate>
curl -X GET /api/index.php/v1/banners/clients

<translate>
==== Get Single Client ==== 
</translate>
curl -X GET /api/index.php/v1/banners/clients/{client_id}

<translate>
==== Delete Client ==== 
</translate>
curl -X DELETE /api/index.php/v1/banners/clients/{client_id}

<translate>
==== Create Client ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/banners/clients -d
<source lang="javascript">
{
"contact": "Name",
"email": "email@mail.com",
"extrainfo": "",
"metakey": "",
"name": "Clients",
"state": 1
}
</source>

<translate>
==== Update Client ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/banners/clients/{client_id} -d
<source lang="javascript">
{
"contact": "new Name",
"email": "newemail@mail.com",
"name": "Clients"
}
</source>

<translate>
=== Categories === 
</translate>
<translate>
==== Get List of Categories ==== 
</translate>
curl -X GET /api/index.php/v1/banners/categories

<translate>
==== Get Single Category ==== 
</translate>
curl -X GET /api/index.php/v1/banners/categories/{category_id}

<translate>
==== Delete Category ==== 
</translate>
curl -X DELETE /api/index.php/v1/banners/categories/{category_id}

<translate>
==== Create Category ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/banners/categories -d
<source lang="javascript">
{
"access": 1,
"alias": "cat",
"extension": "com_banners",
"language": "*",
"note": "",
"parent_id": 1,
"published": 1,
"title": "Title"
}
</source>

<translate>

==== Update Category ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/banners/categories/{category_id} -d
<source lang="javascript">
{
"alias": "cat",
"note": "Some Text",
"parent_id": 1,
"title": "New Title"
}
</source>

<translate>
=== Content History === 
</translate>
<translate>
==== Get List of Content Histories ==== 
</translate>
curl -X GET /api/index.php/v1/banners/contenthistory/{banner_id}

<translate>
==== Toggle Keep Content History ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/banners/contenthistory/keep/{contenthistory_id}

<translate>
==== Delete Content History ==== 
</translate>
curl -X DELETE /api/index.php/v1/banners/contenthistory/{contenthistory_id}

<translate>
== Config == 
</translate>
<translate>
=== Application === 
</translate>
<translate>
==== Get List of Application Configs ==== 
</translate>
curl -X GET /api/index.php/v1/config/application

<translate>
==== Update Application Config ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/config/application -d
<source lang="javascript">
{
"debug": true,
"sitename": "123"
}
</source>

<translate>
=== Component === 
</translate>
<translate>
==== Get List of Component Configs ==== 
</translate>
curl -X GET /api/index.php/v1/config/{component_name}

Example “component_name” is “com_content”.

<translate>
==== Update Application Config ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/config/application -d
<source lang="javascript">
{
"link_titles": 1
}
</source>

<translate>
== Contact == 
</translate>
<translate>
=== Contact === 
</translate>
<translate>
==== Get List of Contacts ==== 
</translate>
curl -X GET /api/index.php/v1/contact

<translate>
==== Get Single Contact ==== 
</translate>
curl -X GET /api/index.php/v1/contact/{contact_id}

<translate>
==== Delete Contact ==== 
</translate>
curl -X DELETE /api/index.php/v1/contact/{contact_id}

<translate>
==== Create Contact ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/contact -d
<source lang="javascript">
{
"alias": "contact",
"catid": 4,
"language": "*",
"name": "Contact"
}
</source>

<translate>
==== Update Contact ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/contact/{contact_id} -d
<source lang="javascript">
{
"alias": "contact",
"catid": 4,
"name": "New Contact"
}
</source>

<translate>
==== Submit Contact Form ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/contact/form/{contact_id} -d
<source lang="javascript">
{
"contact_email": "email@mail.com",
"contact_message": "some text",
"contact_name": "name",
"contact_subject": "subject"
}
</source>

<translate>
=== Categories === 
</translate>
#<translate> Route Contact Categories is</translate>: "v1/contact/categories"
#<translate> Working with it is similar to [[S:MyLanguage/#Categories|Banners Categories]].</translate>

<translate>
=== Fields Contact === 
</translate>
<translate>
==== Get List of Fields Contact ==== 
</translate>
curl -X GET /api/index.php/v1/fields/contact/contact

<translate>
==== Get Single Field Contact ==== 
</translate>
curl -X GET /api/index.php/v1/fields/contact/contact/{field_id}

<translate>
==== Delete Field Contact ==== 
</translate>
curl -X DELETE /api/index.php/v1/fields/contact/contact/{field_id}

<translate>
==== Create Field Contact ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/fields/contact/contact -d
<source lang="javascript">
{
"access": 1,
"context": "com_contact.contact",
"default_value": "",
"description": "",
"group_id": 0,
"label": "contact field",
"language": "*",
"name": "contact-field",
"note": "",
"params": {
"class": "",
"display": "2",
"display_readonly": "2",
"hint": "",
"label_class": "",
"label_render_class": "",
"layout": "",
"prefix": "",
"render_class": "",
"show_on": "",
"showlabel": "1",
"suffix": ""
},
"required": 0,
"state": 1,
"title": "contact field",
"type": "text"
}
</source>

<translate>
==== Update Field Contact ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/fields/contact/contact/{field_id} -d
<source lang="javascript">
{
"title": "new contact field",
"name": "contact-field",
"label": "contact field",
"default_value": "",
"type": "text",
"note": "",
"description": "Some New Text"
}
</source>

<translate>
=== Fields Contact Mail === 
</translate>
#<translate> Route Fields Contact Mail is:</translate> "v1/fields/contact/mail"
#<translate> Working with it is similar to [[S:MyLanguage/#Fields_Contact|Fields Contact]].</translate>

<translate>
=== Fields Contact Categories === 
</translate>
#<translate> Route Fields Contact Categories is:</translate> "v1/fields/contact/categories"
#<translate> Working with it is similar to [[S:MyLanguage/#Fields_Contact|Fields Contact]].</translate>

<translate>
=== Groups Fields Contact === 
</translate>
<translate>
==== Get List of Groups Fields Contact ==== 
</translate>
curl -X GET /api/index.php/v1/fields/groups/contact/contact

<translate>
==== Get Single Group Fields Contact ==== 
</translate>
curl -X GET /api/index.php/v1/fields/groups/contact/contact/{group_id}

<translate>
==== Delete Group Fields Contact ==== 
</translate>
curl -X DELETE /api/index.php/v1/fields/groups/contact/contact/{group_id}

<translate>
==== Create Group Fields Contact ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/fields/groups/contact/contact -d
<source lang="javascript">
{
"access": 1,
"context": "com_contact.contact",
"default_value": "",
"description": "",
"group_id": 0,
"label": "contact field",
"language": "*",
"name": "contact-field3",
"note": "",
"params": {
"class": "",
"display": "2",
"display_readonly": "2",
"hint": "",
"label_class": "",
"label_render_class": "",
"layout": "",
"prefix": "",
"render_class": "",
"show_on": "",
"showlabel": "1",
"suffix": ""
},
"required": 0,
"state": 1,
"title": "contact field",
"type": "text"
}
</source>
<translate>
==== Update Group Fields Contact ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/fields/groups/contact/contact/{group_id} -d
<source lang="javascript">
{
"title": "new contact group",
"note": "",
"description": "new description"
}
</source>

<translate>
=== Group Fields Contact Mail === 
</translate>
<translate> #Route Group Fields Contact Mail is:</translate> "v1/fields/groups/contact/mail"
<translate> #Working with it is similar to [[S:MyLanguage/#Groups_Fields_Contact|Group Fields Contact]].</translate>

<translate>
=== Group Fields Contact Categories=== 
</translate>
<translate> #Route Group Fields Contact Categories is:</translate> "v1/fields/groups/contact/categories"
<translate> #Working with it is similar to [[S:MyLanguage/#Groups_Fields_Contact|Group Fields Contact]].</translate>

<translate>
=== Content History === 
</translate>
<translate> #Route Content History is:</translate> "v1/contact/contenthistory"
<translate> #Working with it is similar to [[S:MyLanguage/#Content_History|Banners Content History]].</translate>

<translate>
== Content == 
</translate>
<translate>
=== Articles === 
</translate>
<translate>
==== Get List of Articles ==== 
</translate>
curl -X GET /api/index.php/v1/content/articles

<translate>

==== Get Single Article ==== 
</translate>
curl -X GET /api/index.php/v1/content/article/{article_id}

<translate>
==== Delete Article ==== 
</translate>
curl -X DELETE /api/index.php/v1/content/article/{article_id}

<translate>
==== Create Article ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/content/article -d
<source lang="javascript">
{
"alias": "my-article",
"articletext": "My text",
"catid": 64,
"language": "*",
"metadesc": "",
"metakey": "",
"title": "Here's an article"
}
</source>

<translate> Currently the options mentioned here are required properties. However the intention is currently to make AT LEAST metakey and metadesc optional in the API.</translate>

<translate>
==== Update Article ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/content/article/{article_id} -d
<source lang="javascript">
{
"catid": 64,
"title": "Updated article"
}
</source>

<translate>
=== Categories === 
</translate>
#Route Content Categories is: "v1/content/categories"
#Working with it is similar to [[S:MyLanguage/#Categories|Banners Categories]], note if workflows is enabled then specifying a workflow is required (similarly to the UI)

<translate>

=== Fields Articles === 
</translate>
<translate> #Route Fields Articles is:</translate> "v1/fields/content/articles"
<translate> #Working with it is similar to [[S:MyLanguage/#Fields_Contact|Fields Contact]].</translate>

<translate>
=== Groups Fields Articles === 
</translate>
<translate> #Route Groups Fields Articles is:</translate> "v1/fields/groups/content/articles"
<translate> #Working with it is similar to [[S:MyLanguage/#Groups_Fields_Contact|Groups Fields Contact]].</translate>

<translate>
=== Fields Categories === 
</translate>
<translate> #Route Fields Categories is:</translate> "v1/fields/groups/content/categories"
<translate> #Working with it is similar to [[S:MyLanguage/#Fields_Contact|Fields Contact]].</translate>

<translate>
=== Content History === 
</translate>
<translate> #Route Content History is:</translate> "v1/content/article/contenthistory"
<translate> #Working with it is similar to [[S:MyLanguage/#Content_History|Banners Content History]].</translate>

<translate>
== Languages == 
</translate>
<translate>
=== Languages === 
</translate>
<translate>
==== Get List of Languages ==== 
</translate>
curl -X GET /api/index.php/v1/languages

<translate>
==== Install Language ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/languages -d
<source lang="javascript">
{
"package": "pkg_fr-FR"
}
</source>

<translate>
=== Content Languages === 
</translate>
<translate>
==== Get List of Content Languages ==== 
</translate>
curl -X GET /api/index.php/v1/languages/content

<translate>
==== Get Single Content Language ==== 
</translate>
curl -X GET /api/index.php/v1/v1/languages/content/{language_id}

<translate>
==== Delete Content Language ==== 
</translate>
curl -X DELETE /api/index.php/v1/languages/content/{language_id}

<translate>
==== Create Content Language ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/languages/content -d
<source lang="javascript">
{
"access": 1,
"description": "",
"image": "fr_FR",
"lang_code": "fr-FR",
"metadesc": "",
"metakey": "",
"ordering": 1,
"published": 0,
"sef": "fk",
"sitename": "",
"title": "French (FR)",
"title_native": "Français (France)"
}
</source>

<translate>
==== Update Content Language ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/languages/content/{language_id} -d
<source lang="javascript">
{
"description": "",
"lang_code": "en-GB",
"metadesc": "",
"metakey": "",
"sitename": "",
"title": "English (en-GB)",
"title_native": "English (United Kingdom)"
}
</source>

<translate>
=== Overrides Languages === 
</translate>
<translate>
==== Get List of Overrides Languages Constants ==== 
</translate>
curl -X GET /api/index.php/v1/languages/overrides/{app}/{lang_code}

<translate>
==== Get Single Override Language Constant ==== 
</translate>
curl -X GET /api/index.php/v1/languages/overrides/{app}/{lang_code}/{constant_id}

<translate>
==== Delete Content Language ==== 
</translate>
curl -X DELETE /api/index.php/v1/languages/overrides/{app}/{lang_code}/{constant_id}

<translate>
==== Create Content Language ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/languages/overrides/{app}/{lang_code} -d
<source lang="javascript">
{
"key":"new_key",
"override": "text"
}
</source>

<translate>
==== Update Content Language ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/languages/overrides/{app}/{lang_code}/{constant_id} -d
<source lang="javascript">
{
"key":"new_key",
"override": "new text"
}
</source>

var app - enum {"site", "administrator"}

var lang_code - string Example: “fr-FR“, “en-GB“ you can get lang_code from v1/languages/content

<translate>
==== Search Override Constant ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/languages/overrides/search -d
<source lang="javascript">
{
"searchstring": "JLIB_APPLICATION_ERROR_SAVE_FAILED",
"searchtype": "constant"
}
</source>

<translate> var searchtype - enum {“constant”, “value”}. “constant” search by constant name, “value” - search by constant value</translate>

<translate>
==== Refresh Override Search Cache ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/languages/overrides/search/cache/refresh

<translate>
== Menus == 
</translate>
<translate>
=== Menus === 
</translate>
<translate>
==== Get List of Menus ==== 
</translate>
curl -X GET /api/index.php/v1/menus/{app}

<translate>
==== Get Single Menu ==== 
</translate>
curl -X GET /api/index.php/v1/menus/{app}/{menu_id}

<translate>
==== Delete Menu ==== 
</translate>
curl -X DELETE /api/index.php/v1/menus/{app}/{menu_id}

<translate>
==== Create Menu ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/menus/{app} -d
<source lang="javascript">
{
"client_id": 0,
"description": "The menu for the site",
"menutype": "menu",
"title": "Menu"
}
</source>

<translate>
==== Update Menu ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/menus/{app}/{menu_id} -d
<source lang="javascript">
{
"menutype": "menu",
"title": "New Menu"
}
</source>

<translate>
=== Menus Items === 
</translate>
<translate>
==== Get List of Menus Items Types ==== 
</translate>
curl -X GET /api/index.php/v1/menus/{app}/items/types

<translate>
==== Get List of Menus Items ==== 
</translate>
curl -X GET /api/index.php/v1/menus/{app}/items

<translate>
==== Get Single Menu Item ==== 
</translate>
curl -X GET /api/index.php/v1/menus/{app}/items/{menu_item_id}

<translate>
==== Delete Menu Item ==== 
</translate>
curl -X DELETE /api/index.php/v1/menus/{app}/items/{menu_item_id}

<translate>
==== Create Menu Item ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/menus/{app}/items -d
<source lang="javascript">
{
"access": "1",
"alias": "",
"associations": {
"en-GB": "",
"fr-FR": ""
},
"browserNav": "0",
"component_id": "20",
"home": "0",
"language": "*",
"link": "index.php?option=com_content&view=form&layout=edit",
"menutype": "mainmenu",
"note": "",
"params": {
"cancel_redirect_menuitem": "",
"catid": "",
"custom_cancel_redirect": "0",
"enable_category": "0",
"menu-anchor_css": "",
"menu-anchor_title": "",
"menu-meta_description": "",
"menu-meta_keywords": "",
"menu_image": "",
"menu_image_css": "",
"menu_show": "1",
"menu_text": "1",
"page_heading": "",
"page_title": "",
"pageclass_sfx": "",
"redirect_menuitem": "",
"robots": "",
"show_page_heading": ""
},
"parent_id": "1",
"publish_down": "",
"publish_up": "",
"published": "1",
"template_style_id": "0",
"title": "title",
"toggle_modules_assigned": "1",
"toggle_modules_published": "1",
"type": "component"
}
</source>

<translate> Example for "Create Article Page"</translate>

<translate>
==== Update Menu Item ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/menus/{app}/items/{menu_item_id} -d
<source lang="javascript">
{
"component_id": "20",
"language": "*",
"link": "index.php?option=com_content&view=form&layout=edit",
"menutype": "mainmenu",
"note": "",
"title": "new title",
"type": "component"
}
</source>

<translate> Example for "Create Article Page"</translate>

<translate>
== Messages == 
</translate>
<translate>
=== Messages === 
</translate>
<translate>
==== Get List of Messages ==== 
</translate>
curl -X GET /api/index.php/v1/messages

<translate>
==== Get Single Message ==== 
</translate>
curl -X GET /api/index.php/v1/messages/{message_id}

<translate>
==== Delete Message ==== 
</translate>
curl -X DELETE /api/index.php/v1/messages/{message_id}

<translate>
==== Create Message ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/messages -d
<source lang="javascript">
{
"message": "<p>text</p>",
"state": 0,
"subject": "text",
"user_id_from": 773,
"user_id_to": 772
}
</source>

<translate>
==== Update Message ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/messages/{message_id} -d
<source lang="javascript">
{
"message": "<p>new text</p>",
"subject": "new text",
"user_id_from": 773,
"user_id_to": 772
}
</source>

<translate>
== Modules == 
</translate>
<translate>
=== Modules === 
</translate>
<translate>
==== Get List of Modules Types ==== 
</translate>
curl -X GET /api/index.php/v1/modules/types/{app}

<translate>
==== Get List of Modules ==== 
</translate>
curl -X GET /api/index.php/v1/modules/{app}

<translate>
==== Get Single Module ==== 
</translate>
curl -X GET /api/index.php/v1/modules/{app}/{module_id}

<translate>
==== Delete Module ==== 
</translate>
curl -X DELETE /api/index.php/v1/modules/{app}/{module_id}

<translate>
==== Create Module ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/modules/{app} -d
<source lang="javascript">
{
"access": "1",
"assigned": [
"101",
"105"
],
"assignment": "0",
"client_id": "0",
"language": "*",
"module": "mod_articles_archive",
"note": "",
"ordering": "1",
"params": {
"bootstrap_size": "0",
"cache": "1",
"cache_time": "900",
"cachemode": "static",
"count": "10",
"header_class": "",
"header_tag": "h3",
"layout": "_:default",
"module_tag": "div",
"moduleclass_sfx": "",
"style": "0"
},
"position": "",
"publish_down": "",
"publish_up": "",
"published": "1",
"showtitle": "1",
"title": "Title"
}
</source>

<translate> Example for "Articles - Archived"</translate>

<translate>
==== Update Module ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/modules/{app}/{module_id} -d
<source lang="javascript">
{
"access": "1",
"client_id": "0",
"language": "*",
"module": "mod_articles_archive",
"note": "",
"ordering": "1",
"title": "New Title"
}
</source>

<noinclude>Example for "Articles - Archived"</noinclude>

<translate>
== Newsfeeds == 
</translate>
<translate>
=== Feeds === 
</translate>
<translate>
==== Get List of Feeds ==== 
</translate>
curl -X GET /api/index.php/v1/newsfeeds/feeds

<translate>
==== Get Single Feed ==== 
</translate>
curl -X GET /api/index.php/v1/newsfeeds/feeds/{feed_id}

<translate>
==== Delete Feed ==== 
</translate>
curl -X DELETE /api/index.php/v1/newsfeeds/feeds/{feed_id}

<translate>
==== Create Feed ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/newsfeeds/feeds -d
<source lang="javascript">
{
"access": 1,
"alias": "alias",
"catid": 5,
"description": "",
"images": {
"float_first": "",
"float_second": "",
"image_first": "",
"image_first_alt": "",
"image_first_caption": "",
"image_second": "",
"image_second_alt": "",
"image_second_caption": ""
},
"language": "*",
"link": "http://samoylov/joomla/gsoc19_webservices/index.php",
"metadata": {
"hits": "",
"rights": "",
"robots": "",
"tags": {
"tags": "",
"typeAlias": null
}
},
"metadesc": "",
"metakey": "",
"name": "Name",
"ordering": 1,
"params": {
"feed_character_count": "",
"feed_display_order": "",
"newsfeed_layout": "",
"show_feed_description": "",
"show_feed_image": "",
"show_item_description": ""
},
"published": 1
}
</source>

<translate>
==== Update Feed ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/newsfeeds/feeds/{feed_id} -d
<source lang="javascript">
{
"access": 1,
"alias": "test2",
"catid": 5,
"description": "",
"link": "http://samoylov/joomla/gsoc19_webservices/index.php",
"metadesc": "",
"metakey": "",
"name": "Test"
}
</source>

<translate>
=== Categories === 
</translate>
<translate> #Route Newsfeeds Categories is:</translate> "v1/newsfeeds/categories"
<translate> #Working with it is similar to [[#Categories|Banners Categories]].</translate>

<translate>
== Privacy == 
</translate>
<translate>
=== Request === 
</translate>
<translate>
==== Get List of Requests ==== 
</translate>
curl -X GET /api/index.php/v1/privacy/request

<translate>
==== Get Single Request ==== 
</translate>
curl -X GET /api/index.php/v1/privacy/request/{request_id}

<translate>
==== Get Single Request Export Data ==== 
</translate>
curl -X GET /api/index.php/v1/privacy/request/export/{request_id}

<translate>
==== Create Request ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/privacy/request -d
<source lang="javascript">
{
"email":"somenewemail@com.ua",
"request_type":"export"
}
</source>

<translate>
=== Consent === 
</translate>
<translate>
==== Get List of Consents ==== 
</translate>
curl -X GET /api/index.php/v1/privacy/consent

<translate>
==== Get Single Consent ==== 
</translate>
curl -X GET /api/index.php/v1/privacy/consent/{consent_id}

<translate>
==== Delete Consent ==== 
</translate>
curl -X DELETE /api/index.php/v1/privacy/consent/{consent_id}

<translate>
== Redirect == 
</translate>
<translate>
=== Redirect === 
</translate>
<translate>
==== Get List of Redirects ==== 
</translate>
curl -X GET /api/index.php/v1/redirect

<translate>
==== Get Single Redirect ==== 
</translate>
curl -X GET /api/index.php/v1/redirect/{redirect_id}

<translate>
==== Delete Redirect ==== 
</translate>
curl -X DELETE /api/index.php/v1/redirect/{redirect_id}

<translate>
==== Create Redirect ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/redirect -d
<source lang="javascript">
{
"comment": "",
"header": 301,
"hits": 0,
"new_url": "/content/art/99",
"old_url": "/content/art/12",
"published": 1,
"referer": ""
}
</source>

<translate>
==== Update Redirect ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/redirect/{redirect_id} -d
<source lang="javascript">
{
"new_url": "/content/art/4",
"old_url": "/content/art/132"
}
</source>

<translate>
== Tags == 
</translate>
<translate>
=== Tags === 
</translate>
<translate>
==== Get List of Tags ==== 
</translate>
curl -X GET /api/index.php/v1/tags

<translate>
==== Get Single Tag ==== 
</translate>
curl -X GET /api/index.php/v1/tags/{tag_id}

<translate>
==== Delete Tag ==== 
</translate>
curl -X DELETE /api/index.php/v1/tags/{tag_id}

<translate>
==== Create Tag ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/tags -d
<source lang="javascript">
{
"access": 1,
"access_title": "Public",
"alias": "test",
"description": "",
"language": "*",
"note": "",
"parent_id": 1,
"path": "test",
"published": 1,
"title": "test"
}
</source>

<translate>
==== Update Tag ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/tags/{tag_id} -d
<source lang="javascript">
{
"alias": "test",
"title": "new title"
}
</source>

<translate>
== Templates == 
</translate>
<translate>
=== Templates Styles === 
</translate>
<translate>
==== Get List of Templates Styles ==== 
</translate>
curl -X GET /api/index.php/v1/templates/styles/{app}

<translate>
==== Get Single Template Style ==== 
</translate>
curl -X GET /api/index.php/v1/templates/styles/{app}/{template_style_id}

<translate>
==== Delete Template Style ==== 
</translate>
curl -X DELETE /api/index.php/v1/templates/styles/{app}/{template_style_id}

<translate>
==== Create Template Style ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/templates/styles/{app} -d
<source lang="javascript">
{
"home": "0",
"params": {
"fluidContainer": "0",
"logoFile": "",
"sidebarLeftWidth": "3",
"sidebarRightWidth": "3"
},
"template": "cassiopeia",
"title": "cassiopeia - Some Text"
}
</source>

<translate>
==== Update Template Style ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/templates/styles/{app}/{template_style_id} -d
<source lang="javascript">
{
"template": "cassiopeia",
"title": "new cassiopeia - Default"
}
</source>

<translate>
== Users == 
</translate>
<translate>
=== Users === 
</translate>
<translate>
==== Get List of Users ==== 
</translate>
curl -X GET /api/index.php/v1/users

<translate>
==== Get Single User ==== 
</translate>
curl -X GET /api/index.php/v1/users/{user_id}

<translate>
==== Delete User ==== 
</translate>
curl -X DELETE /api/index.php/v1/users/{user_id}

<translate>
==== Create User ==== 
</translate>
curl -X POST -H "Content-Type: application/json" /api/index.php/v1/users -d
<source lang="javascript">
{
"block": "0",
"email": "test@mail.com",
"groups": [
"2"
],
"id": "0",
"lastResetTime": "",
"lastvisitDate": "",
"name": "nnn",
"params": {
"admin_language": "",
"admin_style": "",
"editor": "",
"helpsite": "",
"language": "",
"timezone": ""
},
"password": "qwertyqwerty123",
"password2": "qwertyqwerty123",
"registerDate": "",
"requireReset": "0",
"resetCount": "0",
"sendEmail": "0",
"username": "ad"
}
</source>

<translate>
==== Update User ==== 
</translate>
curl -X PATCH -H "Content-Type: application/json" /api/index.php/v1/users/{user_id} -d
<source lang="javascript">
{
"email": "new@mail.com",
"groups": [
"2"
],
"name": "name",
"username": "username"
}
</source>

<translate>
=== Fields Users === 
</translate>
<translate> #Route Fields Users is:</translate> "v1/fields/users"
<translate> #Working with it is similar to [[S:MyLanguage/J4.x:Joomla_Core_APIs#Fields_Contact|Fields Contact]].</translate>

<translate>

=== Groups Fields Users === 
</translate>
<translate> #Route Groups Fields Users is:</translate> "v1/fields/groups/users"
<translate> #Working with it is similar to [[S:MyLanguage/J4.x:Joomla_Core_APIs#Groups_Fields_Contact|Groups Fields Contact]].</translate>

<noinclude>
[[Category:Development{{#translation:}}]]
[[Category:Joomla!_4.x{{#translation:}}]]
[[Category:Joomla!_4.0{{#translation:}}]]
[[Category:Joomla! 4.x Web Services{{#translation:}}]]
[[Category:Needs review]]
</noinclude>

JDOC:Crowdin for Proofreaders

2021-09-13T01:22:10Z

Partic: /* Becoming a Proofreader */

{{underconstruction}}

<noinclude><languages /></noinclude>

{{RightTOC}}

== <translate> What is Crowdin?</translate> ==
<translate>[https://joomla.crowdin.com Crowdin] is a cloud-based solution that streamlines localization (L10N) management for software projects.</translate>

<translate>The Joomla CMS official language packs and many other aspects of the project are managed using Crowdin to facilitate managing L10N activities.</translate>

===<translate>Roles in Crowdin</translate>===
<translate>The translation process is broken into two parts:</translate>
* <translate>Crowdsourcing - Crowdsourcing is the area of Crowdin where anyone can submit translations for their local language.</translate>
* <translate>Proofreading - Proofreaders perform a range of tasks to check, correct, approve and manage the Crowdsourced translations so that the approved translations can be used in various parts of the project.</translate>

<translate>This document outlines various items Proofreaders need to follow and understand to approve crowdsourced translations so that they can be used by the various parts of the project, and in particular be included in language packs for Joomla!</translate>
<translate>For more information on the crowdsourcing translation process, see [[Crowdin|the introduction to Crowdin]].</translate>

===<translate>Becoming a Proofreader</translate>===
<translate>For every language being translated in Crowdin Joomla! needs to have a proofreader assigned so that the translations submitted for that language can be approved and then included for use in the project.</translate>

<translate>Joomla 4's core language pack has over 67,000 words in 12,000 strings that need to be translated and approved. The time requirement for new proofreaders is significant at first as initially every string needs to be checked and approved. Once proofreaders have their language packs at 100%, the time commitment reduces significantly, with the project typically only adding a handful of strings to stable versions over time.</translate>

<translate>The project prefers ongoing commitment for involvement from Proofreaders. Proofreaders become Contributors on the various [https://volunteers.joomla.org/teams/joomla-translation-program-team#subteams sub teams of the Joomla Translation Program Team].</translate>

<translate>For more information on participating in the Joomla Translation Program join the [https://volunteers.joomla.org/teams/joomla-translation-program-team Joomla Translation Program Team] or find out more information on JDocs [https://docs.joomla.org/S:Mylanguage/Joomla_Translation_Program Joomla Translation Program] page.</translate>

==<translate>Proofreading Processes</translate>==
''Roadmap of items to be constructed in this section''
* Using the Proofreading interface on Crowdin
* Preparing a Joomla Language Pack
* Approving translation suggestions after a string has been previously approved.

==<translate>Proofreading Troubleshooting</translate>==
''Roadmap of items to be constructed in this section''
* Resolving comments
* Github Issues raised about language packs

JDOC:Crowdin for Proofreaders

2021-09-13T01:20:06Z

Partic:

{{underconstruction}}

<noinclude><languages /></noinclude>

{{RightTOC}}

== <translate> What is Crowdin?</translate> ==
<translate>[https://joomla.crowdin.com Crowdin] is a cloud-based solution that streamlines localization (L10N) management for software projects.</translate>

<translate>The Joomla CMS official language packs and many other aspects of the project are managed using Crowdin to facilitate managing L10N activities.</translate>

===<translate>Roles in Crowdin</translate>===
<translate>The translation process is broken into two parts:</translate>
* <translate>Crowdsourcing - Crowdsourcing is the area of Crowdin where anyone can submit translations for their local language.</translate>
* <translate>Proofreading - Proofreaders perform a range of tasks to check, correct, approve and manage the Crowdsourced translations so that the approved translations can be used in various parts of the project.</translate>

<translate>This document outlines various items Proofreaders need to follow and understand to approve crowdsourced translations so that they can be used by the various parts of the project, and in particular be included in language packs for Joomla!</translate>
<translate>For more information on the crowdsourcing translation process, see [[Crowdin|the introduction to Crowdin]].</translate>

===<translate>Becoming a Proofreader</translate>===
<translate>For every language being translated in Crowdin Joomla! needs to have a proofreader assigned so that the translations submitted for that language can be approved and then included for use in the project.</translate>
<translate>Joomla 4's core language pack has over 67,000 words in 12,000 strings that need to be translated and approved. The time requirement for new proofreaders is significant at first as initially every string needs to be checked and approved. Once proofreaders have their language packs at 100%, the time commitment reduces significantly, with the project typically only adding a handful of strings to stable versions over time.</translate>
<translate>The project prefers ongoing commitment for involvement from Proofreaders. Proofreaders become Contributors on the various [https://volunteers.joomla.org/teams/joomla-translation-program-team#subteams sub teams of the Joomla Translation Program Team].</translate>
<translate>For more information on participating in the Joomla Translation Program join the [https://volunteers.joomla.org/teams/joomla-translation-program-team Joomla Translation Program Team] or find out more information on JDocs [https://docs.joomla.org/S:Mylanguage/Joomla_Translation_Program Joomla Translation Program] page.</translate>

==<translate>Proofreading Processes</translate>==
''Roadmap of items to be constructed in this section''
* Using the Proofreading interface on Crowdin
* Preparing a Joomla Language Pack
* Approving translation suggestions after a string has been previously approved.

==<translate>Proofreading Troubleshooting</translate>==
''Roadmap of items to be constructed in this section''
* Resolving comments
* Github Issues raised about language packs

JDOC:Crowdin for Proofreaders

2021-09-13T01:19:40Z

Partic: Initial version of the page.

<noinclude><languages /></noinclude>

{{RightTOC}}

{{underconstruction}}

== <translate> What is Crowdin?</translate> ==
<translate>[https://joomla.crowdin.com Crowdin] is a cloud-based solution that streamlines localization (L10N) management for software projects.</translate>

<translate>The Joomla CMS official language packs and many other aspects of the project are managed using Crowdin to facilitate managing L10N activities.</translate>

===<translate>Roles in Crowdin</translate>===
<translate>The translation process is broken into two parts:</translate>
* <translate>Crowdsourcing - Crowdsourcing is the area of Crowdin where anyone can submit translations for their local language.</translate>
* <translate>Proofreading - Proofreaders perform a range of tasks to check, correct, approve and manage the Crowdsourced translations so that the approved translations can be used in various parts of the project.</translate>

<translate>This document outlines various items Proofreaders need to follow and understand to approve crowdsourced translations so that they can be used by the various parts of the project, and in particular be included in language packs for Joomla!</translate>
<translate>For more information on the crowdsourcing translation process, see [[Crowdin|the introduction to Crowdin]].</translate>

===<translate>Becoming a Proofreader</translate>===
<translate>For every language being translated in Crowdin Joomla! needs to have a proofreader assigned so that the translations submitted for that language can be approved and then included for use in the project.</translate>
<translate>Joomla 4's core language pack has over 67,000 words in 12,000 strings that need to be translated and approved. The time requirement for new proofreaders is significant at first as initially every string needs to be checked and approved. Once proofreaders have their language packs at 100%, the time commitment reduces significantly, with the project typically only adding a handful of strings to stable versions over time.</translate>
<translate>The project prefers ongoing commitment for involvement from Proofreaders. Proofreaders become Contributors on the various [https://volunteers.joomla.org/teams/joomla-translation-program-team#subteams sub teams of the Joomla Translation Program Team].</translate>
<translate>For more information on participating in the Joomla Translation Program join the [https://volunteers.joomla.org/teams/joomla-translation-program-team Joomla Translation Program Team] or find out more information on JDocs [https://docs.joomla.org/S:Mylanguage/Joomla_Translation_Program Joomla Translation Program] page.</translate>

==<translate>Proofreading Processes</translate>==
''Roadmap of items to be constructed in this section''
* Using the Proofreading interface on Crowdin
* Preparing a Joomla Language Pack
* Approving translation suggestions after a string has been previously approved.

==<translate>Proofreading Troubleshooting</translate>==
''Roadmap of items to be constructed in this section''
* Resolving comments
* Github Issues raised about language packs

Crowdin

2021-09-13T00:29:32Z

Partic: Added Crowdin for Proofreaders page link

<noinclude><languages /></noinclude>

{{RightTOC}}

== <translate> What is Crowdin?</translate> ==
<translate> [https://joomla.crowdin.com Crowdin] is a cloud-based solution that streamlines localization (L10N) management for software projects.</translate>

<translate> The Joomla CMS official language packs and many other aspects of the project are managed using Crowdin to facilitate managing L10N activities.</translate>

==<translate> What can be translated on Crowdin?</translate>==
===<translate> Joomla! Official Translations</translate>===
<translate> There's a variety of content that needs to be translated and localised for use with Joomla. Joomla's using Crowdin Enterprise for managing localisations across the project. A number of leading extension developers are also using Crowdin as their localisation tool, and you can see those extensions also listed under Joomla's Crowdin project page as related projects.</translate>
<translate> * Joomla! CMS - Core Language packs for Joomla 4</translate>
<translate> * Joomla! Official Extensions - Extensions created by the Joomla! Project such as JEDChecker, Patch Tester, Language Pack component and Install From Web Extension</translate>
<translate> * Joomla! Official Website - Materials for the joomla.org suite of websites</translate>
<translate> * Joomla! Official Website Template - Language strings for the Joomla.org website template</translate>
<translate> * Joomla! Marketing Resources - Internationalising marketing resources to promote Joomla around the globe</translate>

===<translate> Translating Documentation</translate>===
<translate> Joomla Documentation doesn't use Crowdin for translation as it's built into the wiki. See the </translate>[[S:Mylanguage/JDOC:Page_Translation_Quickstart_Guide|<translate> Documentation Translation Quickstart guide</translate>]] <translate> for more information.</translate>

===<translate> 3rd Party Extension Translations</translate>===
<translate> A variety of 3rd party extension developers have also chosen Crowdin as their L10N solution. These are displayed on Joomla's Crowdin, but are managed by the individual developers.</translate>

==<translate> Getting Started</translate>==
===<translate> Create an account</translate>===
<translate> To start using Crowdin, create an account at https://joomla.crowdin.com.</translate> <translate> If you're already using GitHub to contribute to the project, you can use your GitHub login (along with a few other OAuth options) to sign up to Crowdin.</translate>

<translate> Once you've created your account, [https://joomla.crowdin.com/ visit the Crowdin Project for Joomla] to contribute to Joomla 4 core translations, other translations for Joomla websites, Joomla marketing projects and other Joomla extensions.</translate>

''<translate> [https://crowdin.com/project/joomla-cms Joomla 3 translations] are also managed on Crowdin, but are outside Joomla's Crowdin Enterprise structure. The setup works the same in regards to contributing translations, however the proofreading and language pack process is different to the steps described for Joomla 4 in the next section.</translate>''

===<translate> Select a Project</translate>===
<translate> Once logged into joomla.crowdin.com you'll see the project dashboard, showing all of the projects that are available to translate. Click on a project to then see what the status of each localisation is for that project.</translate>
[[File:Languages-crowdinfeaturedprojects.png|1|<translate> Select a Featured Project to begin translating that project in your language</translate>]]

===<translate> Select a Language</translate>===
<translate> When you go into a project, you'll see all of the available languages ready for translation. To start translating, hover on the language and then click on the "Translate" button that appears.</translate>

<translate> The progress bars indicate two main aspects of the translation process:</translate>
* <translate> Blue lines indicate the percentage of strings for this project that have been translated for that language. Once translated, proofreaders then process the suggested translations and approve them - it's a double check in case something has been suggested by accident for that language. An example I've found as a proofreader has been that some translations have been suggested for the wrong language as the translator was not in the correct language when they started suggesting phrases. And there are always different opinions on how to translate a sentence.</translate>
* <translate> Green lines indicate that the proofreader has approved the suggested translations made by translators for that localisation. Once the proofreader approves the translations, the approved translations then move into the production phase, where the project's translation managers can then package up the translations for the project and create packages that can then be installed by users or implemented by Joomla's webmasters team on the various Joomla website properties.</translate>
[[File:Language List.png|<translate> Select your language from the list to begin translating.</translate>]]

===<translate> Start Translating</translate>===
<translate> When you click translate, you'll be taken to the Crowdsourcing language page.</translate>
[[File:Crowdsourcing Screen.png|<translate> Parts of the Crowdsourcing screen you see when translating the page.</translate>]]

# <translate> On the left is a list of all the strings from the language files for the project that need translating. You can filter the list for various parameters, but by default the list will show you all of the strings available, with the untranslated strings at the top of the list (indicated by the red icon before them. Once translated, the icon is green).</translate>
# <translate> Clicking on a string you will see it load in the Source String box. This is the full text that you need to translate. You will see at times various highlighted items, like the green highlighted %s in the screenshot below. When you see some of the source string highlighted, these parts of the string do not need to be translated as they perform a system function that will do a replacement in the code with a variable as an example. The highlighted peace can also be HTML.</translate>
# <translate> In this area, type your translation for the source string.</translate>
# <translate> You may sometimes see suggestions for some strings in this section. If one is suitable, you can click on it to select it as a suitable translation for the source string.</translate>
# <translate> If you find there's an issue with a previously suggested translation, or have questions about the source string's context that you want to clarify, leave a comment in the comments sidebar on the page. Translation managers will then be notified and will either provide clarification or resolve the issue with the source string if required.</translate>
# <translate> Once you are happy with your translation for the source string, click Save and the system will mark that string as Done and move on to the next untranslated string.</translate>

<translate> Once you've finished translating all the available strings (or as many as you have time for in the session) you can exit the editor and return to the project by going to the menu at the top right of the screen and select "Quit Editor".</translate>

<translate> When you've begun providing crowdsourcing translations in each of Joomla's featured projects, you'll be notified when new strings are available to translate that have been added to the various projects.</translate>

==<translate> Proofreading</translate>==
<translate> Before translations appear in Joomla as part of an updated language pack, they need to be approved by that language's proofreader(s).</translate>
<translate> The role of a proofreader is to:</translate>
* <translate> Check that the crowdsourcing translations are correct for that language</translate>
* <translate> Resolve issues where multiple translations are suggested, choosing the most suitable translation</translate>
* <translate> For core language packs, package up the completed language pack to upload it to Joomla Language Download system.</translate>
<translate> To become a proofreader, join the [[#Joomla_Translation_Program_Team|Joomla Translation Program Team]].</translate>
<translate>For more information on the processes proofreaders need to complete with making language packs, please see </translate>[[S:Mylanguage/JDOC:Crowdin_for_Proofreaders|<translate>Crowdin for Proofreaders</translate>]].

==<translate> Joomla Translation Program Team </translate>==
<translate> The purpose of the [https://volunteers.joomla.org/teams/joomla-translation-program-team Joomla Translation Program] within the Programs Department is to coordinate and supervise the work of hundreds of volunteers globally who translate the Joomla CMS, Joomla’s official websites, documentation, and marketing materials into many different languages.</translate>
<translate> If you would like to do more than just translate your language's strings, join the team to assist with managing and recruiting translators and proofreaders.</translate>
<translate> For more information on participating in the Joomla Translation Program join the [https://volunteers.joomla.org/teams/joomla-translation-program-team Joomla Translation Program Team] or find out more information on JDocs [https://docs.joomla.org/S:Mylanguage/Joomla_Translation_Program Joomla Translation Program] page.</translate>

<translate> The [[Category:Languages|Languages Category]] also has a range of documentation articles that translators can contribute to.</translate>

==<translate> Further Information</translate>==
* <translate> Crowdin have a comprehensive [https://support.crowdin.com/ Knowledge Base] which new users would be well served to familiarize themselves with.</translate>
* <translate> Some of the basic concepts about using Crowdin to translate Joomla are explained in more detail in the [https://magazine.joomla.org/all-issues/august/joomla-s-l10n-hearted Joomla's L10N-hearted] article from August 2021 in [https://magazine.joomla.org Joomla Community Magazine].</translate>

[[Category:Languages{{#translation:}}]]
[[Category:Volunteer Engagement{{#translation:}}]]

Crowdin

2021-09-13T00:25:05Z

Partic:

<noinclude><languages /></noinclude>

{{RightTOC}}

== <translate> What is Crowdin?</translate> ==
<translate> [https://joomla.crowdin.com Crowdin] is a cloud-based solution that streamlines localization (L10N) management for software projects.</translate>

<translate> The Joomla CMS official language packs and many other aspects of the project are managed using Crowdin to facilitate managing L10N activities.</translate>

==<translate> What can be translated on Crowdin?</translate>==
===<translate> Joomla! Official Translations</translate>===
<translate> There's a variety of content that needs to be translated and localised for use with Joomla. Joomla's using Crowdin Enterprise for managing localisations across the project. A number of leading extension developers are also using Crowdin as their localisation tool, and you can see those extensions also listed under Joomla's Crowdin project page as related projects.</translate>
<translate> * Joomla! CMS - Core Language packs for Joomla 4</translate>
<translate> * Joomla! Official Extensions - Extensions created by the Joomla! Project such as JEDChecker, Patch Tester, Language Pack component and Install From Web Extension</translate>
<translate> * Joomla! Official Website - Materials for the joomla.org suite of websites</translate>
<translate> * Joomla! Official Website Template - Language strings for the Joomla.org website template</translate>
<translate> * Joomla! Marketing Resources - Internationalising marketing resources to promote Joomla around the globe</translate>

===<translate> Translating Documentation</translate>===
<translate> Joomla Documentation doesn't use Crowdin for translation as it's built into the wiki. See the </translate>[[S:Mylanguage/JDOC:Page_Translation_Quickstart_Guide|<translate> Documentation Translation Quickstart guide</translate>]] <translate> for more information.</translate>

===<translate> 3rd Party Extension Translations</translate>===
<translate> A variety of 3rd party extension developers have also chosen Crowdin as their L10N solution. These are displayed on Joomla's Crowdin, but are managed by the individual developers.</translate>

==<translate> Getting Started</translate>==
===<translate> Create an account</translate>===
<translate> To start using Crowdin, create an account at https://joomla.crowdin.com.</translate> <translate> If you're already using GitHub to contribute to the project, you can use your GitHub login (along with a few other OAuth options) to sign up to Crowdin.</translate>

<translate> Once you've created your account, [https://joomla.crowdin.com/ visit the Crowdin Project for Joomla] to contribute to Joomla 4 core translations, other translations for Joomla websites, Joomla marketing projects and other Joomla extensions.</translate>

''<translate> [https://crowdin.com/project/joomla-cms Joomla 3 translations] are also managed on Crowdin, but are outside Joomla's Crowdin Enterprise structure. The setup works the same in regards to contributing translations, however the proofreading and language pack process is different to the steps described for Joomla 4 in the next section.</translate>''

===<translate> Select a Project</translate>===
<translate> Once logged into joomla.crowdin.com you'll see the project dashboard, showing all of the projects that are available to translate. Click on a project to then see what the status of each localisation is for that project.</translate>
[[File:Languages-crowdinfeaturedprojects.png|1|<translate> Select a Featured Project to begin translating that project in your language</translate>]]

===<translate> Select a Language</translate>===
<translate> When you go into a project, you'll see all of the available languages ready for translation. To start translating, hover on the language and then click on the "Translate" button that appears.</translate>

<translate> The progress bars indicate two main aspects of the translation process:</translate>
* <translate> Blue lines indicate the percentage of strings for this project that have been translated for that language. Once translated, proofreaders then process the suggested translations and approve them - it's a double check in case something has been suggested by accident for that language. An example I've found as a proofreader has been that some translations have been suggested for the wrong language as the translator was not in the correct language when they started suggesting phrases. And there are always different opinions on how to translate a sentence.</translate>
* <translate> Green lines indicate that the proofreader has approved the suggested translations made by translators for that localisation. Once the proofreader approves the translations, the approved translations then move into the production phase, where the project's translation managers can then package up the translations for the project and create packages that can then be installed by users or implemented by Joomla's webmasters team on the various Joomla website properties.</translate>
[[File:Language List.png|<translate> Select your language from the list to begin translating.</translate>]]

===<translate> Start Translating</translate>===
<translate> When you click translate, you'll be taken to the Crowdsourcing language page.</translate>
[[File:Crowdsourcing Screen.png|<translate> Parts of the Crowdsourcing screen you see when translating the page.</translate>]]

# <translate> On the left is a list of all the strings from the language files for the project that need translating. You can filter the list for various parameters, but by default the list will show you all of the strings available, with the untranslated strings at the top of the list (indicated by the red icon before them. Once translated, the icon is green).</translate>
# <translate> Clicking on a string you will see it load in the Source String box. This is the full text that you need to translate. You will see at times various highlighted items, like the green highlighted %s in the screenshot below. When you see some of the source string highlighted, these parts of the string do not need to be translated as they perform a system function that will do a replacement in the code with a variable as an example. The highlighted peace can also be HTML.</translate>
# <translate> In this area, type your translation for the source string.</translate>
# <translate> You may sometimes see suggestions for some strings in this section. If one is suitable, you can click on it to select it as a suitable translation for the source string.</translate>
# <translate> If you find there's an issue with a previously suggested translation, or have questions about the source string's context that you want to clarify, leave a comment in the comments sidebar on the page. Translation managers will then be notified and will either provide clarification or resolve the issue with the source string if required.</translate>
# <translate> Once you are happy with your translation for the source string, click Save and the system will mark that string as Done and move on to the next untranslated string.</translate>

<translate> Once you've finished translating all the available strings (or as many as you have time for in the session) you can exit the editor and return to the project by going to the menu at the top right of the screen and select "Quit Editor".</translate>

<translate> When you've begun providing crowdsourcing translations in each of Joomla's featured projects, you'll be notified when new strings are available to translate that have been added to the various projects.</translate>

==<translate> Proofreading</translate>==
<translate> Before translations appear in Joomla as part of an updated language pack, they need to be approved by that language's proofreader(s).</translate>
<translate> The role of a proofreader is to:</translate>
* <translate> Check that the crowdsourcing translations are correct for that language</translate>
* <translate> Resolve issues where multiple translations are suggested, choosing the most suitable translation</translate>
* <translate> For core language packs, package up the completed language pack to upload it to Joomla Language Download system.</translate>
<translate> To become a proofreader, join the [[#Joomla_Translation_Program_Team|Joomla Translation Program Team]].</translate>

==<translate> Joomla Translation Program Team </translate>==
<translate> The purpose of the [https://volunteers.joomla.org/teams/joomla-translation-program-team Joomla Translation Program] within the Programs Department is to coordinate and supervise the work of hundreds of volunteers globally who translate the Joomla CMS, Joomla’s official websites, documentation, and marketing materials into many different languages.</translate>
<translate> If you would like to do more than just translate your language's strings, join the team to assist with managing and recruiting translators and proofreaders.</translate>
<translate> For more information on participating in the Joomla Translation Program join the [https://volunteers.joomla.org/teams/joomla-translation-program-team Joomla Translation Program Team] or find out more information on JDocs [https://docs.joomla.org/S:Mylanguage/Joomla_Translation_Program Joomla Translation Program] page.</translate>

<translate> The [[Category:Languages|Languages Category]] also has a range of documentation articles that translators can contribute to.</translate>

==<translate> Further Information</translate>==
* <translate> Crowdin have a comprehensive [https://support.crowdin.com/ Knowledge Base] which new users would be well served to familiarize themselves with.</translate>
* <translate> Some of the basic concepts about using Crowdin to translate Joomla are explained in more detail in the [https://magazine.joomla.org/all-issues/august/joomla-s-l10n-hearted Joomla's L10N-hearted] article from August 2021 in [https://magazine.joomla.org Joomla Community Magazine].</translate>

[[Category:Languages{{#translation:}}]]
[[Category:Volunteer Engagement{{#translation:}}]]

Crowdin

2021-09-12T05:42:59Z

Partic: Major update of steps for translating, added from work done creating https://magazine.joomla.org/all-issues/august/joomla-s-l10n-hearted for JCM

<noinclude><languages /></noinclude>

{{RightTOC}}

== <translate> What is Crowdin?</translate> ==
<translate> [https://joomla.crowdin.com Crowdin] is a cloud-based solution that streamlines localization (L10N) management for software projects.</translate>

<translate> The Joomla CMS official language packs and many other aspects of the project are managed using Crowdin to facilitate managing L10N activities.</translate>

==<translate>What can be translated on Crowdin?</translate>==
===<translate>Joomla! Official Translations</translate>===
<translate>There's a variety of content that needs to be translated and localised for use with Joomla. Joomla's using Crowdin Enterprise for managing localisations across the project. A number of leading extension developers are also using Crowdin as their localisation tool, and you can see those extensions also listed under Joomla's Crowdin project page as related projects.</translate>
<translate>* Joomla! CMS - Core Language packs for Joomla 4</translate>
<translate>* Joomla! Official Extensions - Extensions created by the Joomla! Project such as JEDChecker, Patch Tester, Language Pack component and Install From Web Extension</translate>
<translate>* Joomla! Official Website - Materials for the joomla.org suite of websites</translate>
<translate>* Joomla! Official Website Template - Language strings for the Joomla.org website template</translate>
<translate>* Joomla! Marketing Resources - Internationalising marketing resources to promote Joomla around the globe</translate>

===<translate> Translating Documentation</translate>===
<translate> Joomla Documentation doesn't use Crowdin for translation as it's built into the wiki. See the </translate>[[JDOC:Page_Translation_Quickstart_Guide|<translate> Documentation Translation Quickstart guide</translate>]] <translate> for more information.</translate>

===<translate>3rd Party Extension Translations</translate>===
<translate>A variety of 3rd party extension developers have also chosen Crowdin as their L10N solution. These are displayed on Joomla's crowdin, but are managed by the individual developers.</translate>

==<translate> Getting Started</translate>==
===<translate> Create an account</translate>===
<translate> To start using Crowdin, create an account at https://joomla.crowdin.com.</translate> <translate> If you're already using GitHub to contribute to the project, you can use your GitHub login (along with a few other OAuth options) to sign up to Crowdin.</translate>

<translate> Once you've created your account, [https://joomla.crowdin.com/ visit the Crowdin Project for Joomla] to contribute to Joomla 4 core translations, other translations for Joomla websites, Joomla marketing projects and other Joomla extensions.</translate>

''<translate> [https://crowdin.com/project/joomla-cms Joomla 3 translations] are also managed on Crowdin, but are outside Joomla's Crowdin Enterprise structure. The setup works the same in regards to contributing translations, however the proofreading and language pack process is different to the steps described for Joomla 4 in the next section.</translate>''

===<translate>Select a Project</translate>===
<translate>Once logged into joomla.crowdin.com you'll see the project dashboard, showing all of the projects that are available to translate. Click on a project to then see what the status of each localisation is for that project.</translate>
[[File:Languages-crowdinfeaturedprojects.png|1|<translate>Select a Featured Project to begin translating that project in your language</translate>]]

===<translate>Select a Language</translate>===
<translate>When you go into a project, you'll see all of the available languages ready for translation. To start translating, hover on the language and then click on the "Translate" button that appears.</translate>

<translate>The progress bars indicate two main aspects of the translation process:</translate>
* <translate>Blue lines indicate the percentage of strings for this project that have been translated for that language. Once translated, proofreaders then process the suggested translations and approve them - it's a double check in case something has been suggested by accident for that language. An example I've found as a proofreader has been that some translations have been suggested for the wrong language as the translator was not in the correct language when they started suggesting phrases.</translate>
* <translate>Green lines indicate that the proofreader has approved the suggested translations made by translators for that localisation. Once the proofreader approves the translations, the approved translations then move into the production phase, where the project's translation managers can then package up the translations for the project and create packages that can then be installed by users or implemented by Joomla's webmasters team on the various Joomla website properties.</translate>
[[File:Language List.png|<translate>Select your language from the list to begin translating.</translate>]]

===<translate>Start Translating</translate>===
<translate>When you click translate, you'll be taken to the Crowdsourcing language page.</translate>
[[File:Crowdsourcing Screen.png|<translate>Parts of the Crowdsourcing screen you see when translating the page.</translate>]]

# <translate>On the left is a list of all the strings from the language files for the project that need translating. You can filter the list for various parameters, but by default the list will show you all of the strings available, with the untranslated strings at the top of the list (indicated by the red icon before them. Once translated, the icon is green).</translate>
# <translate>Clicking on a string you will see it load in the Source String box. This is the full text that you need to translate. You will see at times various highlighted items, like the green highlighted %s in the screenshot below. When you see some of the source string highlighted, these parts of the string do not need to be translated as they perform a system function that will do a replacement in the code with a variable as an example.</translate>
# <translate>In this area, type your translation for the source string.</translate>
# <translate>You may sometimes see suggestions for some strings in this section. If one is suitable, you can click on it to select it as a suitable translation for the source string.</translate>
# <translate>If you find there's an issue with a previously suggested translation, or have questions about the source string's context that you want to clarify, leave a comment in the comments sidebar on the page. Translation managers will then be notified and will either provide clarification or resolve the issue with the source string if required.</translate>
# <translate>Once you are happy with your translation for the source string, click Save and the system will mark that string as Done and move on to the next untranslated string.</translate>

<translate>Once you've finished translating all the available strings (or as many as you have time for in the session) you can exit the editor and return to the project by going to the menu at the top right of the screen and select "Quit Editor".</translate>

<translate>When you've begun providing crowdsourcing translations in each of Joomla's featured projects, you'll be notified when new strings are available to translate that have been added to the various projects.</translate>

==<translate>Proofreading</translate>==
<translate>Before translations appear in Joomla as part of an updated language pack, they need to be approved by that language's proofreader(s).</translate>
<translate>The role of a proofreader is to:</translate>
* <translate>Check that the crowdsourcing translations are correct for that language</translate>
* <translate>Resolve issues where multiple translations are suggested, choosing the most suitable translation</translate>
* <translate>For core language packs, package up the completed language pack to upload it to Joomla Language Download system.</translate>
<translate>To become a proofreader, join the [[#Joomla_Translation_Program_Team|Joomla Translation Program Team]].</translate>

==<translate> Joomla Translation Program Team </translate>==
<translate>The purpose of the [https://volunteers.joomla.org/teams/joomla-translation-program-team Joomla Translation Program] within the Programs Department is to coordinate and supervise the work of hundreds of volunteers globally who translate the Joomla CMS, Joomla’s official websites, documentation, and marketing materials into many different languages.</translate>
<translate>If you would like to do more than just translate your language's strings, join the team to assist with managing and recruiting translators and proofreaders.</translate>
<translate> For more information on participating in the Joomla Translation Program join the [https://volunteers.joomla.org/teams/joomla-translation-program-team Joomla Translation Program Team] or find out more information on JDocs [https://docs.joomla.org/S:Mylanguage/Joomla_Translation_Program Joomla Translation Program] page.</translate>

<translate> The [[Category:Languages|Languages Category]] also has a range of documentation articles that translators can contribute to.</translate>

==<translate> Further Information</translate>==
* <translate>Crowdin have a comprehensive [https://support.crowdin.com/ Knowledge Base] which new users would be well served to familiarize themselves with.</translate>
* <translate>Some of the basic concepts about using Crowdin to translate Joomla are explained in more detail in the [https://magazine.joomla.org/all-issues/august/joomla-s-l10n-hearted Joomla's L10N-hearted] article from August 2021 in [https://magazine.joomla.org Joomla Community Magazine].</translate>

[[Category:Languages{{#translation:}}]]
[[Category:Volunteer Engagement{{#translation:}}]]

File:Crowdsourcing Screen.png

2021-09-12T05:24:16Z

Partic:

Parts of the Crowdsourcing screen translators see in Crowdin

File:Language List.png

2021-09-12T05:19:51Z

Partic:

Choose your language from the language list to begin creating translations.

File:Languages-crowdinfeaturedprojects.png

2021-09-12T05:14:51Z

Partic:

Choose a Featured Project on Joomla's Crowdin to start translating your language for that project.

2021-05-03T08:30:02Z

Partic: Removed JoomlaFramework twitter account - doesn't exist https://twitter.com/joomlaframework

<noinclude><languages /></noinclude>
<translate>

This page serves to document the Joomla's social media presence, to explain its content policies and strategies to the Joomla! community, and to collect and share information about the management of Joomla's accounts on the various social media channels.</translate>

<translate>
==Official way to contact the Joomla! Social Media Team== 
</translate>
<translate>

To contact the Joomla! Social Media Team please use the “Contact the Social Media Team” on Glip. If you would like to share something from official project's social media channel, or if you have any questions, simply comment in that group and we will answer you as soon as possible. If accepted we may edit and add tags etc as needed then share it. Please feel free to suggest appropriate copy and tags for the post topic.</translate>

<translate> We created an official repository on [https://github.com/joomla/socialmedia GitHub] to contact the Joomla! Social Media Team. If you would like to share something from official project's social media channel, or if you have any question, simply open an issue in the repo and we will answer you as soon as possible. We will revise the content and if we accept it, we will share it.</translate>

<translate>
==Team== 
</translate>
<translate> With the adaptation of the use of HootSuite, all of our Social Media Team members (SMT) have access to post on all of our platforms. While each platform has a team member/s specifically monitoring them, we have been utilizing the time and work savings of HootSuite to be able to schedule regular news posts. This responsibility is shared with all of the team rather than each post taking time from everyone.</translate>

<translate> Remember social media happens every day and our hard working team do their best to keep on top of things while also taking care of their own work and lives. If you see something to be shared or not right, drop a friendly note or tag us. We’re dancing as fast as we can.</translate>

<translate>
== Help Us Help YOU! == 
</translate>
<translate> #Help us see your Joomla content by tagging Joomla</translate>
<translate> #If you have a special event happening contact us and be sure to take photos of your event and supply text of what you want covered (you know your message best). This will allow us to post about your event on our channels.</translate>
<translate> #Have a group of posts you want to schedule for your team? Contact Alison and learn how to make it happen. We can set you up with our template to do your graphics.</translate>
<translate> #Did I mention TAG JOOMLA! We want to share your Joomla events out on our channels to show the world all the great things going on within the Joomla community.</translate>

<translate>
==The Joomla Social Media Team== 
</translate>
<translate> The Joomla Social Media Team consists of:</translate>
#[https://volunteers.joomla.org/joomlers/232-hans-van-der-meer Hans van der Meer] - <translate> Team Lead</translate>
#[https://volunteers.joomla.org/joomlers/266-alison-meeks Alison Meeks] - <translate> Assistant Team Lead</translate>
#[https://volunteers.joomla.org/joomlers/186-sandra-decoux Sandra Decoux]
#[https://volunteers.joomla.org/joomlers/1143-giovanni-genovino Giovanni Genovino]
<translate> Graphics for the Joomla posts if not included within the attached article or supplied by the team requesting the posts, are done by Sandra Decoux and Alison Meeks with the image support of our partner 123RF. Graphics for social are done both in horizontal format as recommended by FB/Tw/LinkedIn but also square for Instagram. Shout out thanks to the video team of Sandra and Brian Teeman who have been creating various videos for various special events for use on our social platforms.</translate>

<translate>

==Guiding Principles== 
</translate>
<translate> #We promote the features and benefits of Joomla! to a worldwide audience of enthusiasts.</translate>
<translate> #The SMT schedule regular posts via HootSuite and as well use it for news posts. Some days there is more news than others. We try to balance it out rather than flooding feeds.</translate>
<translate> #We strictly avoid controversial links, particularly those which involve Joomla! governance or community politics.</translate>
<translate> #Absolute priority is given to Joomla! Releases. Especially in the event of a security or new version release.</translate>
<translate> #We normally avoid mention of products or services developed by companies in the Joomla! Community that are not direct partners or sponsors.</translate>
<translate> #We do highlight events and teams in the community. Some of those are Certification, Showcase, JED, Open Source Friday’s, and volunteers.</translate>
<translate> #We coordinate our work with Joomla's release schedule and the marketing and communications needs of the project as a whole.</translate>

<translate>
==Moderation Guidelines== 
</translate>
<translate> #The Joomla! Volunteer Code of Conduct fully applies to the Joomla! Community gathered on Social Media. Users must conform their behaviour accordingly. At no time will any of our team tolerate harassment or attacks.</translate>
<translate> #Links should posted with the best pictures and images pulled via metadata, if any. Click-through metrics are significantly higher for posts which contain an image.</translate>
<translate> #We direct Social Media participants to ask support questions about Joomla! at the Joomla! Forum or other Joomla support groups located around the web. The official Joomla support is the forum and we always provide a link to it. We do not provide support via any social platforms.</translate>

== [http://www.facebook.com/joomla Facebook] ==
<translate>
===Main Admin=== 
</translate>
<translate> The official Joomla Facebook page is monitored by Alison Meeks with backup support from the rest of the team. Alison is also a member of several Joomla groups on Facebook and shares key posts to them such as updates/security patches etc. The Facebook JoomlaNoSpam Group is not an official Joomla property. Alison is an administrator in this group also. Rules for the NoSpam group are posted within the group. Hans is also in the group but isn't an admin.</translate>

== [https://twitter.com/joomla Twitter] ==
<translate>
===Main Admin=== 
</translate>
<translate> The official Joomla Twitter account is monitored by Hans van der Meer with backup support from the rest of the team.</translate>

<translate>
===List of Joomla Twitter channels=== 
</translate>
<translate>
====The"official" accounts==== 
</translate>

*Twitter: [https://twitter.com/joomla @joomla] - <translate> This account is for all kinds Joomla news and Joomla.org content. It is the go to Joomla Twitter account.</translate>
'''Note:''' Note: As far as possible, the main account follows current board members, team leaders and their assistants, former OSM presidents, JUGs, JoomlaDays, some major active contributors, and some accounts related to the Web.

<translate>
'''Twitter Accounts run by the Production or Marketing Departments''': </translate>
*Developer Network: [https://twitter.com/JoomlaDeveloper @JoomlaDeveloper]
*Joomla! Documentation: [https://twitter.com/joomladocs @joomladocs]
*Joomla! Bug Squad: [https://twitter.com/JoomlaBugSquad @JoomlaBugSquad]
*Joomla! Translation Centre: [https://twitter.com/JoomlaL10nC @JoomlaL10nC]
*Joomla! GSoC: [https://twitter.com/Joomla_GSoC @Joomla_GSoC]
*Joomla! Volunteers: [https://twitter.com/joomlers @joomlers]
<translate>
There are lists of accounts related to Joomla too </translate>
*[https://twitter.com/joomla/lists http://twitter.com/joomla/lists]

<translate>

====Twitter Accounts run by other parts of the Joomla Project==== 
</translate>
<translate>

Do you know more? We want to get in contact with you to join forces! Join the chat!
</translate>
*Twitter: [https://twitter.com/OSMatters @OSMatters]
*Twitter: [https://twitter.com/JoomlaConnect @JoomlaConnect]
*Twitter: [https://twitter.com/JoomlaJUGS @JoomlaJUGS]
*Twitter: [https://twitter.com/Joomla_JED @Joomla_JED]
*Twitter: [https://twitter.com/joomlaevents @joomlaevents]
*Twitter: [https://twitter.com/jworldcon @jworldcon]
*Twitter: [https://twitter.com/JoomlaVel @JoomlaVel]

==[http://www.linkedin.com/companies/joomla Linkedin]==
<translate> The official Joomla LinkedIn account is monitored by Hans van der Meer with backup support from the rest of the team.</translate>

==[https://www.youtube.com/user/joomla/ YouTube]==
<translate> The official YouTube account is updated by Sandra Decoux and Alison Meeks.</translate>

==[https://www.instagram.com/joomlaofficial/ Instagram]==
<translate> The official Joomla Instagram account is run and monitored by Sandra Decoux with backup by the team. Due to Instagram’s unique operation Sandra manages it and does the scheduled posts per her experience with the platform.</translate>

==[http://www.pinterest.com/joomla/ Pinterest]==
<translate> The official Joomla Pinterest account is monitored by Giovanni Genovino with backup by the team.</translate>

==MeWe==
<translate> A Joomla MeWe group account has been created by Alison Meeks to secure the name. Pages there are paid as they don’t do an “ads based” income program but the groups are free. If there gets to a point where there is enough interest we can approach the board for financial approval.</translate>

<translate>
==Want to Join the Social Media Team?== 
</translate>
<translate> If you have the desire and are willing to commit the time we would love to have you join us on the Social Media Team. You can view available positions here: https://volunteers.joomla.org/teams/social-media-team</translate>

<noinclude>
[[Category:Working Groups{{#translation:}}]]
[[Category:Marketing Communication Department{{#translation:}}]]
</noinclude>

Joomla User Group Speakers

2021-05-01T21:14:57Z

Partic: Added speaker profile

<noinclude><languages /></noinclude>

{{:Joomla_User_Group/TOC/<translate>
en</translate>}}
<translate>

This page is intended to be a list of people who are willing to speak at Joomla User Group meetings either in person or virtually.


If you are inviting a speaker who has to travel a significant distance, it is generally best practice to offer to cover some or all of their reasonable travel expenses - some speakers will decline, but it's polite to offer.


To add yourself to the list below, just create an account (top right of this page), then edit the page and add a new row. Be sure to leave a way for people to contact you.
</translate>
{{-}}
{| class="wikitable sortable"
|-
! <translate>
Your name</translate> !! <translate>
Your Locality</translate> !! <translate>
Your country</translate> !! <translate>
Topics you can speak on</translate> !! <translate>
Areas you can visit / Can do online</translate>
|-
| [http://lanyrd.com/profile/rcheesley/ Ruth Cheesley] || [https://www.google.com/maps/place/Ipswich/@52.0573075,1.1639946,13z Ipswich, UK] || <translate>
UK</translate> || <translate>
I can speak about Joomla, SEO, Web design/development, Running a business with Joomla, Open Source, Women in Tech - and more!</translate> || <translate>
Anywhere in UK, Other places possible subject to travel plans - can do online/skype/hangout</translate>
|-
| Jennifer Gress jenngress@gmail.com || <translate>
California</translate> || USA || <translate>
Migration</translate> || <translate>
Local I can do live, otherwise, online is fine.</translate>
|-
| Ali Tavanayan || Vancouver || <translate>
Canada</translate> || <translate>
e-commerce, Integration, Conversion Optimization, Site building and auditing, Run a web business</translate> || <translate>
I do talk locally, unless I am already traveling to your city! Doesn't hurt to ask, just let me know by email.</translate>
|-
| Lucas Radke (lucas @ 4491.eu) || Karlsruhe || <translate>
Germany</translate> || <translate>
Speed, Security, View from a mass Hoster</translate> || <translate>
Anywhere in Germany, East France or Mallorca in Spain, Other than that depending on my travel plans - can offer via skype or hangout</translate>
|-
| [https://www.squareballoon.co.uk Eoin Oliver] || [https://www.google.co.uk/maps?q=london&um=1&ie=UTF-8&sa=X&ved=0ahUKEwiaorzmhtbTAhWFthoKHX0aAx4Q_AUICigB London, UK] || <translate>

England</translate> || <translate>

Email Marketing, Social Media Marketing</translate> || <translate>

Happy to do a Skype or a Hangout, would consider traveling in the UK. May consider elsewhere if I was traveling already or it fits with my plans.</translate>
|-
| <translate>
[https://kps.fyi/pj Patrick Jackson]</translate> || <translate>
Melbourne (UTC+10)</translate> || <translate>
Australia</translate> || <translate>
Everything Joomla; Contributing to Joomla; SEO; Site Optimization</translate> || <translate>
Available for virtual presentations in most time zones.</translate>
|-
| <translate>
Add your name here</translate> || <translate>
Example</translate> || <translate>
Example</translate> || <translate>
Example</translate> || <translate>
Example</translate>
|-
| <translate>
Add your name here</translate> || <translate>
Example</translate> || <translate>
Example</translate> || <translate>
Example</translate> || <translate>
Example</translate>
|}

<div class="row">
<div class="large-6 columns">{{Basic button|S:MyLanguage/Joomla_User_Group_Resources|<translate>
Prev: Joomla! User Group Resources</translate>|class=expand success}}</div>
<div class="large-6 columns">{{Basic button|S:MyLanguage/Joomla_User_Group_Past_Presentations|<translate>
Next: Joomla User Group Past Presentations</translate>|class=expand}}</div>
</div>

<noinclude>
[[Category:User Groups{{#translation:}}]]
[[Category:Joomla! User Group{{#translation:}}]]
[[Category:JUG{{#translation:}}]]
[[Category:Events Department{{#translation:}}]]
</noinclude>