Code org на русском
Code org на русском
About Us
History
In 2013, Code.org was launched by twin brothers Hadi and Ali Partovi with a video promoting computer science. This video became #1 on YouTube for a day, and 15,000 schools reached out to us for help. Since then, we’ve expanded from a bootstrapped staff of volunteers to build a full organization supporting a worldwide movement. We believe that a quality computer science education should be available to every child, not just a lucky few.
What We Do
We do work across the education spectrum: designing our own courses or partnering with others, training teachers, partnering with large school districts, helping change government policies, expanding internationally via partnerships, and marketing to break stereotypes. Our work builds on decades of effort, by countless organizations and individuals who have helped establish, fund, and spread computer science education. We’re grateful for the tireless work of the broader computer science education community, and we thank all the partners and individuals who have expanded our impact over the years.
Code.org’s International Reach
Over 40% of our website traffic comes from outside of the United States and that number continues to climb. In order to expand global access to computer science, our team works closely with more than 100 international partners, helping them to promote the Hour of Code, advocate for policy change, and train teachers. We are making computer science part of the international education discourse by partnering with ministries of education from around the world and working with international organizations like the Organisation for Economic Co-operation and Development and the United Nations Educational, Scientific and Cultural Organization.
Translation
Want to have a direct impact on students in your country? Help us make Code.org content available in their native language! If you volunteer to help translate our tutorials and lessons, you’ll be joining a community of more than 7,000 translators who help bring computer science education to students around the world. Take a look at our translation guide for more information.
Our commitment to free curriculum and open source technology
All curriculum resources and tutorials we create will forever be free to use and openly licensed under a Creative Commons license, allowing others to make derivative education resources for non-commercial purposes. If you are interested in licensing our materials for commercial purposes, contact us. Our courses are translated for worldwide use or by speakers of different languages. Our technology is developed as an open source project.
Программирование с code.org
Свежие записи
Метки
Архивы
Это интересно
В нашем учебном заведении при изучении программирования используется электронный задачник Programming Taskbook (http://ptaskbook.com) и система PascalABC.NET (http://pascalabc.net).
Каждый в этой стране должен научиться программировать, потому что это учит людей думать.
Созданная в 2013 году обучающая платформа code.org является некоммерческой, полностью бесплатной системой онлайн обучения посвященной популяризации программирования среди всех желающих его изучать.
Среди создателей и спонсоров — знаменитые личности в IT-индустрии: Марк Цукенберг (Facebook), Гейб Ньюэл (Valve), Билл Гейтс (Microsoft), Джек Дорси (Instagram) и другие.
Создатели проекта считают, что каждый учащийся в каждой школе должен иметь возможность изучать информатику и программирование на доступном уровне.
Code.org поможет всем желающим независимо от их возрастных категорий и способностей войти в мир современных IT-технологий.
Обучение проходит в игровой форме, но охватывает все основные базовые понятия языков программирования. Как и в нашумевшем Scratch, используется похожий язык — «blockly», детям не нужно запоминать текстовые конструкции для написания кода. Составление скриптов (алгоритмов) производится путем перетаскивания блоков с командами и другими конструкциями в область кода.
Советую использовать code.org перед изучением языка Scratch. Так как он предоставляет уже готовые разработанные курсы с которых удобно быстро начать обучение. Все курсы предоставлены на многих языках, в том числе и на русском.
После создания учётной записи, учитель может контролировать прогресс своих учащихся. Для этого нужно создать виртуальный класс, выбрать курс для изучения (предложено множество курсов для разных возрастных категорий), добавить учащихся (поддерживается экспорт списка) и можно приступать к обучению.
После того как учитель настроил класс, каждому учащимуся выдается уникальное секретное слово. У каждого класса есть персональная ссылка для входа. С помощью этой ссылки и секретного слова и осуществляется вход в аккаут учащегося.
Сервис можно использовать для организации дополнительного домашнего задания или на факультативных занятиях и кружках.
Code.org и программирование для детей
Ниже приводится гостевой блог, написанный Посол учителей CodeMonkey
Code.org предлагает учебные программы для начальной и средней школы. Они также предлагают семинары для учителей, чтобы узнать, как использовать платформу кодирования в Соединенных Штатах. Мне посчастливилось быть Code.org Основы CS Фасилитатор из штата Иллинойс, и мне очень нравится энтузиазм и энергия, которые я получаю от учителей, которые проводят семинары, поскольку они создают план для реализации в рамках семинара, чтобы они могли немедленно вернуть его своим ученикам. Учебная программа состоит из уроков без подключения к электросети (без использования компьютера) и с подключением к сети. Каждый урок без подключения к сети знакомит с концепциями, которые затем можно отрабатывать в подключенных головоломках в режиме онлайн. Это позволяет обучать программированию всех учащихся, даже если технологии недоступны. В Соединенных Штатах 90% родителей хотят, чтобы их дети изучали информатику, но 40% в школах преподают ее. Информатика является фундаментальной. Реальность такова, что технологии влияют на все области торговли:
Community
Join the movement
Join this teacher-led movement to ensure that every student in every school has the opportunity to learn computer science. Share your passion and get the latest information, tips, and tools on social media.
Join the conversation with other teachers using Code Studio on our forum.
Connect to your local community
Computer Science Teacher’s Association: The CSTA is an engaged community of educators across the nation that is committed to bringing computer science education to their students while raising awareness of the subject to the general public. They host an annual conference and also have chapters that hold local meetings.
Advocating for computer science: We have a (small) team that focuses on advocating through state governments to bring computer science into K-12 classrooms. We have fact sheets telling the state of computer science in each of these states — and you can access and download your state’s information.
Leadership Opportunities
Become a Code.org Regional Partner
Code.org Regional Partners help increase the sustainability of our Computer Science programs at the local level. Code.org is partnering with organizations who can host local workshops for teachers new to computer science and build and sustain a community of computer science educators.
Become a Code.org Facilitator
Code.org is interested in partnering with experienced computer science educators to host local workshops for teachers enrolled in our Professional Learning Program.
Other Community Resources
Looking for other ways to get connected to computer science teachers around the world? Check out these great resources from our partners:
Don’t see your local CS community listed? Connect with @TeachCode on Twitter so we can get to know you!
На Code.org у детей не сохранилась домашняя работа: кончился 32-битный индекс
Задание из вступительного курса «Введение в информатику» на платформе Code Studio
Сайт для обучения программированию Code.org попал в неловкую ситуацию. Из-за «технических проблем» на платформе Code Studio утром 20 января с 9:19 до 10:33 PST работы школьников по программированию — весь написанный код и другие действия на сайте — не удалось сохранить.
Технический директор образовательного сайта Джереми Стоун (Jeremy Stone) оперативно опубликовал объяснение произошедшего: «До нынешнего времени мы хранили работы по программированию учеников в таблице с 32-битным индексом, — написал он. — Эта база данных может хранить только 4 млрд строк информации об активности. Мы не осознавали, что приближаемся к этому лимиту, и таблица заполнилась».
«Сейчас мы сделали новую таблицу активности студентов, которая сохраняет учебный прогресс. С новой таблицей мы перешли на 64-битный индекс, который позволяет хранить до 18 квинтиллионов строк информации, — объяснил технический директор. — Положительной стороной является то, что новая таблица сможет хранить информацию об учебных работах миллионы лет».
Из-за проблемы с переносом данных сайт вообще на некоторое время ушёл в офлайн, что могло обеспокоить 16 миллионов учеников, которые проходили там задания и сохраняли результаты. Позже учебная платформа по программированию вернулась в строй с частично восстановленными данными.
Администрация пояснила, что код, созданный между 9:19 до 10:33 PST, сохранить не получилось, он потерян безвозвратно. Кроме того, на время переноса данных из старой таблицы в новую некоторый сохранённый ранее код был временно недоступен. Но в течение суток программисты Code.org закончили перенос данных, и вся сохранённая информация пользователей снова появилась в их аккаунтах.
Code.org — некоммерческая организация и сайт, который помогает школьникам и другим начинающим ученикам освоить основы программирования. На сайте размещена бесплатные уроки программирования. Сайт открылся в январе 2013 года с первоначальной целью составить каталог компьютерных курсов в школах США. Основатель проекта Хади Партови (Hadi Partovi) тогда заметил, что в 90% американских школ вообще не преподаётся программирование, хотя это «фундаментальная дисциплина». Инициатива получила всеобщую поддержку. В феврале 2013 года в рекламе Code.org снялись Билл Гейтс, Марк Цукерберг, Джек Дорси и другие программисты и предприниматели — все они говорили, как важно научиться программировать.
В декабре 2013 года Code.org запустил общенациональный конкурс Hour of Code Challenge, в котором предлагалось принять участие всем студентам и школьникам страны. Участники решали простые задачки на программирование: нужно было написать небольшой фрагмент кода на визуальном «детском» языке программирования Blocky, чтобы достичь поставленной цели. После запуска конкурса в нём поучаствовал даже тогдашний президент США Барак Обама, а также руководители крупнейших ИТ-компаний, в том числе Microsoft и Apple. В общей сложности около 20 млн участников написали более 600 млн строк кода.
Поскольку в большинстве школ отсутствовали уроки программирования, организаторы Code.org начали решать эту проблему. С 2014 года там открылись курсы программирования, в которых могла участвовать любая школа. К 2017 году обучение на Code.org прошли более 51 тыс. учителей информатики. Были заключены партнёрские соглашения со 120 учебными округами и множеством школ на обучение школьников на сайте Code.org. По опросу учителей, 99% из них рекомендуют вступительный курс «Введение в информатику» (20-часовые курсы по основам информатики для всех возрастов, доступны на русском языке).
По текущей статистике, на учебной платформе Code Studio зарегистрированы 506 546 учителей информатики и 16 472 129 учеников.
Сейчас организаторы национальной американской программы ставят перед собой цель устранить неравенство в информатике: привлечь в программирование девочек и меньшинства (афроамериканцев и латиноамериканцев), добавить информатику во все 12-е классы американских школ и заставить власти всех 50 штатов признать информатику базовым учебным предметом (20 штатов уже сделали это). Code.org теперь вышел за пределы Америки: сейчас курсы программирования доступны на 45 языках мира, в том числе на русском.
Наверное, когда проект создавали в 2013 году, организаторы не рассчитывали на такую популярность, поэтому изначально спроектировали 32-битный индекс для учебной платформы. Мол, 4 млрд строк должно быть достаточно для каждого.
Если посмотреть на эту проблему философски, то 20 января 2017 года ученики на курсах программирования получили по-настоящему ценный практический урок из реального мира. Изначальный выбор архитектуры проекта может иметь непредвиденные последствия для внедрения, управляемости и жизнеспособности проекта в долговременной перспективе. К тому же, этот случай поощрит детей к размышлениям, как избежать рисков, вызванных надзором некоторых взрослых. И что облаку нельзя доверять на 100%.
Archie Goodwin
Авторизация
Рубрики блога
Рекомендуем
Последние комментарии
Облако тегов
Устами великих
Реклама
Онлайн учебник Codecademy проект Code.org
К этому проекту привлекло мое внимание видео, увиденное на одном из новостных сайтов, собственно, вот это видео.
Меня пока больше всего заинтересовал курс по JavaScript, который решил пройти в первую очередь, наверное, потому, что это один из самых простых и используемых языков, да и потому, что часто используется в качестве функционального элемента в веб-проектах, с чем мне нередко приходится иметь дело. Зарегистрировался и так увлекся, что сразу же прошел первый курс из 28 упражнений, который служит чем-то вроде вводного занятия.
В качестве отправной точки, сразу вам необходимо пройти по ссылке и зарегистрироваться на сайте codecademy.com.
После ознакомления с сайтом, что вы сможете успешно сделать сами, если того пожелаете, нужно зарегистрироваться (Создать учетную запись). Для этого вам понадобится лишь почтовый ящик, логин на английском и пароль продублировать дважды (стандартный набор 🙂 ).
Далее в верхнем меню кликаете на ссылку Учиться, выбираете язык программирования, который хотите изучить, далее выбираете курс и поэтапно их проходите следуя указаниям учебного пособия.
Да, забыл упомянуть, сайт на главной частично переведен на русский, но курсы обучения все еще на английском, может в будущем их и переведут, но пока как есть. Исходя из этого, хотя бы самое убогое понимание английского (пусть даже у вас в школе была тройка с натяжкой) было бы желательным. Но даже если с английским очень серьезные проблемы, то это не причина останавливаться на старте.
About Us
Over 70 million students and 2 million teachers on Code.org
Code.org increases diversity in computer science by reaching students of all backgrounds where they are — at their skill-level, in their schools, and in ways that inspire them to keep learning. The vast majority of the students on Code.org are from student groups historically underrepresented in computer science. Increasing diversity in computer science is foundational to our work, and we encourage you to read more about our efforts.
Code.org in the News
Our goals and metrics
For a closer look at our goals in closing gaps and increasing opportunity, you can review the ambitious 2025 goals we’ve detailed and how we determined those goals. We’ve also identified a number of large-scale, multiyear projects that would enable Code.org to reach an even greater scale in making CS a standard in education globally. Read about them in our Big Bets in Computer Science Education summary.
| Code.org Goal | Accomplishment |
|---|---|
| Improve diversity in CS (US students) | 45% of Code.org students are young women, 50% are students from marginalized racial and ethnic groups, and 45% of US students are in high needs schools. Read more about our approach to diversity. |
| Inspire students | Tens of millions have tried the Hour of Code. (1,495,916,037 served. 49% female) |
| Reach classrooms | 2,295,455 teachers have signed up to teach our intro courses on Code Studio and 73,704,313 students are enrolled. |
| Prep new CS teachers | We’ve prepared more than 106,000 new teachers to teach CS across grades K-12. Learn about our professional learning programs. |
| Change school district curriculum | We’ve partnered with 180+ of the largest school districts and 60 regional partners to add CS to school curriculum. Learn about becoming a regional partner. |
| Set up policies to support CS | Policies changed in 50 U.S. states to establish CS education standards, make CS courses count towards high school graduation, etc. (details) |
| Go global | Our courses are available in over 67 languages, used in 180+ countries. |
More information, history, and philosophy
In 2013, Code.org was launched by twin brothers Hadi and Ali Partovi with a video promoting computer science. This video became #1 on YouTube for a day, and 15,000 schools reached out to us for help. Since then, we’ve expanded from a bootstrapped staff of volunteers to build a full organization supporting a worldwide movement. We believe that a quality computer science education should be available to every child, not just a lucky few.
To support our goal, we do work across the education spectrum: designing our own courses or partnering with others, training teachers, partnering with large school districts, helping change government policies, expanding internationally via partnerships, and marketing to break stereotypes.
Our work builds upon decades of effort, by countless organizations and individuals who have helped establish, fund, and spread computer science education. We’re thankful to benefit from the tireless help of the broader computer science education community, and we thank all the partners and individuals who have supported our impact over the years.
A unifying approach in a divided world
Code.org’s global role in the K-12 computer science movement is only possible because we use a unifying approach across diverse and often divided stakeholders. At a time of increasing polarization, the idea of increasing opportunity for students unites people from across the political spectrum. Code.org’s team members, students, teachers, and supporters have diverse and diverging viewpoints, and they are all welcome in our mission. Read more.
Our commitment to accessibility
Code.org believes computer science is foundational for all students and we are committed to equity, access, and opportunity in our organizational values. To achieve this goal, we work to identify and eliminate barriers that prevent the inclusion and full participation of students and educators with disabilities. To learn more about our efforts, see our accessibility statement.
Our commitment to free curriculum and open source technology
All curriculum resources and tutorials we author will forever be free to use and openly licensed under a Creative Commons license, allowing others to make derivative education resources for non-commercial purposes. If you are interested in licensing our materials for commercial purposes, contact us. Our courses are translated for worldwide use or by speakers of different languages. Our technology is developed as an open source project.
Code.org Advocacy Coalition
The Code.org Advocacy Coalition is a bipartisan coalition of corporations and nonprofits that work together to help establish US federal and state policies to expand and sustain access to K-12 computer science and to broaden participation and diversity in the field. We bring together Republican and Democratic political leaders in common cause supporting expanding access to and participation in K-12 computer science.
K-12 Computer Science Framework
Code.org Donors
Code.org® is a registered public 501c3 nonprofit, with support from the general public. We are grateful for the generous support we’ve received from individuals and organizations who support our vision.
Code’s accomplishments (above) demonstrate our ability to leverage those dollars into strong outcomes. But given our nonprofit ambition that every child in every school should have access to computer science — to become literate citizens in today’s digital world and to test their interests in exploring CS further as a career — we have a long way to go to meet a fundraising goal that will support that vision.
Please contact us if you, your company, or your foundation is interested in talking with our leadership team further to better understand our program and to explore options for investing in our work.
Обучение программированию на Code.org
Потребность в программистах сейчас гораздо выше, чем число студентов, изучающих программирование. Я не побоюсь утверждать, что в ощутимом будущем большинство известных нам профессий исчезнет по причине автоматизации. Поэтому, важной задачей для развитых стран является увеличение количества специалистов в этой области.
Появляются все новые проекты, посвященные образованию в сфере IT, нацеленные на подрастающее поколение. Один из наиболее интересных — code.org. «Домашние задания» вашим детям дают такие известные личности как Билл Гейтс, Марк Цукерберг, Джек Дорси… Слоган: “Каждый ученик в каждой школе должен иметь возможность научиться программировать”.
Принцип игр таков: игрок не управляет персонажем в реальном времени, а вместо этого составляет последовательность команд и запускает их на выполнение. В процессе игры по мере возрастания сложности изучаются базовые принципы программирования, такие как: цикл, процедура, функции, условие и др.
Обучение проходит легко и интересно. По сути вы не играете, а пишите код на яп. Процесс реально захватывает, одну задачу можно решить несколькими способами.
Вот ответы на задачки к уроку №15.
Хотя для одной задачи может существовать несколько решений, у каждого ведь своя логика.
| Задание | Картинка задания | Картинка Решения | Код решения | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1. Эта головоломка показывает, как устроены процедуры «нарисовать квадрат» и «нарисовать окружность». Чтобы нарисовать квадрат, тебе нужно достать блок «нарисовать квадрат». |  |  | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2. Используя процедуру «нарисовать квадрат» как пример, создай процедуру «нарисовать треугольник» и используй её. |  |  | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3. Нарисуй треугольные ограждения вокруг кошек и квадратные ограждения вокруг коровы. Совет: проверяй программу по мере продвижения вперёд. |  |  | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 4. Посмотрим, сможешь ли ты сообразить, как использовать «нарисовать квадрат» и «нарисовать треугольник» (и некоторые другие блоки), чтобы нарисовать дом вокруг льва. |  |  | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 5. Теперь создай новую процедуру «нарисовать дом» и используй её, чтобы обеспечить двух кошек жильём. Подсказка: Создай новую процедуру с помощью блока «выполнить что-то» и введи свой текст в названии блока. |  |  | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 6. Используя «нарисовать квадрат» в качестве примера, добавь параметр с именем «длина» в процедуру «нарисовать треугольник». Затем нарисуй треугольники разных размеров. (Подсказка: нажми на звездочку для добавления параметра к процедуре) |  |  | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 7. Добавь параметр с именем «длина» в процедуре «нарисовать дом» и построй большой дом для слона (со сторонами длиной 150) |  |  | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 8.Здесь есть все блоки из предыдущей головоломки. Измени «нарисовать дом» так, чтобы после рисования нового дома я оказывался в правом нижнем углу. Используй эту изменённую процедуру, чтобы нарисовать три дома. |  | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Our own team gender diversity | |
|---|---|
| Code.org full time staff | 60% female |
| Our leadership team | 55% female |
| Our engineering team (software engineers only) | 55% female |
| Our technical staff (software engineers, technical product managers, computer science educators) | 53% female |
| Our extended team of expert facilitators | 66% female |
| The teachers attending our professional development | 86% female |
“I had more girls interested this year than ever. Students were skipping recess to come to my class to do extra coding!”
Our curriculum platform
In only six years, we’re proud to have grown into the most broadly-used curriculum in computer science, with 37% of our teachers and students using the platform from outside of the U.S., and 54% of our CS Fundamentals usage being international as well.
Beyond measuring logins or page-views, we measure student achievement, whether at solving coding puzzles or passing the AP computer science exam. We created a definition of “basic coding proficiency” in our CS Fundamentals course by measuring student success in coding challenges.
As a first step in measuring achievement on our platform, this method will continue to improve and evolve. In the meantime, this chart shows how many students demonstrate this proficiency at different levels of difficulty, with almost 4.5 million showing “basic coding proficiency”.
By the end of 2019, students have created 67 million projects on Code.org, demonstrating that computer science can help schools teach problem-solving and critical-thinking hand-in-hand with creativity and collaboration. For these and other fun data points, see our new Code.org Statistics page.
“My students didn’t realize coding could be a career option! As children of a very rural part of southern Ohio, they don’t always see a variety of careers in action, so this was eye-opening to them. When we watched the videos and discussed the career options, they were excited! Many went home that night and continued coding.”
-Kayleigh Stevens, Ohio
The AP Computer Science Principles exam
In 2019, Code.org Computer Science Principles classrooms accounted for 42% of all U.S. students taking the Advanced Placement exam, up from 38% in 2018. Given our scale, the performance and diversity of Code.org students on the exam matches the national average. Both nationally and in Code.org classrooms, the pass rate also increased by one percentage point compared to 2018.
The exam pass-rate, however, can be unreliable for drawing academic conclusions, because for an optional course and an optional exam the pass-rate can vary widely based on the selection of students who take the class or the exam. Given our focus on diversity, what’s important to Code.org is to maximize the total participation and diversity of students in computer science, and to help as many students learn as possible.
Over 39,000 Code.org students took the AP Computer Science exam, including 13,110 female students, and 11,513 underrepresented minorities. As you can see in the chart below, classrooms taught by teachers who attended the Code.org Professional Learning Program also have an increased percentage of female and URM student test-takers compared to the rest of the nation.
This is consistent with a 2018 research study of schools in the Code.org program, which found a school’s participation in the Code.org program causes an estimated five-fold increase in the number of students that take, and earn qualifying scores on the AP Computer Science Principles exam.
Our work with America’s educators & schools
In 2019, Code.org continued to grow our professional learning for teachers and school outreach programs. Workshops were held throughout the country by our amazing network of Regional Partners and expert Facilitators. This network is the backbone for the future of computer science in U.S. schools.
Our professional learning network: 60 regional partners, 615 expert facilitators
After launching our first fee-for-service pricing two years ago, 2019 was an opportunity to focus on the sustainability of our new pricing model. We were proud to offer scholarships to half of our attendees, with the other 46% of teachers being able to fund the program on their own through school funding or other scholarships.
Across our programs, we passed a new milestone: 106,547 new CS teachers have been prepared by Code.org, 16,000 of which were in 2019. The largest growth can be seen in our programs aimed at preparing teachers in grades 6-12, particularly our CS Discoveries course for grades 6-10.
In addition to working directly with teachers through our Professional Learning Program and online curriculum, we’re also proud to partner with reputable education organizations such as the International Society for Technology Education (ISTE). In 2019, we participated in the writing and reviewing of the ISTE Computational Thinking Standards. These standards help integrate computational thinking into all disciplines, not just computer science, for students of all ages.
We also worked with the Expanding Computing Education Pathways Alliance, CSforAll, and CSTA to host our first ever CSEdCon. More than 450 attendees gathered in Las Vegas, Nevada from across districts, regions, and 17 countries to discuss advancing CS at a district and state-level. Keynote speakers included Global Teacher Prize winner Peter Tabichi, Nevada Governor Steve Sisolak and Nevada Senator Woodhouse.
“I went through Code.org’s CSP Training in the summer of 2017 and taught it for the first time last school year to 8 students. This year, I have 42 students! Who knows how high the numbers will go. Code.org’s curriculum, the support, and the friends that I have made have certainly made this an outstanding, comfortable experience. ”
-Joe Afflerbach, Pennsylvania
50 states have adopted policies for computer science
While most of Code.org focuses on implementing our computer science curriculum and our programs in schools, the Code.org Advocacy Coalition works to change government policies to support, expand, and sustain K-12 computer science. This wouldn’t be possible without our coalition partners (especially Microsoft, the College Board, the Computer Science Teachers Association, and Amazon), and the local champions who deserve the real credit for driving change.
Our state policy work focuses on 9 ideas we urge every state to consider. Below, we highlight our impact across 3 of these that are easiest to measure.
| Policy area | Policy changed since 2013 |
|---|---|
| Requiring all schools to offer CS States that have changed policies to require at least all high schools to offer one or more computer science courses | AL, AR, CT, DE, FL, GA, ID, IN, MD, NH, NJ, NV, SC, TX, VA, WA, WV, WY. |
| Establishing state-level standards for CS States that have developed or are in the process of developing state education standards for computer science | AK, AL, AR, AZ, CA, CT, DE, FL, HI, IA, IN, ID, KS, KY, MA, MD, MI, MO, MS, ND, NH, NJ, NM, NV, OH, OK, PA, RI, SC, UT, VA, WA, WI, WV States that are developing standards: MT, NC, NY, WY, TX. |
| Funding for CS States that have allocated funding specifically to K-12 computer science, totaling $150 million! | AL, AZ, AR, CA, CO, FL, GA, HI, IA, ID, IN, KY, MA, MD, MO, MS, NC, NJ, NM, NV, NY, OH, PA, RI, SC, UT, VA, WA, WV. |
In 2019, we set a new record, as 45 states adopted new policies for K-12 computer science in just one year! The Governors for CS partnership which we launched in 2016 now has 18 state governors committed to establishing educational standards, funding, and expanding access and diversity in computer science in every school in their states.
The Code.org Advocacy Coalition published the 2019 State of CS Education report, a landmark study of policy adoption in the United States. Code.org also grew the K-12 Computer Science Census database, which now has data on 55% of all U.S. schools, including data on 83% of public high schools. This is an increase of 13% across K–12 schools and 16% of public high schools reported last year.
Comparison of the school-level census data to the state policies shows that the implementation of Code.org policy recommendations correlate not only to increased access in K-12 computer science, but also to improved gender diversity.
“Our school is 7th through 12th grade. All students were able to participate, even those with intellectual disabilities reading on a kindergarten level. The variety of activities made Hour of Code accessible to all my students.”
-Robin Fox, West Virginia
The Hour of Code and CS Education Week
2019 was a record year for the Hour of Code, which has now surpassed 900 million served, with almost a third being international. In December alone, students tried the Hour of Code almost 50 million times.
Inspired by the United Nations’ Sustainable Development Goals, this year’s Hour of Code used #CSforGood as a guide for showing students how computer science can make a positive impact in our world —from self-driving car technology that can make our roads safer, to data science techniques that can identify disease earlier and keep us healthier.
This led to Code.org’s newest activity, AI for Oceans. Created to show the potential of Artificial Intelligence, AI for Oceans is the Hour of Code’s first machine learning activity. By teaching students about AI, training data, and bias while also exploring ethical issues and ways AI can be used in the world, we’re proud to bring another example to classrooms of how CS is about much more than coding.
Together with the CS Teachers Association and the Computer Science Alliance, we were honored to kick off CS Education Week in December with 400 Native American students from the Santa Fe Indian School in New Mexico. The event featured a student project fair and a #CSforGood panel that spoke to students about the importance of ethical responsibility in computer science.
The Hour of Code and CS Education Week have become a fixture in hundreds of thousands of schools, each year recruiting tens of millions of new students and tens of thousands of teachers to try computer science, globally.
Global momentum for computer science
Ever since the 2013 launch of Code.org, 50 countries have implemented nationwide policies or plans for computer science in primary and secondary school.
While many of these countries are acting independently of Code.org, most have drawn inspiration from our effort in the United States, from the global momentum of the Hour of Code, and from the work of classroom teachers who use Code.org in over 67 languages.
In 2019, we continued to strengthen our investment in international partnerships, with notable events across the globe. In February, President Cyril Ramaphosa pledged to overhaul South Africa’s education sector in part by including new technology subjects and specialisations including the internet of things, robotics, and artificial intelligence. Later in the year, Code.org President, Alice Steinglass, attended an Hour of Code with Stevo Pendarovski, the President of North Macedonia. Microsoft also organized a unique opportunity for two young girls to teach the Prime Minister of Malaysia, Mahathir Mohamad, how to code using Code.org.
Last but not least, Pope Francis joined 3 young women to contribute a line of code to an app, became the first Pope to program a computer, and called on students globally to learn computer science and use their creativity to improve the world.
This year it was also announced that the PISA assessment will soon measure how countries teach computational thinking and computer science. The PISA is an internationally recognized assessment on student achievement that determines how countries are ranked for student success in math and science. PISA 2021 will be the first to explicitly study how countries include computer science in their education programs. With the introduction of computational thinking in the PISA Math assessment, global ministries of education have a new incentive to prioritize CS in order to maintain their rankings.
We have a long way to go
With another record year behind us, we are more sure than ever about the momentum of the computer science movement, not just in the United States, but worldwide. Over 1.3 million teachers have joined Code.org to bring opportunity to their students.
The strength of this movement lies in the inspirational commitment of these educators. The nonprofits, philanthropists, corporations, and local governments who support them will push computer science to new levels in 2020 and beyond.
To all of our supporters and partners, to all the organizations helping the cause, and especially to the teachers: your dedication is what gives us our daily dose of motivation. Thanks to you, every year we are closer to realizing our vision: that every student in every school has the opportunity to learn computer science.
Hadi Partovi, Code.org
Finances
*Important note: The information above is not (yet) based on audited financials.
The table below shows the total cost breakdown of our headline achievements since founding.
Privacy Policy
Date of Last Revision: November 11, 2021
You can review the previous Privacy Policy here.
About Code.org
Code.org® is a US-based charitable nonprofit dedicated to expanding access to computer science in schools and increasing participation by young women and students from other underrepresented groups. Our vision is that every student in every school has the opportunity to learn computer science.
Your privacy is important to us. We want to be transparent about the personal data we collect, why we collect it, and what we do with it. Moreover, we want you to know your rights regarding your personal data. We recommend that you read this Privacy Policy carefully before accessing or using the Services. If you have any questions about this Privacy Policy, you can email us at privacy@code.org.
Code.org Privacy Principles
Our Privacy Policy is fueled by our commitment to the following Privacy Principles:
Privacy Policy
Visitors and users of the Services and participants in our education programs are referred to in this Privacy Policy individually as “User” (or “you” depending on the context) and collectively as “Users.” Any User that creates a student account is referred to as “Student” even if they are using the Code.org Services outside of a school setting. Similarly, any User that creates a teacher account is referred to as “Teacher.”
As a not-for-profit organization, we use the data we collect only insofar as it helps our mission of providing a high-quality computer science education for every student in every school. We established ourselves as a not-for-profit organization so that a for-profit motive will not interfere with our mission of providing a trusted educational resource.
Our Privacy Policy describes what information we collect, how we use it, when we may share it, how we protect it, and your choices and rights. Your use of the Services and any information you provide on the Services are subject to the terms of this Privacy Policy, which is incorporated into and subject to our Terms of Service.
By visiting or using our Services, you expressly consent to the information handling practices described in this Privacy Policy. In the event this Privacy Policy is translated into another language resulting in any potential conflict or ambiguity, the official version of the Privacy Policy shall remain the English version. Where we have entered into separate agreements with local education authorities or similar entities that supplement our Terms of Service for the processing of Student Records (as defined in the School Users and Student Records section below), such as our Student Data Privacy Addendum, the processing terms of those agreements may also apply.
Code.org is a signatory to the Student Privacy Pledge, which contains a set of principles intended to safeguard student privacy, including responsible stewardship, protection, and transparent handling of student data.
Quick Reference
How We Collect and Use Information
The sections below describe the ways Code.org collects and uses personal data, which refers to any information that Code.org can use to reasonably identify a User as an individual (directly or indirectly), as well as information that is or can be reasonably linked (directly or indirectly) to a User or a User’s device. This includes things like name, display name, email address, school name and address, telephone number, etc., provided by Users (“Personal Information”), persistent cookies or IP addresses automatically collected (“Persistent Identifiers”), as well as some of the non-Personal Information and technical information (described below) we collect that is associated with a User.
We generally collect personal data in three ways: (1) information a User voluntarily provides to us by using the Services, (2) information we automatically collect as a User uses the Services, and (3) information from third-parties. The types and amounts of personal data collected vary depending on whether the User is a Student, Teacher, parent or other visitor, and on how they use the Services.
Our goal is to minimize the personal data we collect. We do not require Users to create a Code.org account or otherwise provide Personal Information in order to participate in the Hour of Code tutorials or to try our courses. However, we cannot save a Student’s learning progress or a Teacher’s class records unless a User creates a Code.org account.
Code.org Student and Teacher Accounts
The following table describes the data that Code.org collects and stores if a User creates a Code.org Student or Teacher account for use with Code.org courses.
| Data stored by Code.org if a User creates a Code.org Student account | How and when is the data collected? | How this data is used |
|---|---|---|
| Display Name (e.g., “Cool Coder” or “John”) and username (e.g., “coolcoder7”) | Required by User (or their Teacher) on account creation | Display name is used to provide Students a welcoming login and to identify the Student in the Teacher’s view of student progress. We recommend using first names only to increase privacy. Usernames are generated based on the initial display name and can be used along with a password to sign into an account. |
| Account passwords | Required by User (or their Teacher) on account creation. | Passwords are established by the User and can be updated through the User’s account settings or by a Teacher that manages a section in which the Student is enrolled. They are used for User authentication at sign-in. |
| Secret words/pictures | System generated by Teacher when adding Student to section (if choosing not to use Student accounts with passwords). | Secret words or pictures are system generated, but can be reset by the Teacher. They are used for User authentication at sign-in. |
| Age (Not birthdate) | Required by User (or their Teacher) on account creation or first sign in before using the site. | This data is used to understand the developmental stage of Students in order to offer an age-appropriate experience for each Student. We also use this field to ensure we don’t allow Students under age 13 to access age-restricted features (such as sharing their coding projects on social media). We store ages (e.g., 16), as opposed to birth dates (e.g., Feb 13, 2001). |
| One-way hash of student email address (NOT the actual email address, which is collected in the web browser but never transmitted to Code.org and thus never stored by us) | Email address is required (but not stored) on account creation if a Student creates an account or a Teacher creates the account via a third-party rostering provider. Email address is not required if an account is created by a Teacher using a picture or secret word login for the section, though it can be optionally added by the Student later. | A Student’s email address is only used for the purposes of login (along with the User’s password). It is NOT stored by Code.org in a retrievable format. To protect Student privacy, we only store a one-way hash of the email address. We do not have any way of sending email to Students or retrieving their actual email addresses from their account. See Student Email Addresses below for more details. |
| Parent or guardian email address | Can be optionally provided by a parent to receive updates or create a login for their child at home. | Parents or guardians can choose to link their email address to their Student’s account to receive updates from Code.org. (A student can also add the parent or guardian email address.) A Student may want to create a personal login to access their account independently of their Teacher or school, especially if the Teacher decides to delete the classroom section that the Student belonged to or the Student signs in with a school-sponsored account like Google, Microsoft, Clever, or PowerSchool. If the Student is under 13 or doesn’t have a personal email address and wants to create a personal login, we require a parent or guardian email address for password recovery. The Student will then be able to sign in at home with a username and password. |
| Account Identifiers | System generated (separate identifiers may be provided by authentication services). This is NOT a student number assigned by a school. | These identifiers are used to maintain and operationalize accounts. |
| Login time, IP address, and other technical data | Automatically collected as the Services are used. | This data helps Code.org troubleshoot any problems Users experience. It also helps Code.org understand usage patterns, ensure the service can support all Users, and enable Services updates with minimal service disruption. See Technical Information below for more details. |
| Gender | Optionally provided by the Student or their Teacher. | This information is only used in aggregate to measure the percentage of students that are “male/female/nonbinary/preferred term not listed” and measure how such Students respond to different computer science challenges, or track our aggregate progress towards reducing the gender gap in computer science. |
| Race | Optionally provided by the Student (only requested from Students if their IP address is in the US). | Students aged 13 and over have an option to indicate their race. For Students under age 13 we do not ask individual race, but we ask the Teacher to optionally estimate the racial distribution of the entire classroom. This information is only used in aggregate, to measure the percentage of students from underrepresented racial and ethnic groups and their aggregate response to computer science challenges, and in order to track our aggregate progress toward improving diversity in computer science. |
| Progress in the course 1- Date/Time each lesson is tried 2- Number of tries to solve a level, and whether it was solved successfully or optimally 3- Information on how the Student solved the level including time to completion and whether they used hints 4- The code that the Student submitted 5- Student-provided answers to simple assessments (e.g., multiple-choice questions) | Collected as a Student works through a tutorial or course progression. | This information is displayed to Students and their Teachers to see their progress in a course, to see the code they’ve created, and to identify topics they need help with. It also lets Students pick up where they left off if they sign out and sign in later. See Technical Information below for more details. When Students work in the context of a classroom, their Teacher also has access to view the projects created by any Students in the classroom. Student projects and code creations each have a custom URL that Students can use to share with others, or post to the Code.org public gallery. On the public gallery, projects are displayed with only the first letter of the Student’s display name to protect Student privacy as well as their age. We do not allow Students under the age of 13 to share projects (e.g., in App Lab) to the Code.org public gallery when these projects allow for Student-uploaded content. Students may “remix” (copy and then change or improve upon) projects made by themselves or by other Users. Students age 13 or over can also, at their discretion, post their projects to their social media accounts. In our elementary school courses, Students create stories, games, or art using tools, such as Play Lab and Sprite Lab, which are generally limited to using artwork and sounds provided by Code.org or uploaded by their teacher. Where we do allow custom uploads by Students in these tools (e.g., uploading an image for a Student-created storyboard), Students are advised never to upload any media containing Personal Information and we implement controls that block Student sharing of projects to the Code.org public gallery that contain custom uploads. Students can write dialogues for these projects. Some text provided by Students in these tools is automatically analyzed and moderated to help prevent sharing of personal data like email addresses and phone numbers. Our middle school and high school courses teach Students to make more complex apps and games, such as App Lab, Game Lab, and Web Lab. These tools allow the Students to upload custom photos, sounds and/or videos. (See below) |
| Student-uploaded images, sounds, or videos | Collected if a Student chooses to upload custom files. | Only Students age 13 and older, or Students under 13 who are working in a classroom whose Teacher has added the Student to a class section, can choose to upload custom images, sounds, and videos to the Code.org platform to use within apps or games that they create in programing tools as part of our courses for grades 6+ (App Lab, Game Lab, and Web Lab). Students under 13 are advised never to upload any media containing Personal Information and we do not allow Students under the age of 13 to share projects created using these tools to the Code.org public gallery. Similarly, where custom uploads are allowed for programming tools intended for younger students (e.g, Play Lab and Sprite Lab), Students are advised never to upload any media containing Personal Information and we implement controls that block Student sharing of projects that contain custom uploads. These files are not used by Code.org for any purpose other than within these projects. These projects may be shared and remixed as described above, subject to those restrictions described. |
| Data collected by Student-created apps | Collected if users of a code project created by the Student choose to enter data into the app. | Students may use Code.org to create their own apps. Depending on the app author’s design, a Student-created app may in turn collect data by prompting other Users (anybody who tries using the Student-created app) to enter information, such as a favorite movie. If a Student creates an app that collects and stores data in this fashion, all data entered by Users of the app may be accessed and possibly shared publicly by the app author, the app itself, and potentially anybody with a link to view the app. Code.org does not itself use or share this data outside of the app. Before using a Student-created app that collects data, Users are shown a clear warning that any data they enter may be shared publicly and that they should not share anything personal to them or to others. |
| Written comments in response to curricular/educational prompts within Code.org courses | Collected if a Student chooses to enter text in response to the prompts. | Within some of our courses, Students in a classroom are prompted to answer a question. Their answers are shared with any Teacher with whom the Student is affiliated on Code.org and are used by Code.org in de-identified form to improve the curriculum. |
| Student-provided responses to surveys (e.g., multiple choice and free response questions) | Collected if a Student chooses to fill out a survey offered inside the courses. | We may ask for responses to attitudinal questions (to assist the Teacher in understanding their classroom’s reaction to learning computer science and, in de-identified or aggregate form, to help Code.org improve our curriculum). Students are informed that answers to these attitudinal questions are shared with the Teacher anonymously without their name attached. We may, however, share a Student’s identity, answer, and other information related to a given question with their teacher or appropriate authorities if we are prompted to do so, and upon investigation, we have a good-faith and reasonable belief that the answer indicates the Student may harm themselves or others, among a few other limited scenarios outlined in the section titled “How We Share or Transfer Information.” However, we are not actively monitoring student answers for such issues. If you are a teacher, please contact support@code.org so we can help you if your Student indicates they may be unsafe. |
| Additional* data stored by Code.org if a User creates a Code.org Teacher account | How and when is the data collected? | How this data is used |
|---|---|---|
| Email address | Email address is required at account creation (or when switching from a Student account to a Teacher account). | Email addresses are used to send emails to the Teacher with updates about their classroom or Student progress, send notices when new course-work is available, and provide updates on curriculum, tools, professional learning opportunities, etc. Teachers can choose at account creation whether to receive non-transactional emails (e,g., updates to our courses, local opportunities, or other computer science news). All non-transactional emails sent by Code.org contain an unsubscribe link and do not require typing a password to unsubscribe. |
| District and school name and/or school type (private, public, charter, homeschool, after school, organization, or other) and/or school address | Optionally provided by the Teacher at account creation or after creating an account. | At the Teacher’s discretion and under their control, we will list their school in the Code.org map and database of schools that teach computer science courses. Code.org or our professional development partners may also use this information to reach out to the Teacher’s school or district to discuss broader education partnerships or participation in special events. |
| Student section data | Collected if a Teacher decides to create a section on Code.org to manage their Students. | The Teacher may create accounts for their students (and provide each Student’s display name and, optionally, their age and gender) or direct students to create accounts themselves, and organize these Students into sections. The Teacher may assign each section a display name, a course assignment, and grade level. The section grouping data is used to simplify their view of Students across multiple sections. Teachers are encouraged to share a Code.org document with Students and parents informing them about enrollment in a Code.org section, including the privacy implications. |
| Survey and demographic data | Collected if a Teacher chooses to optionally fill out a survey. | For the purposes of evaluating our own work and improving our education results, Code.org regularly sends surveys to Teachers. These surveys are completely optional. The data provided by Teachers in these surveys is saved and used for analysis by Code.org, research partners, our Regional Partners, our International Partners, or facilitators. Any survey data shared with external parties is de-identified and aggregated. |
| Attendance at professional learning workshops | Collected when a Teacher attends a workshop. | Attendance of Teachers at our professional learning workshops is stored and associated with the Teacher’s account on Code.org. This data may be shared (along with the Teacher’s identity) with any other parties involved in the Teacher’s professional learning, such as the facilitator who led the workshop, the professional learning organization hosting the workshop, or the school district of the Teacher. In some cases, the school district may use workshop attendance data to compensate Teachers for participating in the Code.org professional learning program. |
| Progress, answers, documents, projects, and peer reviews for online professional learning. | Collected as a teacher interacts with our online professional learning tools. Participation in professional learning programs is optional. | Progress and answers in online professional-learning courses for Teachers are stored in their Teacher account in order to allow Teachers to pick up where they left off. This includes the lesson plans, documents, and other projects Teachers create as part of finishing the online learning courses. After submitting a document or project, Teachers receive peer feedback from each other which is also stored so that they can read it. Teachers also take a self-assessment survey to create a custom learning plan. The results of this survey are stored with the Teacher’s account along with their custom plan. |
| Comment feedback provided to students | Collected if a Teacher decides to give written comments to their Students on their work | The Teacher may provide written feedback to their Students on their coursework. Though a Student will only see the most recently provided comment on a given level, we store all the previously shared comments as part of the Teacher’s account in case the Teacher or school needs to access them later. |
* A Teacher account on Code.org has all the functionality of a Student account, and as a result the data collected and stored for a Teacher account is a superset of the data stored for a Student account.
Teachers can create accounts on behalf of Students. When registering an account for a Student who is under the age of 13, the Teacher represents and warrants that they or the educational organization they work for has proper permission to register the Student for a Code.org account, and that they or the educational organization has obtained the necessary parental consent for collection of the Student’s Personal Information for the use and benefit of the school and for no other commercial purpose. In addition, the Teacher agrees to be bound by the Code.org Terms of Service and this Privacy Policy on behalf of the educational organization they work for, and that they are authorized to do so. See Protecting Children’s Privacy below for more information.
Third Party Authentication Services
When using a third-party authentication service, Code.org may receive personal data (such as a Student’s full name or gender) that is not required for use of the Services. For example, districts or schools that use Clever as an authentication service can permit Code.org to use existing Clever teacher and student account information to sign in to Code.org Services. Districts or schools may revoke Code.org’s access to this information in Clever at any time.
You may revoke Code.org’s access to your account on any authentication service at any time by disconnecting the respective authentication service from your account settings. You should check your privacy settings on each authentication service to understand and change the information sent to us through such service. Please review each authentication service’s terms of use and privacy policies carefully before connecting them to our Services.
Non-Curriculum Features and Other Services
When you use certain non-curriculum features of our Services, Code.org may ask you to provide Personal Information including your full name, email address, age, school or company name, and postal code or school street address, as well as your billing and/or shipping information when necessary to complete a purchase or make a donation. Examples include signing forms or petitions to help advocate for computer science, providing information to put your school on the map of schools teaching computer science, contacting us for help or information via customer support pages, subscribing to receive email communications from Code.org, participating in a workshop, signing up as a local volunteer, bringing Code.org programs to your school or district, donating to Code.org, purchasing t-shirts or other items, nominating a teacher, or participating in online surveys. This information is used to enable your participation in the relevant feature and to send you occasional emails with information about Code.org that we feel may interest you. All non-transactional emails we send include an “unsubscribe” link. (When a User identified as under the age of 16 signs our online petition supporting Code.org’s mission, any name or email address they provide is deleted from our servers and thus never used.)
If you enter your name to create a certificate of completion upon finishing select courses or exercises, we store the certificate data in order to allow you to print and/or share the certificate digitally (e.g., on social media). We periodically delete this data, which may impact the certificate sharing function.
We may ask Users to provide us with optional demographic information (such as gender, age, race or ethnicity), which we use in aggregate to better understand our User base.
Computer science educators may provide a school or classroom street address, along with a description of course offerings, in order to allow students or parents to find local schools, summer-camps, or workshops that teach computer science in their neighborhood.
Location Information
Code.org does not request or collect GPS or other precise location data. We may collect and store non-precise location information (e.g., the approximate geographic region of a computer or mobile device, as determined from the IP address) to help provide educational experiences or email updates that are tailored for that region.
Information from Other Sources
In certain situations, we may obtain information, including Personal Information, from third parties or other sources. If we combine or associate information from other sources with personal data that we collect through the Services, we will treat the combined information as personal data in accordance with this Privacy Policy. Your sharing of Personal Information or other personal data with those third parties will also be subject to their privacy policies.
Technical Information
To provide a personalized learning and high-quality experience for our Users, we may use various technologies that automatically record certain technical information from the User’s browser or device, including browser language settings, standard log files, web beacons, or pixel tags. This technical information may include Internet Protocol (IP) address, browser type, internet service provider (ISP), referring or exit pages, click stream data, operating system, and the dates and times the User visited the Services. This information assists us in providing the Services and understanding how our Users are using the Services.
To assess information about use of our Services, we use various technological tools. For example, whether or not a User is a registered member, we may send one or more cookies to the User’s browser when they visit our Services. We may use:
Code.org may use both session cookies and persistent cookies. A session cookie disappears automatically after the User closes their browser. A persistent cookie remains after the browser is closed and may be used by the browser on subsequent visits to the Services. You can, however, remove a persistent cookie at any time. Please review your web browser Help file, Tools menu, or other similar menu options to learn the proper way to modify your cookie settings, or visit www.allaboutcookies.org. Please note that without cookies you will not have access to certain capabilities and features on the Services.
A pixel tag (also known as a “clear GIF” or “web beacon”) is a tiny image – typically just one pixel – that can be placed on a Web page or in an email to tell us when the recipient has displayed that page or opened that email. We may allow third-party service providers to place and read their own cookies, pixel tags, and similar technologies to collect information through the Services to perform the service we’ve requested. This technical information is collected directly and automatically by these third parties.
Custom Content
Student and Teacher profiles cannot be customized with a photo.
As part of certain in-browser programming tools available on Code.org (such as “App Lab,” Game Lab,” “Web Lab,” and “Sprite Lab”), Students can upload custom images, text, sound, and videos to the Code.org platform to use within applications or “apps” that they create. These files are stored by Code.org, but are not used by Code.org for any purpose other than within the applications created by Users. When we allow uploads of images, sounds or videos by Students under age 13, we implement controls that block Student sharing of such projects as described in the table above.
Internet Simulator and Other Messages
Code.org offers a tool called the “Internet Simulator” for use in High School classrooms to model how the Internet functions. With this tool, Students participating in a Teacher-supervised classroom activity can send text-based messages to their Teacher and to other Students in their specific classroom section. Message contents are visible to the classroom Teacher and are not accessed or used by Code.org for any purpose other than in this educational tool. All messages are deleted after two hours of class inactivity, or upon a manual reset by the Teacher.
In select courses, such as the Code.org CS A AP course, Teachers may optionally enable peer review groups within their classroom sections to allow students to provide feedback on other students’ projects. The student feedback is visible only to the Teacher and to students within the group designated by the Teacher. The Teacher may disable the feature at any time and may also delete specific feedback.
In addition, Teachers may provide written feedback to their Students on coursework. Users may also send messages to Code.org for customer-support requests.
Other than the above, the Services do not directly provide any other form of messaging among Users (although Users may use Code.org tools to create apps that support messaging among individuals).
Student Email Addresses
When Students use an email address for login, Code.org does not store the email address provided by those Users in a retrievable format. Instead, we immediately create and store only a one-way hashed version of the email address (which cannot be converted back into the original address), and use it only for the purposes of login, account management, and password recovery. In fact, when creating or signing into a Student account, the actual account email address is never even transmitted to Code.org’s servers. The only circumstance when Code.org’s servers receive a Student’s email address is if the Student forgets their password and asks to reset it. At that point, the Student is prompted to enter their email address, which is used to send them a password reset link after we verify the email address through the same one-way hashing algorithm. We then delete the clear text email address. We will, however, store and use email addresses provided by Students when they choose to participate in Non-Curriculum Features and Other Services to the limited extent described above.
For a small minority of our Students, and only if they are over the age of 18, we may offer the opportunity to participate in a “longitudinal” study to understand the multi-year impact of learning computer science. Participation in such a study is entirely optional. Students who receive an offer and choose to participate will be asked to provide their contact information (email address and optionally other forms of contact that may be more convenient for the Student). This contact information will not be shared with third parties, nor used in any way outside the purpose of such a study – to ask Students to participate in surveys. If we learn that we have inadvertently collected this information from a Student under 18, we will delete such information immediately.
No Commercial Use of Student Personal Information
Some laws, such as California’s Student Online Personal Information Protection Act (SOPIPA) and similar state laws, prohibit the gathering of the Personal Information of K-12 students for targeted advertising purposes. Code.org abides by such laws and shall not use, disclose, or compile Personal Information of Students on the Services for the purpose of marketing or advertising commercial products or services. We do not disclose Personal Information or other personal data of Students to third parties for marketing purposes.
How We Share or Transfer Information
We do not rent or sell personal data or any other information that we collect from Users, or exploit it for financial gain in any other way. Code.org will never share or grant rights to personal data with other third-party organizations to use without your consent, except as part of a specific program or feature for which you will have the explicit ability and choice to opt-in. In particular, we do not share any personal data you provide with our donors or sponsors (only de-identified reports as described below) without your explicit consent.
The sections below explain circumstances in which we may share personal data with third-parties. We may also share de-identified or aggregate data that does not reasonably identify any individual or User.
We may share personal data with third-party service providers
Code.org may use a variety of third-party service providers to support our operations. For example, we may use third parties such as email service platforms to send email, analytics companies to understand our Services usage and performance, and social networking platforms to host our videos. Similarly, we may use third-party service providers to implement and host our Services and associated services and features, provide teacher forums, process donations, provide contract and workflow management services, assist with customer support, and provide other functions in support of our organization. When we give service providers access to data, including personal data, they are only allowed to use the data to provide services for which we have contracted and based on our direction. They are not allowed to use personal data for any other reason without the user’s consent or at the user’s direction. You can find a list of third-party service providers we use here.
We may share Student personal data with the Teacher and Teacher personal data with the Student
If a Student belongs to a Teacher’s section, we will share Student account information, course progress, and standalone projects with that Teacher so the Teacher can help manage the Student’s progress. The Student will also see limited information about their Teacher including their Teacher’s display name and section information.
We may share personal data on classroom usage and Student achievement with the school or school district
In order to support school and district needs to oversee Code.org usage in their classrooms, we may allow a Student’s school or school district to access reporting data on student progress and achievement, presented on a student-level, classroom-level, teacher-level, grade-level or school-level basis for Students enrolled in a Teacher’s section. The reports available to school and district administrators will be based on the same data that is displayed on the Student progress report that is also shared with the Student’s Teacher(s). If Teachers choose to give Students feedback on coursework and projects through Code.org, we may also share this with school or district administrators upon request. We may also share personal data in Student Records with third-parties as directed by a school or school district. For more information about the data we may be sharing with a Student’s school or school district, please click here.
We may share Teacher personal data with the Teacher’s training facilitators, our Local Partner, the school district, and other partners
Code.org partners with U.S.-based nonprofit professional learning organizations (our “Regional Partners”) as well as similar organizations outside the U.S. (our “International Partners”) (collectively our “Local Partners”). We share limited personal data (never including Student personal data) with these partners to allow them to run local professional development workshops and support teachers and schools in their region. Each Local Partner signs an agreement with Code.org that requires them to comply with this Privacy Policy and to treat any information received through the partnership as confidential.
We may also share the list of schools (solely the school identities, without any personal data about Teachers or Students) that use Code.org or have participated in our professional learning program with select partners, such as a local, state, regional, or national education agencies or authorities, so long as such partners agree to treat the information as confidential.
We also provide Teachers other opportunities (such as when adding their school to the map of schools teaching computer science) to share their contact information (name, school, email) — at their option and under their control — with a Code.org Local Partner so that teachers can be contacted about local professional learning workshops, resources, and events.
Our Local Partners or other partners can sometimes provide additional programs or services such as scholarships or free supplies for schools. When these services or programs are available locally, Teachers will have the option to share their personal data, such as email address, school name, and school ID with a specific partner to opt in to a specific service or program to support their classroom.
We may share personal data Users choose to post publicly
In certain cases, Users may choose to post information that is publicly accessible on our Services. This includes making public posts as a Teacher on our forum, offering to be a volunteer if a User is over the age of 18, or choosing to put information about a User’s school or organization on a public map. When you are filling out a form to post information on our Services, we will always make it clear exactly what will be shared publicly.
Some of our Users choose to post their code-creations or other information to social networks. This functionality is entirely optional. When you post content to social networks, the content posted is entirely under your control, and never posted automatically on your behalf by Code.org. Typically this content includes only the code (i.e., the app or animation or game or other content that is part of the project) that you wrote, posted alongside any other remarks you may choose to add to it.
We may also re-share (e.g., retweet) public posts made by Users, educators, media, governments, or others on social media platforms without seeking permission.
We may share personal data when Users contact us for support
When a User contacts us with a support request, they may provide personal data, which is shared with a Code.org support representative in order to process the User’s request. Code.org support representatives are either employees or independent contractors of Code.org, and will always have signed an agreement requiring them to protect and not disclose confidential information including personal data of Users, and to use it only in the context of resolving product support requests.
We may share personal data if Users are chosen (and give permission) to be profiled on our Services
Code.org promotes Student and Teacher work on our Services and social media channels. These profiles and similar testimonials are published with the permission of the participating Student or Teacher and, if applicable, their parent, legal guardian, or teacher, and may include personal data such as the name, likeness, and photo or video of the person being profiled. As indicated above, we may also re-share public posts from other platforms (where we are not the original publisher) without seeking permission.
We may share personal data when required by law
Code.org may disclose personal data if required to do so by law, or if we have a good-faith belief that such action is necessary to comply with local, state, federal, international, or other applicable laws or respond to a court order, judicial or other government order, subpoena, warrant, or administrative request. In some cases, we may make such disclosures without first providing notice.
We may share personal data when necessary or appropriate to protect Code.org or others
Code.org may disclose personal data that we believe, in good faith, is appropriate or necessary to: take precautions against liability; protect Code.org from fraudulent, abusive, or unlawful uses; investigate and defend ourselves against third-party claims or allegations; assist government enforcement agencies; protect the security or integrity of the Services; or protect the rights, property, or personal safety of Code.org, our Users, or others.
We may share or transfer personal data in the context of a change of business, including a merger or acquisition
In the event that Code.org is acquired by, or combined or merged with, another entity, we may transfer or assign the personal data that we have collected as part of such merger, acquisition, sale, or other change of control. Our promise to you is that any personal data we have collected will be used, shared, and safeguarded by the acquiring organization under the same conditions described in this Privacy Policy.
We may share de-identified or aggregate data
We may share or publish de-identified or aggregate data about Students, Teachers, and our Services for various purposes. De-identified and aggregate data does not contain any personal data. For example:
We may provide our Local Partners with de-identified demographic information and information about usage of courses and professional learning programs for schools and districts in their area. They will not see names or contact information of any Teacher unless that Teacher chooses to share it as part of signing up for a local professional learning workshop or joining their professional learning program.
We may publish de-identified information (e.g., code.org/statistics) about Student performance on our Services. These reports will never include personal data. Instead, aggregated, de-identified data over large populations of Students may be reported by demographic criteria such as age, general location, gender, race or ethnicity, and socioeconomic status.
We may work with third parties (such as universities and education research organizations) to improve our services or offerings and disclose automatically collected and other aggregated and de-identified data to these authorized partners to conduct research on online education or assist in understanding the usage, viewing, and demographic patterns for certain programs, content, services, promotions, and/or functionality on the Services. We require any research partner that receives de-identified data from us to agree in advance that they will not attempt to use this data to identify Users.
How We Protect Information
We use reasonable safeguards to help ensure that our Services are secure, but no security measures are perfect
Code.org uses physical, administrative, and technical safeguards designed to reasonably protect the confidentiality, availability, integrity, and security of personal data and other information we collect and maintain in connection with the Services. These safeguards include, for example, restrictions on physical access to the data center, hardened system configuration, two-factor authentication, patch management, disaster recovery processes, employee security and privacy training, employee background checks, and third-party security resources, among others. We encrypt Personal Information in transit and at rest, and we have generally aligned our security practices to the NIST Cybersecurity Framework.
However, no security measures can fully ensure the security of any or all of the personal data or other information we collect and store. If you transmit personal data to Code.org you do so at your own risk. We cannot guarantee that such personal data and other information may not be accessed, disclosed, altered, or destroyed by breach of any of our physical, administrative, or technical safeguards.
If we learn of a data security incident that compromises or appears to compromise your Personal Information or that of your Students, we will attempt to notify you electronically so that you can take appropriate protective steps.
We try to minimize the personal data we collect and store
Code.org’s goal is to minimize the personal data we collect. For instance, Code.org does not directly collect or store payment instrument data. Donations to Code.org or purchases from the Code.org store are processed via third parties, and although Code.org receives a receipt for donations (for tax purposes), we never receive the payment instrument data (such as credit card number or wallet information). Similarly, Code.org does not collect or store biometric or health-related data and other sensitive categories of data except as disclosed in this Privacy Policy.
Even when Code.org collects personal data in order to provide the Services, we attempt to minimize the data we store. For instance we intentionally choose not to store email addresses for Code.org Student accounts or phone numbers used in our send-to-phone feature.
We limit employee and authorized party access to personal data
Code.org’s officers, directors, employees, agents and contractors must have a legitimate business reason (related directly to furthering our charitable, nonprofit, education-focused mission) to access personal data we maintain about Users or others (e.g., to assist in product support). Code.org provides staff privacy and security training and will require our officers, directors, employees, agents, and contractors to comply with this Privacy Policy, and to treat any personal data of Code.org Users as confidential information.
If, at any point, you wish to access, amend, or delete your personal data on the Code.org learning platform, you may do so from your Code.org account settings page as described below. Alternatively, if you wish to access, amend, delete, export, or object to or restrict the processing of your personal data, you can email us at support@code.org or enter a request at https://code.org/contact. We will promptly review all such requests in accordance with applicable laws after verifying your identity.
Unless we receive a deletion request, we may retain your personal data as long as a User account is active, as long as the personal data is necessary or useful for operational purposes, or as required under any contract or by applicable law. We may indefinitely retain information which has been de-identified or aggregated such that it is no longer personal data.
Managing and Deleting Code.org Accounts
Code.org does not require an account to try our courses. However, Students and Teachers with an account may update, correct, or delete Personal Information and other personal data in their Code.org accounts at any time via the account settings page after logging into their account. Teachers can go to their section’s “Manage Students” tab to update the most common settings or to access and delete a Student’s login information. Teachers also have the ability to reset the password of any Student in their section who is not also a Teacher. A parent or legal guardian of a Student under the age of 18 may also review Personal Information and other personal data and correct erroneous information, if any, by asking the Student or Teacher to access the Student account.
Except as described below, personal data of any Student that is in a Teacher’s section will be under the control of the Teacher. The Teachers for these sections get access to the Student’s course progress and display name, but not their email address. If a Student is no longer associated with a Teacher’s section, that means the Student’s account will no longer be managed by the Teacher and the Student may retain possession and control of the Student-Generated content by creating a personal email login. If a Teacher deletes their own Teacher account (and all sections under their account) or removes a Student from a section they manage, the Student account in the section will also be deleted unless the Student has created a personal email login for their Student account. If the Student has created a personal email login, the Student account will be removed from the Teacher’s section but the Student account will not be deleted.
In order to allow Users to recover deleted accounts, we will save progress, code creations and other data for a short period of time after a User executes an online deletion request. A User can email support@code.org or enter a request at https://code.org/contact to request an immediate permanent deletion of their account and all the associated data. A Teacher may also request the immediate deletion of Student accounts or particular Student projects or Student personal data the same way. Deleting a Student’s project will not delete other Students’ creations that were previously remixed from the deleted project. As part of the deletion process, we may de-identify data by removing identifiers such that remaining data cannot reasonably be used to re-identify a user. We do this to allow for ongoing research or product improvement (e.g., retaining a gender identifier to help analyze ongoing efforts to improve discrepancies in computer science learning).
We automatically delete personal data associated with Student or Teacher accounts that have remained unused and inactive for a period of time in accordance with our data retention policies.
Managing and Deleting Other Data
Deleting your Code.org account will not delete data that you may have submitted outside of Code.org’s learning platform (such as signing our petition to support advocacy in your area) or on related services hosted by third parties such as our support forum or the teacher forum. Please send us an email at support@code.org or enter a request at https://code.org/contact if you would like to have this information deleted and we will take reasonable steps to do so.
School Users and Student Records
Code.org may be used in a classroom setting by schools, school districts, or teachers (collectively referred to as “Schools”). When the Services are used as part of a School’s educational curriculum, the personal data related to the School’s Student Users that is provided to Code.org by the School or collected by Code.org during the provision of the Services to a School, may include information defined as “educational records” by the Family Educational Rights and Privacy Act (“FERPA”) or be covered by other similar student data privacy laws, to which the School may be subject. In these cases, the Student’s personal data we collect, along with any other student records the school provides to us and any student-generated content is referred to as “Student Records” and we have implemented controls and procedures to help the Schools address their obligations under such laws. In some cases where we process Student Records, we may enter into separate agreements with Schools that supplement our Terms of Service, such as our Student Data Privacy Addendum.
Because many of our Student accounts are used for both School and non-School purposes, only personal data relating to Code.org accounts that are (1) created by a School (for example, when a Teacher creates the user name, login and password to establish the Student account, or when the teacher rosters a class using Google Classroom, Clever, or similar authentication service), or (2) created by a Student at the direction of a School or Teacher, using a School email address and associated with a Teacher’s section, are “Student Records.” Student Records do not include information a Student or other individual may provide to Code.org independent of the Student’s use of the Services at the direction of the School.
Protecting Children’s Privacy
The Code.org Services are designed for Users of all ages, including children under the age of 13 with the involvement of and pre-authorization by their school, teacher, parent or legal guardian. As a nonprofit entity, Code.org is not subject to the Children’s Online Privacy Act (“COPPA”). However, Code.org takes numerous steps to minimize the collection and use of Personal Information from children under the age of 13 as described throughout this Privacy Policy, some of which go beyond COPPA requirements, including:
If Code.org learns that it has inadvertently collected Personal Information or Persistent Identifiers from children under the age of 13 without prior parental or teacher consent, Code.org will take appropriate steps to delete this information. If you are a teacher, parent or legal guardian of a Student on Code.org, you can ask us to deactivate the Student’s account and delete any hashed email address or inadvertently collected Personal Information or Persistent Identifiers. To make such a request, please email us at support@code.org or enter a request at https://code.org/contact. Before processing your request, we may verify your identity and your relationship with the Student.
Links to Other Sites and Services
The Code.org Services may link to, and may be linked from, websites operated by other entities or individuals. Some third-party websites, such as the Code.org Facebook page and Twitter page, may be co-branded with our name or logo. Use of these third-party services are completely optional and typically meant only for adult users. These services are governed by the privacy policy of these third parties. We encourage you to review these third-party privacy policies for details about how they may collect, store, and use your personal data if you choose to engage with them.
We Do Not Allow Advertising on Our Services
Code.org does not allow advertising on our Services, and we do not have the ability to collect web search history across third-party Internet websites or search engines. However, if you navigate to the Code.org Services via a web search, your web browser may automatically provide to us the web search term you used in order to find Code.org. Because Code.org doesn’t display advertising or track browsing on third-party sites, we do not do anything different in response to “do not track” signals transmitted by web browsers.
We use the embedded YouTube player in Privacy Enhanced Mode to deliver computer science videos within our curriculum. This means that YouTube does not place cookies or track viewing behavior for advertising purposes. Our student-facing curriculum does not embed any YouTube videos that are not part of our curriculum. We have disabled the “rel” functionality of YouTube, which prevents the embedded YouTube player from playing related content outside of our curriculum. We have also tagged our “YouTube” videos on the site for “child-directed treatment.” Schools can also choose to block access to YouTube, in which case we use a fallback option that plays videos directly from our Services.
We offer clearly marked links to visit Facebook or Twitter to share various things such as User creations or certificates on Code.org. Using an account on these third-party social networking services is entirely at your option and under your control, and will not result in behavioral tracking of your browsing behavior on Code.org. However, because we know that these services use behavioral targeting as part of their advertising business model, on student-facing course and activity pages, we don’t offer links to these services to Students under the age of 13, or in schools that have blocked Internet access to these services.
To opt out of various forms of internet advertising by third parties, you may visit the following links: http://www.networkadvertising.org/choices or http://www.aboutads.info/choices/. If you use these tools, you will need to opt out separately for each of your devices and for each web browser on each device. If you reside in the EU, you may manage certain advertising cookies by visiting the EU-based http://www.youronlinechoices.eu/. You may also be able to limit interest-based advertising through the settings on your mobile device by selecting “limit ad tracking” (iOS) or “opt-out of interest based ads” (Android).
International Users
Our Services are operated and managed on servers located within the United States. If you choose to use our Services from regions of the world with laws governing data collection and use that differ from U.S. law, then you acknowledge and agree that you are transferring information, including personal data, outside of those regions to the United States and that, by providing your personal data on the Services, you are providing your consent to that transfer.
Rights Under the General Data Protection Regulation (GDPR)
If you are an individual in the European Economic Area (EEA) and you choose to use our US-based Services, we collect and process personal data about you only where we have a legal basis for doing so under the GDPR or other applicable EU laws. This means we process your personal data only where:
If you have consented to our use of personal data for a specific purpose, you have the right to change your mind at any time, but this will not affect any processing that has already taken place. When we are using your personal data because we or a third party have a legitimate interest to do so, you may have the right to object to that use though, in some cases, this may mean no longer using the Services.
If you use our Services from the EEA, your personal data will be transferred to and processed in the United States. The United States has not sought nor received a finding of “adequacy” from the European Union under Article 45 of the GDPR. Therefore, Code.org generally relies on derogations for specific situations as set forth in Article 49 of the GDPR for such transfers. In particular, Code.org collects and transfers to the U.S. personal data (1) with your explicit consent or (2) to perform a contract with you. Code.org endeavors to apply suitable safeguards to protect the privacy and security of your personal data and to use it only consistent with your relationship with Code.org and the practices described in this Privacy Policy.
In most cases, Code.org is the controller of personal data we collect and process through the Services. In some cases, however, such as where we have entered into an agreement with an educational authority to provide the Services to its students, they may be the controller and we may be their processor (in which case you should direct any requests regarding your personal data to the controller). Where we are the controller of your personal data, you have the following rights:
To exercise the foregoing rights, please contact us by sending us an email at support@code.org or enter a request at https://code.org/contact. We will consider your request in accordance with applicable law. In some cases our ability to uphold these rights may depend upon our obligations to process personal data for security, safety, and fraud prevention reasons, compliance with regulatory or legal requirements, or because processing is necessary to deliver the services you have requested. Where this is the case, we will inform you of specific details in response to your request.
Changes and Updates to Our Privacy Policy
We may update our Privacy Policy from time to time. Code.org will notify Users of any change to our Privacy Policy by posting the revised Privacy Policy with an updated date of revision on our Services. If we make material changes to the Privacy Policy we will highlight that fact with a short notice of the revision conspicuously posted on the Services homepage. We will contact Users and notify them of the changes if required by law.
We stand behind the promises we make, and will not change how we use personal data we have already collected from Users in any material way without also providing notice of the change via email, through the Services, or through other means, and obtaining consent via your continued use to any new data use policies after such notice.
Where applicable, we will not make any material changes to the Privacy Policy that relate to the collection or use of Student Records without first giving notice to the School and providing a choice before Student Records are used in a materially different manner than was disclosed when the information was collected.
What is CS Discoveries?
CS Discoveries can be flexibly taught as a single semester, two semesters over multiple years, or as a full-year course. Options are even available for less than one semester. Our curriculum is available at no cost for anyone, anywhere to teach. And, professional learning opportunities are available!
Bring CS Discoveries to your school!
Why should you teach CS Discoveries?
Engaging Curriculum
Our team designed the CS Discoveries curriculum to support students and teachers new to the discipline. The curriculum includes daily lesson plans made up of inquiry-based activities, videos, assessments, and computing tools, allowing teachers to guide and learn alongside students as they discover core computing concepts throughout the following units:
A Focus on Emerging Technologies
The CS Discoveries curriculum features a unit on artificial intelligence (AI) and machine learning (ML), which can also be taught as a standalone module. As these technologies touch more and more of our daily lives, they have become an essential part of foundational computer science education. The unit focuses on AI ethics, examines issues of bias, and explores and explains fundamental concepts through a number of online and unplugged activities and full-group discussions. Teachers can view the module here.
Extensive Teacher Resources
Professional Learning
Interested in professional learning? Find out more!
Looking for an in-depth program to help you implement CS Discoveries? Apply to join a Professional Learning Program in your region! Code.org’s Regional Partners offer hands-on, Code.org-designed workshops to thousands of eachers across the country each year.
Whether you’re brand new to computer science or an experienced teacher looking for the best way to use the Code.org curriculum, our Professional Learning Program is a great way to get started. And teachers love it! Over 90% rank it the best professional development ever.
Keep up with CS Discoveries!
Stay connected
Let us know how we’re doing!
Subscribe for the latest news
Sign up for our monthly emails, which contain the latest news about tools, videos, and other important updates for CS Discoveries.
Chat about CS Discoveries in the forum
We have forums for educators to discuss and trade ideas about CS Discoveries and talk about the curriculum. Code.org forums are used for all of our courses K-12.
Spread the word about CS Discoveries
Inspire students to enroll in the course with these resources:
Send home these fliers
Hang these posters in your classroom and around your school
Frequently Asked Questions
For answers to our most frequently asked questions, click on the questions below!
Is CS Discoveries mapped to standards?
CS Discoveries was written using both the K-12 Framework for Computer Science and the 2017 CSTA standards as guidance. Currently, every lesson in CS Discoveries contains mappings to the relevant 2017 CSTA standards. The summary of of all CSTA 2017 mappings can be found at studio.code.org/courses/csd-2022/standards. A google sheet version of the standards can be found at CSD Standards 2022.
How/Where can I get professional development for this course?
Our Professional Learning Program offers year-round support. The program kicks off with a 5-day summer workshop where you’ll have an opportunity to work hands-on with the curriculum and meet other teachers from your area. Throughout the year, we offer follow up workshops and forum support. You don’t need any prior computer science experience to get started. And teachers love it! 90% rank it the best professional development ever. Click here to apply and learn more.
Have questions about professional development? Provide your contact information to a Regional Partner in your area.
I’m teaching CS Discoveries but have less than one semester with my students. What would you recommend?
CS Discoveries consists of two semesters that build on each other. Schools can choose to teach a single semester, two sequential semesters, or a single, year-long course. Options are even available for less than one semester. See the CS Discoveries Guide to Implementation for more details.
What materials and supplies are required for CS Discoveries?
This course requires that students have access to computers with a modern web browser. Most tablets are not supported, with some exceptions requiring external keyboards. For more details, check out Code.org’s technology requirements.
In addition to computer access, you’ll need:
To learn more about getting Adafruit Circuit Playground Boards for your classroom and their software requirements, please visit code.org/circuitplayground
How can I access answer keys?
With an approved teacher account you can find answer keys in a blue «Teacher Only» panel that shows in the online lessons and activities.
Teachers in our Professional Learning Program will automatically be approved to view answer keys. If you need an approved teacher account, you can apply for access to protected teacher-only materials (answer keys, etc) through this form. Please keep in mind that it may take 3-5 business days to verify your account.
How does CS Discoveries fit with the other Code.org courses?
CS Discoveries is designed to fit naturally between our CS Fundamentals courses and our CS Principles course. While each of these courses is designed to be an age-appropriate entry point to computer science, students with previous experience will find many new topics to explore, and they will revisit familiar topics in novel and more challenging contexts.
For more information about our goals and approach to our courses, please see our curriculum values and our professional learning values.
Содержимое разработки
Методическая разработка открытого занятия
Направление: «Современный урок и внеурочная деятельность»
Ковязин Владимир Анатольевич,
Педагог дополнительного образования
Муниципальное бюджетное образовательное учреждение дополнительного образования детей
629300 ЯНАО г. Новый Уренгой
проектирование и конструирование;
поиск альтернативных творческих решений;
развитие пространственного и математического воображения;
образовательная: формировать умения и навыки проектирования и конструирования;
развивающая: развивать конструкторские навыки, творческое воображение;
воспитательная: воспитывать трудолюбие и стремление добиваться выполнения поставленной задачи.
Здравствуйте ребята! На прошлом занятии мы познакомились с понятием алгоритма, рассмотрели его основные свойства, виды и способы представления. Попробуйте ответить на следующие вопросы:
От имени какого ученого произошло слово алгоритм?
Какие свойства присущи всем алгоритм, перечислите?
Какие вам известны способы представления алгоритма?
Назовите известные вам виды алгоритмов.
Приведите пример алгоритма, который вам приходится выполнять каждый день.
Неплохо для начала, а теперь давайте перейдем к изучению нашей новой темы. Сегодня мы познакомимся с замечательным онлайн-сервисом Code.org.
Изучение нового материала.
Переходим по ссылке https://code.org/, на главную страницу нашего онлайн-сервиса.
Code.org — это игра для обучения программированию, которая была создана двумя братьями близнецами Хайди и Али Партови в 2013 году.
Мы будем изучать эту среду на самом сайте в онлайн-режиме.
Нажимаем пункт меню Каталог курсов и переходим на страницу, где представлены 4 курса по основам программирования, с учетом возрастных особенностей.
Выбираем курс, нажимаем по нему и переходим на страницу уроков и уровней. Урок представлен в форме игры.
Для усвоения урока нужно пройти все уровни, которые предлагаются.
Курс 1. Раздел «Лабиринт. Последовательность».
Выбираем Курс1, для начинающих читателей и переходим на страницу уроков. Далее выбираем 4. Лабиринт: последовательность и выбираем 1 уровень. Закрываем флешмоб и нажимаем кнопку продолжить.
Читаем инструкцию (задание), составляем нашу программу (код) и нажимаем кнопку выполнить. Если все правильно, программа предлагает перейти на следующий уровень и вверху пройденный уровень окрашивается в зеленый цвет.
Аналогичным образом проходим остальные уровни игры: 2 и 3.
Никаких трудностей при прохождении уровней не возникает благодаря тому, что разработчики сделали повышение трудности заданий максимально плавным.
Вопросы по проведённому занятию:
а) Что вызвало у вас затруднения при выполнении уровней?
б) Какой из этапов уровней вам понравился больше всего?
в) Какой полезный вывод можете сделать для себя?
А теперь попробуйте самостоятельно пройти остальные уровни игры с 4 по 15.
Результат с прохождением уровней сфотографируйте и выложите на своей страничке в инстаграмме, или в нашей группе вайбера, а мы оценим.
code-dot-org/code-dot-org
Use Git or checkout with SVN using the web URL.
Work fast with our official CLI. Learn more.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching Xcode
If nothing happens, download Xcode and try again.
Launching Visual Studio Code
Your codespace will open once ready.
There was a problem preparing your codespace, please try again.
Latest commit
Git stats
Files
Failed to load latest commit information.
README.md
Welcome! You’ve found the source code for the Code.org website and the Code Studio platform. Code.org is a non-profit dedicated to expanding access to computer science education. You can read more about our efforts at code.org/about.
To see a list of all build commands, run rake from the repository root.
Wondering where to start? See our contribution guidelines.
What’s in this repo?
Here’s a quick overview of the major landmarks:
The server for the Code.org website, a Sinatra application responsible for:
The JavaScript ‘engine’ for all of our tutorials, puzzle types and online tools. It gets built into a static package that we serve through dashboard. Though there are currently some exceptions, the goal is that all JS code ultimately lives here, so that it gets the benefit of linting/JSX/ES6/etc. Start here if you are looking for:
Research at Code.org
Code.org partners with researchers for a variety of types of studies. Researchers also conduct conduct their own work using data provided by Code.org (see below) or just on their own using Code.org materials.
Research, Papers and Reports about Code.org Materials and Programs
Research Partnerships
Anonymized data for research purposes
Numerous academic organizations have asked to access anonymized course-progress data from our Code Studio tutorials in order to research the student learning process and ideas for improving on it.
As explained in our privacy policy, when students solve coding puzzles on our platform, we save the number of tries a student takes to solve a puzzle, including the code they submit. This is how we generate progress reports for students and teachers. This same data can also help identify how to improve our tutorials.
We’re interested in exploring ways to share just the machine-level data (with no student identifying information) to allow 3rd party researchers to help us improve our service, without any risk of impact on student privacy.
If you want to help
We’d love to do a lot more in this space, and we’re limited by our own staff’s ability to support third parties. We recently hired a data engineer to help us perform our own analysis and also to support academic efforts using the same data. We’re hoping to open up more data soon.
In the meantime, we’ve done one experiment with researchers at Stanford University as explained below.
We’d like to take this further and look at what factors influence learning. For example, how do different puzzle types promote learning? How well do students transfer learning from one type of puzzle to another? How can we give students the right type of hints at the right time? What can we do to help students persist through hard problems instead of giving up? How do external factors (gender, age, class size, geography, etc.) impact student learning and what can we do to support diverse classes?
If you’re interested in working with us on these questions (and more), email research@code.org.
Data from 2 puzzles from Hour of Code 2013
Our first foray in this space has been a partnership with a Stanford University research team led by Mehran Sahami. Stanford researcher Chris Piech evaluated the various computer programs that students submitted to two computer programming puzzles from our popular Hour of Code tutorial. The dataset below was generated for the paper Autonomously Generating Hints by Inferring Problem Solving Policies by Piech, C. Mehran S. Huang J and Guibas L.
The link below is a dataset of anonymized, aggregated data of student attempts to solve these two puzzles, as explained in the readme.txt file and below. Please contact piech@cs.stanford.edu if you have questions.
A note on privacy
The dataset is FERPA compliant. It does not contain any identifiable information such as database IDs, timestamps, gender, age, or location data. Absolutely no information is included in the dataset which could be used to identify a student. For more information on how we protect private information, see our terms of service and privacy policy.
Explanation of the dataset
This is a dataset of aggregate user interaction data for logged-in users working on two computer programming challenges, Hoc4 and Hoc18 from December 2013 to March 2014. The solution to Hoc4 requires students to string together a series of moves and turns. The solution to Hoc18 requires an if/else condition inside a for loop. Submissions are collected each time a logged in user executed their code.
Description of the puzzles
Schematic of the maze and example solution for Hoc4 (left) and Hoc18 (right). The arrow is the agent and the heart is the goal.
Usage statistics on the puzzles:
| Statistic | Hoc4 | Hoc18 |
|---|---|---|
| Unique Students | 509,405 | 263,569 |
| Code Submissions | 1,138,506 | 1,263,360 |
| Unique Submissions | 10,293 | 79,553 |
| Pass Rate | 97.8% | 81.0% |
The data for each problem is split into different directories, as follows
The Abstract Syntax Trees of all the unique programs. Each file is an AST in json format where each node has a «block type», a nodeId and a list of children. The name of the file is the corresponding astId. AstIds are ordered by popularity: 0.json is the most common submission, followed by 1.json etc. The file asts/counts.txt has corresponding submission counts and asts/unitTestResults.txt has the code.org unit test scores.
Graphs
Graphs/roadMap.txt stores the edges of the legal move transitions between astIds as allowed by the code.org interface.
GroundTruth
A dataset gathered by Piech et Al to capture teacher knowledge of «if a student had just submitted astId X, which adjacent astId Y would I suggest they work towards.»
Trajectories
Each file represents a series of asts (denoted using their astIds) that one or more students went through when solving the challenge. File names are the trajectoryIds. The file trajectories/counts.txt contains the number of students who generated each unique trajectory. The file trajectories/idMap.txt maps «secret» (eg anonymized) studentIds to their corresponding trajectories.
Interpolated
We interpolate student trajectories over the roadMap graph, so that for each student we attempt to calculate the Maximum A Posteriori path of single block changes that each student went through. The file interpolated/idMap.txt contains the mapping between interpolated trajectory Ids and trajectory Ids.
NextProblem
The students who attempted and completed the subsequent challenges (Hoc5 and Hoc19 respectively). The file nextProblem/attemptSet.txt is the list of «secret» (eg anonymized) studentIds of users who tried the next problem. The file nextProblem/perfectSet.txt is the list of «secret» (eg anonymized) studentIds of users who successfully completed the next problem.
Unseen
Some ASTs do not compile in the interface and are thus not captured. This dir contains a list ASTs that do not compile but are still relevant for understanding user transitions.
рабочая программа Программирование на Code.org
Общая характеристика курса внеурочной деятельности Данная программа кружка «Программирование на Code.org» разработана для организации внеурочной деятельности обучающихся 5-х и 6-х классов. Курс построен таким образом, чтобы помочь учащимся заинтересоваться программированием вообще и найти ответы на вопросы, с которыми им приходится сталкиваться в повседневной жизни при работе с большим объемом информации; научиться общаться с компьютером. Целесообразность изучения пропедевтики программирования в игровой, увлекательной форме, используя среду программирования Codu обусловлена следующими факторами. Во-первых, в основе Codu лежит графический язык программирования, который позволяет контролировать действия и взаимодействия между различными типами данных. В среде используется метафора кирпичиков Лего, из которых даже самые маленькие дети могут собрать простейшие конструкции. Но, начав с малого, можно дальше развивать и расширять свое умение строить и программировать. Во-вторых, существенной ролью изучения программирования и алгоритмизации в развитии мышления, формировании научного мировоззрения школьников. В-третьих, занятия по программе кружка «Программирование на Code.org» подготовит их к более успешному усвоению базового и профильного курса «Информатика и ИКТ» в старших классах. Сроки реализации программы: 1 год. Программа реализует общеинтеллектуальное направление во внеурочной деятельности. На реализацию программы отводится 1 часа в неделю, всего 35 часов в год. Цель программы – способствовать формированию у школьников информационной и функциональной компетентности, развитие алгоритмического мышления. Назначение курса – помочь детям узнать основные возможности компьютера и научиться им пользоваться в повседневной жизни. Основные задачи: 1. развитие интеллектуальных, познавательных и творческих способностей школьника, способов мыслительной деятельности; 2. развитие метапредметных умений (личностных, познавательных, коммуникативных, регулятивных); 3. формирование целостной картины мира и системного мышления на основе межпредметных связей. Формы проведения занятий: беседы, игры, практические занятия, самостоятельная работа, викторины и проекты. Использование метода проектов позволяет обеспечить условия для развития у ребят навыков самостоятельной постановки задач и выбора оптимального варианта их решения, самостоятельного достижения цели, анализа полученных результатов с точки зрения решения поставленной задачи. Программой предусмотрены методы обучения: объяснительно-иллюстративные, частично-поисковые (вариативные задания), творческие, практические.
Выходные данные (библиографическая ссылка):
Code org на русском
CS 101
Udacity
In this course you will learn key concepts in computer science and learn how to write your own computer programs in the context of building a web crawler. There is no prior programming knowledge needed for this course. Beginners are welcome! At the end of this course, you will have learned key concepts in computer science and enough programming to be able to write Python programs to solve problems on your own. This course will prepare you to move on to intermediate-level computing courses.
Trilogy
Trilogy Education Services
Enroll in a Trilogy-powered bootcamp.
CompuScholar
CompuScholar
CompuScholar’s online, turn-key computer science courses enable middle and high schools to confidently teach Java, C#, Python, HTML and Unity game design skills. Student material includes instructional videos, lesson text, built-in quizzes and tests and many hands-on programming labs. Course are aligned to numerous state and national standards and come with complete teacher material, free teacher PD and dedicated support.
CompuScholar’s online, turn-key computer science courses enable middle and high schools to confidently teach Java, C#, Python, HTML and Unity game design skills.
Harvard CS50 class
CS50 is Harvard University’s introduction to the intellectual enterprises of computer science and the art of programming. Topics include abstraction, algorithms, data structures, encapsulation, resource management, security, software engineering, and web development. Languages include C, Python, SQL, and JavaScript plus CSS and HTML. Problem sets inspired by real-world domains of biology, cryptography, finance, forensics, and gaming. CS50 is Harvard’s largest course and freely available.
The most popular class at Harvard
Learn to make web pages
Intro to HTML/CSS: Making webpages
Khan Academy
Learn how to use HTML and CSS to make webpages. Through a series of interactive challenges and projects, you’ll learn how to use HTML to create headings, lists, tables, and more, plus use CSS to change the color, font, and layout of your page.
Learn how to use HTML and CSS to make webpages. Through a series of interactive challenges and projects, you’ll learn how to use HTML to create headings, lists, tables, and more, plus use CSS to change the color, font, and layout of your page.
Intro to Web Development
EduCode Academy
Enable your students to learn the basics of HTML and CSS by making delicious treats in a virtual bakery competing with Supreme Chef Horus for best honors. Our self-directed, fully immersive and fun micro-lessons and exercises using story rich videos and real world problem solving will teach and engage your students for hours with just a facilitator to help move them along.
Enable your students to learn the basics of HTML and CSS by making delicious treats in a virtual bakery.
Microsoft
Build an interactive pizza web application using Blazor, C#, and ASP.NET Core on your computer with free developer tools! Through this learning path, you’ll see the structure of a web application, learn how to interact with your pizza data, and so much more. At the end of this tutorial, you’ll know how to build fully functioning web applications and may even be able to build a website for your local pizza place.
Build an interactive pizza web application using Blazor, C#, and ASP.NET Core on your computer with free developer tools!
Learn HTML
w3schools.com
Learn to create websites on your own computer. Learn the server basics in less than a day. Learn to add databases to your website
Why should you teach CS Principles with Code.org?
It’s endorsed by the College Board.
It’s backed by research.
Six different studies show: students who study computer science perform better in other subjects, excel at problem-solving, and are more likely to attend college.
Students who take AP Computer Science Principles, in particular, are 12% more likely to enroll in college compared to similarly-situated peers, and students who take AP exams are more likely to graduate 4-year college, regardless of their score on the exam. AP computer science students also earn better AP Calculus scores than comparable students who don’t take AP computer science.
CS Principles is designed for beginners.
Our team designed the CS Principles curriculum to support students and teachers new to the discipline. The curriculum includes daily lesson plans made up of inquiry-based activities, videos, assessments, and computing tools, allowing teachers to guide and learn alongside students as they discover core computing concepts.
Every lesson plan and activity is tested by a diverse mix of classrooms around the country to make sure it’s appropriate and engaging for all students.
We support you every step of the way with extensive teacher resources.
Our Professional Learning Program comes recommended by more than 100,000 teachers.
Interested in professional learning? Find out more!
Compared with similarly-situated schools, a school’s participation in the Code.org Professional Learning program causes an estimated five-fold increase in the number of students that take, and earn qualifying scores on the AP Computer Science Principles exam. And teachers love it! Over 90% rank it the best professional development ever.
Whether you’re brand new to computer science or an experienced teacher looking for the best way to use the Code.org curriculum, our Professional Learning Program is a great way to get started.
Our approach to teaching programming: EIPM
Want to learn more about each lesson type? View our video playlist.
For more on the development of this lesson sequence, watch the video or read up on this introduction to EIPM.
Getting started with CS Principles!
Stay connected
Let us know how we’re doing
Subscribe for the latest news
Sign up for our monthly emails, which contain the latest news about tools, videos, and other important updates for CS Principles.
Chat about CS Principles in the forum
We have forums for educators to discuss and trade ideas about the CS Principles curriculum. Code.org forums are used for all of our courses, K-12.
Spread the word about CS Principles
Inspire students to enroll in CS Principles:
Send home these fliers.
Hang these posters in your classroom and around your school:
Frequently Asked Questions
For answers to our most frequently asked questions, click on the questions below!
Is CS Principles mapped to standards?
CS Principles was written using the AP CS Principles Framework and prepares students for the AP CS Principles exam. The curriculum has also been aligned to the newly revised 2017 CSTA standards. A summary of standards mappings can be found here. A google sheet version of the standards can be found at CSP Standards 2021.
How much does it cost to teach CS Principles?
Our curriculum and platform are available at no cost for anyone, anywhere, to teach!
How/Where can I get professional development for CS Principles?
Our Professional Learning Program offers year-round support. The program kicks off with a 5-day summer workshop where you’ll have an opportunity to work hands-on with the curriculum and meet other teachers from your area. Throughout the year, we offer forum support and follow-up workshops. You don’t need any prior computer science experience to get started. And teachers love it! 90% rank it the best professional development ever. Click here to apply and learn more.
Have questions about professional development? Provide your contact information to a Regional Partner in your area.
If you previously participated in the Code.org Professional Learning Program for CS Principles, your Regional Partner may be hosting a follow-up workshop to help support your transition to the new course. Please contact your Regional Partner for more details.
What is the recommended timing for teaching CS Principles?
We recommend that CS Principles be taught as a full year class, assuming that you meet with students daily or nearly daily for 45 or more minutes.
It is possible to teach CS Principles on a semester block schedule, though we highly recommend this implementation only be used in the fall semester. Since the AP Performance Tasks are due in late April and require 20 dedicated hours of class time to complete, most schools find there is not enough time to complete the course on a block schedule in the spring.
What materials do I need for CS Principles?
Required Materials:
CS Principles requires that students have access to computers with a modern web browser. At this time, our courses are not optimized for tablets or mobile devices. For more details, check out Code.org’s technology requirements.
Many lessons have handouts that are designed to guide students through activities. While these handouts are not required, we highly recommend their use.
In addition to handouts, several lessons call for specific items. You can find these listed below as well as our suggestions for alternatives:
Optional Materials
The following supplies are completely optional but will be useful to have on hand for various lessons:
How can I access answer keys?
With an approved teacher account you can find answer keys in a blue «Teacher Only» panel that shows in the online lessons and activities.
Teachers in our Professional Learning Program will automatically be approved to view answer keys. If you need an approved teacher account, you can apply for access to protected teacher-only materials (answer keys, etc) through this form. Please keep in mind that it may take 3-5 business days to verify your account.
How was the curriculum developed?
Our CS Principles curriculum has always been designed as part of a broader vision of supporting high quality, engaging, and equitable computer science instruction in classrooms across the country. Our Curriculum Values continue to guide us, and in particular our focus on expanding access to those who historically have been denied opportunities to learn about the exciting and impactful field of computing.
While our vision and values remain unchanged, the landscape of CS education is rapidly developing. For the 2020-21 school year the College Board has made some significant updates to the CS Principles framework and AP assessment to ensure that CS Principles remains relevant and aligned with equivalent university courses. CS education research continues to reveal new insights on how students learn about computing, and feedback from the thousands of classrooms now using our CS Principles curriculum has identified opportunities to further improve our courses, tools, and recommended pedagogy. The goal of the updates to our curriculum is to navigate these developments in a way that remains committed to our vision and values and supports the many teachers, schools, classrooms, and districts that are already a part of our broader CS Principles community. We remain deeply thankful for you joining us on this mission to make our collective vision a reality.
For more information about our goals and approach to our courses, please see our curriculum values and our professional learning values.
Beyond CS Principles: Standalone AI Module
Artificial intelligence (AI) and machine learning (ML) are shaping the world around us. As these technologies touch more and more of our daily lives, they have become an essential part of foundational computer science education. In this standalone module, which spans roughly 5 weeks, students can learn the fundamentals of these technologies and discuss their ethical implications.
AP® is a registered trademark of the College Board.
My name is Mei’lani. I’m an intern at code.org and I’m also a computer science student. I like computer science because it’s really creative. I get to be the problem solver. I get to make everything function how I want it to. But I also get to be the designer. I get to be the artist and choose everything on the creative side of it.
Making your own apps is easy with App Lab! Whether you’re new to coding or have some experience. App Lab is a great tool for building new apps and sharing them with your friends.
This is a App Lab. On the left side is your app. On the right side is the code that will make it run. You build your program by dragging in blocks from the toolbox. To start you’ll just have one block called ‘setProperty’.
The set property block changes the look of the elements on your screen. Like the buttons, labels, or even the screen itself. First you need to decide which element you want to change. If you hover over an element in your app you can see the name or ID here. Then go select that ID from the first drop down.
Elements have lots of properties you can change like their text color, background color or font size. You can see the full list and choose which property you want to change in the second drop down.
The last drop down is where you’ll write the value you want to use value you want to use. The block will make a suggestion for you. But you can always type in different colors or numbers yourself.
Once you’re done, the block reads a bit like a sentence:’Set button1’s background color to green.’ Hit run to see the changes you’re building in code. If you reset you can drag in more blocks to change other things about your app. Like the text!
For this tutorial we’ll be working in block mode but App Lab also supports working in text.
Either way you’ll be programming in JavaScript, the language of the web. Each level has a goal, instructions and an image of what you’re aiming to create.
If you’re ever stuck, click on this picture and it will show you exactly how to complete the level. But see if you can do it on your own first.
Once you’ve completed the goal for this level click Finish to move on. That’s all there is to it! Hit the orange «continue» button to go to the next level and start your adventure with an App Lab!
Code org на русском
Обновлено: 2 года назад
Обновить
Добавить в избранное
Скачать отчёт в pdf
Заголовок: Learn computer science. Change the world. | Code.org
Описание: Нет
Рекомендации по оптимизации сайта:
— Уменьшите время ответа сервера, желательно, чтобы это значение не превышало 200 миллисекунд.
— Для ускорения индексации, добавьте в корневую папку файлы sitemap, где укажите все индексируемые страницы вашего сайта.
— Добавьте сайт в новостные агрегаторы, это увеличит количество посетителей.
— Удалите или закройте c nofollow ссылки на другие сайты.
— Создайте группы сайта в социальных сетях.
— Внесите в HTML код атрибуты alt у 15 изображений.
— Удалите из исходного кода страницы лишние пробелы, табуляции и переносы строк.
— Добавьте метатэг viewport в код страницы, это позволит правильно масштабировать страницы сайта при просмотре в мобильных браузерах.
— Удалите код подключения JavaScript и CSS, блокирующий отображение верхней части страницы. Страница начинает отображаться, только после загрузки этих файлов.
— Отключите отображение версии сервера, операционной системы.
— Добавьте к записям DNS сервера TXT(spf) запись с указанием настоящих серверов отправки почты.
Яндекс
Citation Flow 43
Trust Flow 48
| Проверка наличия в каталогах: | Санкции поисковых систем: | ||
| Нет | |||
| Нет | |||
| Ссылки с форумов и блогов: | Проиндексированные изображения: | ||
| Другое: | |
| Активность в соцсетях 77 | 13 |
 | с 15 Июля 1997 |
| Нет | |
Learn computer science. Change the world. | Code.org
Мы нашли 128 ссылок со страницы.
Внутренние ссылки: 58
Ссылки на другие сайты: 70
Открытые ссылки: 66
Ссылаются на 1 доменов:
Анализ SSL сертификата:
SSL сертификат соответствует доменному имени сайта.
Для сайта code.org найдены: 18 поисковых запросов в Яндекс. Средняя видимость в поиске Яндекса: 44%
Страницы с лучшей видимостью в поиске Яндекс: