too late to make it make sense
This commit is contained in:
parent
d136a42635
commit
d2f2c5cb7e
1 changed files with 52 additions and 6 deletions
|
@ -17,6 +17,9 @@ Why not WordPress or Backdrop or Ghost or Grav or Jekyll or Hugo? Why not Ruby
|
|||
* Faceted search
|
||||
* Fine-grained permissions
|
||||
* Development workflow that's not just editing configuration on live
|
||||
* The possibility of building most any functionality into the site
|
||||
* The ability to both read and write to APIs, cognizant of your data model
|
||||
* Use what you know
|
||||
|
||||
What are your reasons?
|
||||
|
||||
|
@ -41,27 +44,64 @@ Approaches:
|
|||
|
||||
### Distributions
|
||||
|
||||
* Restaurant
|
||||
* Small business
|
||||
What kind of site are you trying to build? There may be something that gives you a start.
|
||||
|
||||
* Restaurant site, with [Open Restaurant](https://www.drupal.org/project/openrestaurant)
|
||||
* Small business site, with [Druppio](https://www.drupal.org/project/druppio_small_business_distribution )
|
||||
* Online magazine or newspaper, with [Thunder](https://www.drupal.org/project/thunder )
|
||||
* Community site allowing active subgroups, with []( )
|
||||
* Online community site allowing active subgroups, with [Open Social](https://www.drupal.org/project/social )
|
||||
* Church site, with [OpenChurch](https://www.drupal.org/project/openchurch )
|
||||
* Corporate site, with [Droopler](https://www.drupal.org/project/droopler )
|
||||
* Learning management system, with [Opigno LMS](https://www.drupal.org/project/opigno_lms )
|
||||
* Research and grant management, with [Niobi](https://www.drupal.org/project/niobi )
|
||||
* Government sites, [GovCMS](https://www.drupal.org/project/govcms8 )
|
||||
* Volunteer coordination, with [Volunteer Center](https://www.drupal.org/project/vc )
|
||||
* and [more](https://www.drupal.org/project/project_distribution?f%5B0%5D=&f%5B1%5D=&f%5B2%5D=drupal_core%3A7234&f%5B3%5D=sm_field_project_type%3Afull&f%5B4%5D=&f%5B5%5D=&text=&solrsort=ds_project_latest_activity+desc&op=Search )
|
||||
* including [Varbase]( ), a sort of generic starting point.
|
||||
* including [Varbase](https://www.drupal.org/project/varbase ), a sort of generic starting point.
|
||||
* and of course, for a grassroots group, [Drutopia](https://www.drupal.org/project/drutopia ).
|
||||
|
||||
You can take any one of these distributions, and build your site on it. It can give you a big head start. It may bring some headaches, too, but, that's Drupal. That's web development. That's life. Still, grab and hack, which is a reason to start with a product-and-a-framework in one, a content management system and a framework in one like Drupal, in the first place, can give your small site a boost. If you change
|
||||
|
||||
### Drutopia's approach to distributions
|
||||
|
||||
#### Swappable pieces
|
||||
|
||||
With Drutopia we also tried to go a bit further to make it a flexible distribution that can be built on.
|
||||
|
||||
We didn't go as far as i would have liked, which would be to make the idea of a base distribution obsolete. I wanted to explode every requirement into its tiniest component part: Does a feature need a given role? It depends on a feature module that provides that role, and nothing else. An image style? Same thing, a feature module providing just that image style.
|
||||
|
||||
Reasonably rejected as impractical, we still went to a lot of work to be able to
|
||||
|
||||
But not many heeded our call, and distributions are essentially incompatible with each other.
|
||||
|
||||
#### Upgradeable
|
||||
|
||||
The other thing we (read: Nedjo Rogers) put a lot of time into is trying to make it so that when
|
||||
|
||||
|
||||
####
|
||||
|
||||
|
||||
## Growing big enough that the bumps seem tiny
|
||||
|
||||
All of these are big dreams, that to do well, requires resources. Which is why part of our dream is to get big.
|
||||
|
||||
And one way to get big, and *also* to immediately benefit smaller sites, is to provide websites as a service.
|
||||
|
||||
### SaaS
|
||||
|
||||
* Localeyz, a Drupal-based service for local media, but their code is not shared as far as i can tell.
|
||||
Software as a Service is of course a huge business. You probably use accounting software, timetracking or invoice software, or something else that runs on someone else's computer and you actually pay for. And then there's the social media (Facebook and Twitter), office suites (Google Docs and Google Calendar), and the like that we might not pay for with dollars, but we're giving our data.
|
||||
|
||||
More in the website space:
|
||||
|
||||
* Wix, Squarespace, Weebly, etc.
|
||||
* Salesforce
|
||||
* Pantheon
|
||||
|
||||
And we have Software as a Service in the Drupal world, too:
|
||||
|
||||
* Pantheon, almost devops as a service
|
||||
* Acquia, not so much on the hosting tools but with proprietary Drupal enhancements
|
||||
* Localeyz, a Drupal-based service for local media, but their code is not shared as far as i can tell.
|
||||
|
||||
|
||||
### Distributions + SaaS == LibreSaaS
|
||||
|
@ -229,3 +269,9 @@ Failed to be community-first. Not sure that's possible but that's what i'd like
|
|||
join the actually-existing federated social web
|
||||
|
||||
That's what [Mastodon did](https://blog.joinmastodon.org/2018/06/why-activitypub-is-the-future/ )
|
||||
|
||||
|
||||
|
||||
# Transparency does not equal democracy
|
||||
|
||||
The concentrated benefit, diffuse cost conundrum helps explain a mystery uncovered by James D'Angelo: that the move to public votes in the US House of Representatives in 1970 increased the power of big donors, lobbyists, and political parties. Before, when most votes were secret, representatives had the option of lying to their donors, to lobbyists, to party "whips", and thus to vote their conscience.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue