10
xic3fox
7d

I just found this when I updated my profile.

Guess what? Drupal is actually my facorite CMS nowadays 😂

Comments
  • 0
    You have been very quite since then :D
    Why is drupal your fav cms? My team is considering to switch to drupal...
  • 1
    @ynnk Drupal is super flexible, super customizable, super scaling and you can use it for almost everything, from a small blog over a backend an app is communicating with to a very complex web application.
    Drupals biggest plus is the quite infinite dynamic. You can build almost everything completely dynamic, not like Typo3 where you create static pages.
    To be fair, Drupal is also super complex and quite hard to understand in the beginning. You need to take your time to understand how Drupal work and where you can hook in to insert your custom logic.
    But in my opinion I think you will never wamt to work with other CMS like WordPress or Typo3 if you have learned Drupal :)
  • 1
    6/8/17 95 points
    4/11/19 105 points

    HOW ARE YOU SO NINJA
  • 0
    @toriyuno I just have not been using devRant for quite a while :D
  • 0
    TYPO3 doesn't create static pages?!
    Curious how the pages concept works in Drupal.
    From what i heard, a page is a "node". A node is a record and can have any type like page, cotent etc.
    right?
  • 0
    @cephei as far as I know Typo3 creates static pages but I can be wrong :)

    Right, there are nodes and you can define as many node types as you want and give them fields and so on.
  • 0
    @xic3fox you'd have to install a third party extension to typo3 to serve static pages.

    So i guess Drupal is quite flexible to create custom records. Is there like a JSON (or similar) config file where you can define how a field should be rendered?
    e.g. the node 'page' has a field 'title' that should be displayed as input [text] and allow max. 30 characters.

    And this config would create the SQL and the GUI?
  • 1
    @cephei okay, we probably have that extension for our Typo3 systems but I'm not sure 😅

    Well, you have a config folder for like everything thats configurable (nodes display, nodes form dislay, field settings, etc.) and the single config files are in yaml format. I don't how Drupal builds the SQL queries exactly but I know that the GUI is buikt by twig templates you define in your themes.

    These configs are normally generated by what you do in the backend. When you add a field of the type 'text' to a node it will be put into the config.

    As I'm typing this I remember that the config files you can ex- / import are just a 'copy' of whats inside the config table in the database. In production you should never configure anything by yourself, import the configurations instead.
  • 1
    @xic3fox thanks for the elaboration. i might look into it some day :)
Your Job Suck?
Get a Better Job
Add Comment