puddle
puddle

Maybe some of you used Drupal and theres one feature I loved there which is that you can promote any content of any content type to the front page which is kind of an article feed (another content type). Drupal is very slow on shared hosting especially and I love laravel so I would like to start using October but there are still a lot to learn and some stuff is consfusing atm for me. Anyways this feature in Drupal allows you to have a news feed and occasionally promote content from another content type to the article home page like you have a new product with description and you dont want to post it twice to be able to post it on the front page aswell to let the users know about this new product... This is one thing I am thking about how to do it in October. Also I would like to be able to display related content on the same page, so for example if you have a gallery which has on or more artists and every artist has one or more gallleries, I would like to have a page to display each gallery and also present info about the artist and vica versa, I need a page to display each artists and their related galleries. I do not want to ask you for a full solution, I will do that myself but I do not know October too much (yet) so I dont have a complete concept on how to do this. Could you give me directions on how I should go about implementing these features? It would be much appreciated, thank you!

philipptempel
philipptempel

I did use Drupal once - I didnt' like it. But that was a few years ago.

But to give you an answer to your question: Yes, it sounds like it could be done in OctoberCMS, too. To me it merely sounds like a question of how you define your backend/models since all this sounds like a rather model-specific task than something frontend-targeted. This means that you will have to define multiple database models for your content types that do what they'd usually do. With a field is_promoted or so you could mark these items as promoted to the frontpage. For the frontpage you'd have a non-database model which retrieves all the content from other models then sorts that according to some needs. Finally, this data is passed to a component which renders all the stuff. Your galleries example would work similary. You need to ask yourself: how can these questions be answered in terms of SQL-queries or model relationships or something like that.

Maybe you also want to have a look at Drupal source code to see how it's implemented there? Or head over to the Plugins Section of OctoberCms and look through source code of free plugins to see what you can do somehow. Also, you definitely want to read the docs and I can highly encourage you to look through all the other resources. Especially Sam's screencasts were very helpful to me to get my learning curve steep ;)

I'd be happy to help you with implementation-specific problems as they arise. You can find me here and on Slack.

Last updated

1-2 of 2