FAQ - Freequently Asked Questions + Glossary

Post status: [unfinished.public.draft]
(Any errors will be corrected as we move on. You may send your feedback about this page, more questions, or the like using the contact form.)

[PS. Please bear with us, this is just an initial FAQ/Glossary, which will probably be structured differently when we have the first content structure specification ready. For now we just use one normal page for this.]

(August 2016) PS. You may be adviced to cross-check the information on this FAQ against the latest updates on the About page..!

Glossary

  • Components: since in the long run we are going to address more than 1 CMS here at content.cat, we will use the term "component" as the general term to refer to both modules, plugins, themes, libraries, and the like. With the initial two-fold focus on Drupal and Wordpress, we already have the terms "modules" and "plugins" meaning technically the same.
  • Premium community: paid membership, or earned membership. We will be maintaining a comprehensive list of tasks where it is possible to earn one's way into a membership without having to do a money transfer. This is currently pending discussion and decisions about how we are going to measure the value on tasks. Feel free to provide suggestions and feedback in the main thread at drupal.org (see the link on the front page).

(why/how) Will it be worthwhile for participants to contribute?

  • we will use community voting and rating along with both bounties and direct funding support from the content.cat membership payments, to finance bugfixing and feature requests for the components we decide to take under our wings. This moneywise funding will mainly be focused on two aspects: a) stability maintenance (within the scope of our "pool of components", which we are guessing will be over 300, possibly graded on more than one level* (a separate post will address this challenge)), and b) Content Management flexibility features.
  • over time, more and more small and medium sized businesses will learn the value of finally having a solid, stable and long-term focused platform with sufficient flexibility for common types of web sites. We are aiming at convincing more and more people that YES, it is actually a costly experience only to be free-floating down the open-source stream, and YES, in the long run it will be LESS costly to commit more seriously in a joined community effort to finance a whole platform than to just chip in here and there and most likely never get the security of confirmed and committing long term views.
  • anyone can choose not to pay and still benefit; everything that passes our quality control will be posted back to the original, free community. This will be delayed perhaps roughly 3-6 months due to the quality control moderation process. Members of the community can watch the progress of those issues all along their process, and non-members will see them when they have been posted on the original community site (example: drupal.org). This will be both documentation, patches, component versions, themes, theme adjustments, etc. A major part of the collaboration on these contributions will be done in the original issue queue at for example drupal.org, available to all. The decision making, subsequent documentation, validation, and also initial funding and priority discussions will be done with dedicated community tools here at content.cat. For the professionals, we are betting that it will be economically (and profesionally) worthwhile to be a member, with all the attention and direct access to resources the membership brings. For small projects, non-profits, etc. that are ok with staying 3-6 months behind the current development, the ride will be free, all verified parts will be available from the main repositories at for example drupal.org.
  • we will have several membership types, and evaluation and rating on each member, with membership profiles, member goals, learning stage, etc. It will be possible to earn rating at a level where one can offer oneself as paid assistance to others, with our quality meter reflecting some credibility and such aspects. There will be several good professional reasons as why these memberships will be worth the initial cost. We aim to make it just that: an initial cost that will subsequently materialize for each member as a source of more revenue, more efficiency, less insecurity, more stability, etc. All for the benefit of any project or individual that decides to use these components for their web sites.

Does this also include paid work for real money, not just userpoints?

  • Yes. It is at the heart of this community to collaboratively decide, prioritise and finance this work. We will have various levels of importance, obviously, some work will still be on volunteer basis, but the more members we get, and the more work we finishes along the path to real platform stability, the greater the percentage of paid work will be.
  • Please note that one of the main functions of userpoints is to avoid blocking the entry for people that lack financial resources but have enough other resources such as time, competence, structure, etc. to contribute with.

How will each task / issue be funded? (process before work starts)

  • we will initially work out a list of outstanding tasks that for various reasons have been stalled for long time without progress in the original communities. From that list, we will start voting and rating importance, costs (timewise/moneywise), aligning with roadmaps, contact current maintainers to determine if the direction is agreeable or not, and then use bounties and direct sponsorships to cover the final specification for each issue. A good example is the "comment mover" module at https://www.drupal.org/project/comment_mover, which is crucial for flexible Drupal Content Management, yet have not until now had a stable architecture to base its development upon. One can learn a lot about the reality of open-source development and dilemmas by taking a look at the lifespan of that module in comparison with the architectural changes each Drupal version has undergone. That module may serve as a miniature example of why we mean the current state of Drupal warrants a LTS release, freezed at D7.

How will userpoints be converted to time or membership level payment?

  • We are having that discussion now. There are several things to consider. We invite you to offer your insights and suggestions through the contact form and/or over at Drupal.org / BackDropCMS.org / Wordpress.org until our forums are up. (Depending on the topic, some of these discussions may belong permanently in one or more of those external forums.)

Why the focus on Drupal and Wordpress, why no others, or why not just one?

  • This is the start of a very long term community. We aim to stay here long after the next 10 years. We have honestly no idea as of which Content Management System or platform we will be using later, after these initial 10+ years. Therefore, we are focused on the main two systems, one with unparallelled flexibility and API framework (Drupal), and one as an equally unparallelled "front-end site" (Wordpress), currently (still) lacking some of the under-the-hood power architecture that Drupal offers. We dont mind stand corrected if this position is wrong or shifting in the future, but we need both: We really need good architecture at the bottom, with significant flexibility. We still dont see WP as a real Drupal contender in that "flexible architecture" space.
  • On the other hand, there are a significant amount of great layouts/presentations/front end stuff on WP where Drupal still needs to catch up on. As a simplification, we think of Drupal as the engine for services and framework for complex community sites and professional blogs, possibly even powering some WP content features, for example through the https://www.drupal.org/project/feeds module, and WP for the "blog" and "front layout" presentation layer. We are not yet sure if it is a necessary reality that Drupal is lacking great themes to such a degree that it stands far behind WP, at least in the free themes area. Among the "components" we will maintain here are the porting and maintenance of several open-source WP themes, in particular a selection from http://www.elegantthemes.com . We will contribute back to both communities in the development and maintenance of the selected themes.

What is the main purpose(s) of this community?

  • (Update, August 2016; see the About page..!)
  • We have long been agreeing on the expression "Content is King". However, the current state of affairs in the content realm of tools is not very impressive. We are not very advanced or impressive, really. Now it is 2015, and high time to get a solid CM platform in place. We need a long term platform where we can develop the content-centric features and not only "the system". This take a lot of effort. We cannot have a continuously moving architecture "target", as we need several years to fine-tune content features once we have a stable and flexible platform. Therefore this 10-year scope ("D7LTS15"), which will provide that. (See also https://twitter.com/hashtag/D7LTS15 )
  • So CONTENT features is our main focus here, more than the underlying "platform". We will maintain the system as a stable platform, then focus our efforts on more and more flexibility and ready-made configurations for all sorts of CM features.
  • That said, we also need to present that content, both with flexibility, multiple layers, languages, and layouts/themes.
  • And during the process from draft to published content, we need quality control in terms of revisions and moderation, both for main content, categories, metadata, and more. The invisible content stage(s) before something is published to the wider audience are equally important when dealing with content. Some sites may be closed from the public, but still need such tools, and others may be so open that they post "drafts" openly (like this very FAQ page here), and that too needs various content features such as revisions display, version comparisons, etc..