I have been in IT for over 10 years. I can code in several languages (shell, perl, python, apple script, etc) but am not a web developer. Drupal uses a lot of industry terms that have different meanings, or uses existing technology found in enterprise IT, but has a totally different name for it. Relationships are like parent/child configurations, the whole theory of a trunk and branches has the same thing in directory services and LDAP. You have a tree and leaf items that branch off your tree.
There was mention of the boot strap and no one touched on it. I guess I would like to understand the core under the hood processes that go on with drupal and where to look at to customize certain simple things out of the box.
I know php, but barely, and I know html, but also barely as well as CSS just a bit. If anyone is interested in collaborating with some fundamentals and maybe even a few easy projects to get the hang of it, I would be down to go. This will also of course broaden the user base of drupal as those that do not know what it is could attend such meetings.
This weekend if I get time I am going to read through the API and find out exactly what drupal is doing under the hood so I understand how it works.
Submitted by JohnStone on Wed, 02/24/2010 - 12:29pm.
my brother would love this level of discussion but for me in particular : I am a designer trying to use drupal as an out of the box basic website builder.
Using W@#$P#@$$ ;) currently because of it's simple static CMS nature.
I'd like to start using drupal however for it's ability to be future-rooted (i.e. someone could come in later and really tweak it).
So anything to help me use drupal as an out-of-the-box turnkey website maker would be great. I understand though that this is NOT the intention of the regular Drupal group.
This is one area Drupal has a bit of an identity crisis, even among its core developers. Some consider it a CMS and others consider it a platform to be developed on. The first group think custom coding should be optional and not required for typical use, the second group consider it a fact of life.
Perhaps this would be a good discussion for in the forum and then a presentation could be flushed out of that discussion?
Submitted by gregrenner on Wed, 02/24/2010 - 3:47pm.
Why can't it be both? A Content Management Framework that can be used out of the box, with Contrib modules and then also a base framework for developers to build from. It gives both user types what they want.
drupal
I have been in IT for over 10 years. I can code in several languages (shell, perl, python, apple script, etc) but am not a web developer. Drupal uses a lot of industry terms that have different meanings, or uses existing technology found in enterprise IT, but has a totally different name for it. Relationships are like parent/child configurations, the whole theory of a trunk and branches has the same thing in directory services and LDAP. You have a tree and leaf items that branch off your tree.
There was mention of the boot strap and no one touched on it. I guess I would like to understand the core under the hood processes that go on with drupal and where to look at to customize certain simple things out of the box.
I know php, but barely, and I know html, but also barely as well as CSS just a bit. If anyone is interested in collaborating with some fundamentals and maybe even a few easy projects to get the hang of it, I would be down to go. This will also of course broaden the user base of drupal as those that do not know what it is could attend such meetings.
This weekend if I get time I am going to read through the API and find out exactly what drupal is doing under the hood so I understand how it works.
-Tom
Drupal Bootstrap
Check out pg 9 for Drupal Bootstrap details. This book is a must have for techies like yourself, Tom.
http://books.google.com/books?id=VmZrdGuBZCMC&lpg=RA1-PR29&dq=google%20b...
I may not be a good candidate
my brother would love this level of discussion but for me in particular : I am a designer trying to use drupal as an out of the box basic website builder.
Using W@#$P#@$$ ;) currently because of it's simple static CMS nature.
I'd like to start using drupal however for it's ability to be future-rooted (i.e. someone could come in later and really tweak it).
So anything to help me use drupal as an out-of-the-box turnkey website maker would be great. I understand though that this is NOT the intention of the regular Drupal group.
Split Identity
This is one area Drupal has a bit of an identity crisis, even among its core developers. Some consider it a CMS and others consider it a platform to be developed on. The first group think custom coding should be optional and not required for typical use, the second group consider it a fact of life.
Perhaps this would be a good discussion for in the forum and then a presentation could be flushed out of that discussion?
Why can't it be both? A
Why can't it be both? A Content Management Framework that can be used out of the box, with Contrib modules and then also a base framework for developers to build from. It gives both user types what they want.
I agree, that is the
I agree, that is the definition of a framework, some tools you use to accomplish your overall goals.