Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorporate Docker-specific instructions and educational content into README.md #74

Merged
merged 37 commits into from
Jan 11, 2025
Merged
Changes from 1 commit
Commits
Show all changes
37 commits
Select commit Hold shift + click to select a range
022934a
Update to README.md (multiple sections)
GrahamLeach Dec 27, 2024
db55af1
Tag archive removed from end of README.md
GrahamLeach Dec 27, 2024
dd2909d
Extensive changes to README.md - simplified and semi-finalized
GrahamLeach Dec 28, 2024
c8b738c
Cleaned up README.md, removed first heading (redundant)
GrahamLeach Dec 28, 2024
227925e
missing word (it)
GrahamLeach Dec 28, 2024
b6e6f1e
Tightened Docker section
GrahamLeach Dec 28, 2024
f9667db
Fixed some typos
GrahamLeach Dec 28, 2024
a5a7398
Fixed some typos
GrahamLeach Dec 28, 2024
4eec962
Adjusted messaging of Compatibility section
GrahamLeach Dec 28, 2024
49bee3c
Adjusted What is Backdrop section
GrahamLeach Dec 28, 2024
378800c
README.md messaging tweaks
GrahamLeach Dec 28, 2024
a2d3cd2
README.md messaging tweaks
GrahamLeach Dec 28, 2024
3c19f80
README.md messaging tweaks
GrahamLeach Dec 28, 2024
0ddd821
README.md messaging tweaks
GrahamLeach Dec 28, 2024
1d8374e
added to gitignore
GrahamLeach Dec 28, 2024
6767aca
Delete README.md.backup
ProfessorGram Dec 28, 2024
333c084
Removed TAGS section (saved as fragment elsewhere)
GrahamLeach Dec 28, 2024
34b5e6f
Added compose.yml
GrahamLeach Dec 29, 2024
c80ad45
Delete docker-compose.yml
ProfessorGram Dec 29, 2024
ad9968f
Added ToC to README
GrahamLeach Dec 29, 2024
0ad0557
Updated README
GrahamLeach Dec 29, 2024
291ea16
Updated README
GrahamLeach Dec 29, 2024
689e783
Updated README
GrahamLeach Dec 29, 2024
58c0d26
Updated README
GrahamLeach Dec 29, 2024
7fb145d
Updated logos in README
GrahamLeach Dec 29, 2024
45b7ff8
Removed typo in README
GrahamLeach Dec 29, 2024
ef824d6
Re-wrote initial section
GrahamLeach Dec 29, 2024
2a9e309
Removed extra text
GrahamLeach Dec 29, 2024
9af5637
changed compose.yml to fix container_name reference
GrahamLeach Dec 29, 2024
6e8672c
added :latest to mysql image
GrahamLeach Dec 29, 2024
96843b9
updates to README
GrahamLeach Dec 29, 2024
2eeab27
updated README.md file
GrahamLeach Dec 29, 2024
6cb6dc6
updated README.md file
GrahamLeach Dec 29, 2024
3fe46d8
updated README.md file
GrahamLeach Dec 29, 2024
76408bf
Update README.md
diraneyya Jan 3, 2025
ae8babb
Update README.md
diraneyya Jan 3, 2025
a5cd17c
Merge branch 'master' into patch-1
diraneyya Jan 3, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
README.md messaging tweaks
GrahamLeach committed Dec 28, 2024
commit 3c19f80fc3258a6ac074f577cf0958c94b1c0933
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -23,7 +23,8 @@ Many production Drupal websites are currently deployed on an "unsupported" versi


## Compatibility
The Backdrop leading principle of compatibility resulted in the creation of a "Drupal compatibility layer" in Backdrop early on. This important and highly useful development has become a "secret weapon" for Backdrop because, with only slight alteration, the vast majority of "unsupported" Drupal code is able to run in a supported version of Backdrop. This is especially true for Drupal 7 code, as that was what Backdrop was derived from, and is the version of Drupal for which Backdrop offers the highest degree of compatibility. Another reason why Backdrop selected Drupal 7 as its basis was pragmatic: The Drupal 7 ecosystem is massive, with over 16,000 contributed modules and themes. This staggering amount of innovation was the result of over a decade of distributed development by thousands of dedicated and loyal developers, agencies and companies that relied on Drupal 7 for their everyday livelihood. The result of ths collective effort is a body of work comprised of over 150,000 individual pieces of freely available intellectual property that range across every conceivable organizational model and business problem...and all of them are available to Backdrop.
The Backdrop principle of compatibility resulted in the creation of a "Drupal compatibility layer" in Backdrop very early in its evolution. This highly useful Backdrop feature has become a bit of a "secret weapon" because "unsuppoted" Drupal code needs only to be slighty altered to then be hosted in a fully supported version of Backdrop. This is especially the case for "unsupported" Drupal 7 code, as that was the base product from which Backdrop was derived. The selection of Drupal 7 as the basis for Backdrop was no accident. When Backdrop was launched, Drupal 7 was the latest and most popular version of Drupal, with the best-developed ecosystem of contributed modules and themes. Today, over a decade later, the Drupal 7 ecosystem is simply massive, with over 16,000 contributed modules and themes. This staggering amount of innovation has resulted from a distributed development model supported by thousands of dedicated and loyal developers, agencies and companies that relied on Drupal 7 on a daily basis. The result of ths collective effort is a body of work comprised of over 150,000 distinct pieces of freely available intellectual property that range across every conceivable organizational model and business problem...and all of them are available to Backdrop.


## Cost of Adoption
Converting a Drupal website to Backdrop can take a fraction of the time and expense required to migrate to other CMS systems (Wordpress, Magento) or to move onto a cloud-based solution (WIX or Shopify). Most notably, a Drupal to Backdrop conversion is often faster and cheaper than a Drupal to Drupal upgrade - mostly due to how complicated more recent versions of Drupal have become. To date, hundreds of organizations have chosen Backdrop because they have concluded that Backdrop is the fastest, easiest and least expensive way for them to move forward.
8 changes: 6 additions & 2 deletions README.md.backup
Original file line number Diff line number Diff line change
@@ -23,10 +23,14 @@ Many production Drupal websites are currently deployed on an "unsupported" versi


## Compatibility
The Backdrop leading principle of compatibility resulted in the creation of a "Drupal compatibility layer" in Backdrop early on. This important and highly useful development has become a "secret weapon" for Backdrop because, with only slight alteration, the vast majority of "unsupported" Drupal code is able to run in a supported version of Backdrop. This is especially true for Drupal 7 code, as that was what Backdrop was derived from, and is the version of Drupal for which Backdrop offers the highest degree of compatibility. Another reason why Backdrop selected Drupal 7 as its basis was pragmatic: The Drupal 7 ecosystem is massive, with over 16,000 contributed modules and themes. This staggering amount of innovation was the result of over a decade of distributed development by thousands of dedicated and loyal developers, agencies and companies that relied on Drupal 7 for their everyday livelihood. The result of ths collective effort is a body of work comprised of over 150,000 individual pieces of freely available intellectual property that range across every conceivable organizational model and business problem...and all of them are available to Backdrop.
The Backdrop principle of compatibility resulted in the creation of a "Drupal compatibility layer" in Backdrop very early in its evolution. This highly useful Backdrop feature has become a bit of a "secret weapon" because "unsuppoted" Drupal code needs only to be slighty altered to then be hosted in a fully supported version of Backdrop. This is especially the case for "unsupported" Drupal 7 code, as that was the base product from which Backdrop was derived. The selection of Drupal 7 as the basis for Backdrop was no accident. When Backdrop was launched, Drupal 7 was the latest and most popular version of Drupal, with the best-developed ecosystem of contributed modules and themes. Today, over a decade later, the Drupal 7 ecosystem is simply massive, with over 16,000 contributed modules and themes. This staggering amount of innovation was the result of over a decade of distributed development by thousands of dedicated and loyal developers, agencies and companies that relied on Drupal 7 for their everyday livelihood. The result of ths collective effort is a body of work comprised of over 150,000 individual pieces of freely available intellectual property that range across every conceivable organizational model and business problem...and all of them are available to Backdrop.

and therefore is the version that typically requires the least conversion effort to function correctly in Backdrop.



## Cost of Adoption
Converting a Drupal website to Backdrop can take a fraction of the time and expense required to migrate to other CMS systems (Wordpress, Magento) or to move onto a cloud-based solution (WIX or Shopify). Most notably, a Drupal to Backdrop conversion is often faster and cheaper than a Drupal to Drupal upgrade - mostly due to how complicated more recent versions of Drupal have become. To date, hundreds of organizations have opted to move over to Backdrop because they have concluded that Backdrop is the fastest, easiest and least expensive way forward for their organization.
Converting a Drupal website to Backdrop can take a fraction of the time and expense required to migrate to other CMS systems (Wordpress, Magento) or to move onto a cloud-based solution (WIX or Shopify). Most notably, a Drupal to Backdrop conversion is often faster and cheaper than a Drupal to Drupal upgrade - mostly due to how complicated more recent versions of Drupal have become. To date, hundreds of organizations have chosen Backdrop because they have concluded that Backdrop is the fastest, easiest and least expensive way for them to move forward.

## Track Record
Since 2013, Backdrop has remained true to its key principles. Today, the Backdrop story is marked by a series of increasingly significant achievements. Backdrop has always been continually improved, and keeps up to date with the latest developments in web technology and approaches, including DLT and AI. Backdrop is upgraded in a predictable and methodical way, with planned updates occurring every six months. Major releases of Backdrop have been (and will be) supported for an extremely long time. New Backdrop functionality is arriving ever more frequently as more and more Drupal modules are converted. Finally, Backdrop has a proven, dedicated, mature, experienced and highly professional project team.