Curious about using Articles in multiple sections on a site ... perhaps like mini-blogs ... For my site, I have 3 distinct buckets of content; Meet, Build, Share.
The site is for LEGO fans/hobbyists ... Each section will have dynamic content, articles on topics related those those buckets. Meet is about our Meet Ups, meeting minutes, etc. Build is how-tos and project ideas, and Share will be discussions, general blog posting ...
What approach would be best in terms of using Articles to manage all of that dynamic content? I've had two ideas in mind
1. Create "Articles" beneath each resource container
2. Create a single "Articles" container and use tags to display the associated posts in those sections, using some filtering on the tags.
Are either of those something someone has done or tried. I suspect using tags may be the better option, as I could speculate that multiple Articles could get a tad messy and maybe even conflict. Certainly risky to maintain. For the tags, I haven't yet found and example where I can filter the content display by tag values ... but it's very likely I haven't looked thoroughly enough - I'm still pretty new to ModX and Articles.
Thanks for any feedback and suggestions!
Hello,
I think it depends on how distinct you want to make these "mini-blogs" or how unified.
And also if you wish to use certain features of Articles, the TAGS to categorize topics among the "blogs"
I have used up to 5 separate Article containers - each having a distinct TAG system.
There was no problem of messy: as the topics within the "blogs" where clearly and carefully under their respective categories.
With separate Containers, I could also fine-tune user permission...say you want some Editors to post articles (via front-end) in the MEET blog and not in the SHARE blog.
I have also used separate containers if I wanted to easily use different templates (or bulk change) for each mini blog.
Yea, sometimes, it is nice to go the easy way... of course you can write different templates for articles according to TAG content...
Hope this helps
TinymceWrapper: Complete back/frontend content solution.
Harden your MODX site by
passwording your three main folders:
core, manager, connectors and renaming your
assets (thank me later!)
5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
-
☆ A M B ☆
- 894 Posts
I just use a single Article resource and use a getResource call on my other pages and filter them by a TV I assigned to each category in my
CMSTricks site, it works pretty well haven't had any issue with it so far.
@Benmarte: So for your site you have one Article container and in your getResources calls you are filtering the content by a seed tag for the relevant section of the site? (just clarifying)
I'm actually pleased to see two replies that say you've used Article in both ways with success ... I can certainly see the advantages of segregating them for custom templates and permissions as donshakespeare mentioned.
For my needs, I think filtering them by a tag would be sufficient, and in terms of the content editors who may (if any besides me) contribute, and keep it a bit easier to manage.
@Benmarte could you elaborate more on the TV you used to default the seed tag? (perhaps there is a tutorial on your site on this, I'll look there too) -- And one thing, I assume there is a "Integrating a template ... part 1" but the Tutorials page doesn't have a "See all tutorials" link or list and that one has been pushed off the page. (I could have missed something)
Thanks,
-
☆ A M B ☆
- 894 Posts
I just made a TV for each section so basically Tutorials, Reviews, Tricks and Interviews are all values of a TV I called article-category.
Then for each article I write I just select under what category it should be filed under.
Then in my template I just have it do this:
[[!getResources?
&parents=`ID of Articles Container goes here`
&tpl=`ArticleRowTpl`
&tvFilters=`article-category==[[*pagetitle]]`
&showHidden=`1`
&includeTVs=`1`
&processTVs=`1`
&includeContent=`1`
&sortdir=`DESC`]]
Hope that gives you a better idea, good luck.
P.S.
Here is the link for the first part of the template integration thanks for letting me know the pagination isn't working on the other sections of the site I will look into it tonight.
Thank you. About what I was thinking to setup myself.
If they should live in different areas of the site, and don't need to share tags they should be in separate containers (querying with tv filters or TVs at all is slow).
If they need to share tags, same container
jpdevries
