Thread

Thanks Michael, for clearing this up a little.

The last site I made is a bit wordpress blog styled, so very straightforward. This way I can offer a full EE site in a day without too much effort and next we’ll build out the business /website from there. My experience is that clients have no clue what they can do with their website until they start using it. It is very difficult to sell a complex setup to a starting business. so this setup works very well for me. It’s a clear example of a reason to use just one weblog.

In this case we’re already discussing a condolence page, which will have a different setup. That would be perfect for a separate weblog. I have been thinking about a template, but you’re right, it may force people to go through more fields then necessary and we might want to keep the content separated.

However, I’ve also discovered some drawbacks with separated weblogs. As far as I know you can’t just duplicate or move entries between weblogs. Very inconvenient if you’re using a multi language site!

However, I’ve also discovered some drawbacks with separated weblogs. As far as I know you can’t just duplicate or move entries between weblogs.

If the weblogs share the same field group, then you can move an entry from one to the other. A “Weblog” drop-down should show up under the Options tab in that case.

OK Michael, yet another thing learned! Well, basically different weblogs have different fields most of the time… but it’s something to keep in mind.

PS; sorry for hijacking this thread… But it’s good to get a clear picture of which technology to use when.

If the weblogs share the same field group, then you can move an entry from one to the other. A “Weblog” drop-down should show up under the Options tab in that case.

I have learned something new as well…but this is another point of what can be done and it is hard to decide where to stop.
Now I would want to make 1 field group and stick all the fields into it “just in case client wants to move entries”.
Is this a good way of doing things? What does this do my database and table structure?

For questions like these I find myself developing more and more…which is why I posted the thread. I agree (or trying to think in terms) with noregt, why not start of with 1 weblog and then build upon.

An “FAQ” section can be a simple page with a few paragraphs and html anchors…
Often I find ‘clients/friends’ excited over the fact that they will be able to edit their site but in reality they get over it in a month or so. Again, taking about simple sites much like noregt pointed out…there just isn’t much content they need to add/change over time.
Well, anyhow, just thinking out loud here.
Thanks for keeping the discussion going.

I always analyze the content first - never decide on the number of weblogs until that’s done. I never create extra fields in a group just to accommodate different types of content. I find most clients just get confused if I do that - “What fields do I fill in again if it’s just a faq entry?” I can’t imagine a client wanting to move a faq entry to a different weblog like “bios”

Sometime one can over simplify and just make it more complex/confusing.

It’s much easier (to me) to just tell the client - “You want to create/edit a faq entry?, choose FAQ in publish/Edit list” You want to create/edit a job opening?, choose JOBS in Publish/Edit list.

I have learned something new as well…but this is another point of what can be done and it is hard to decide where to stop.
Now I would want to make 1 field group and stick all the fields into it “just in case client wants to move entries”.
Is this a good way of doing things? What does this do my database and table structure?

I’ve never needed this ability on a client site.  Mainly, again, because weblogs hold unique content types so the ability to move a post is immaterial - it never makes sense from a content perspective.

An “FAQ” section can be a simple page with a few paragraphs and html anchors…

True, but EE is a Content Management System, so I wouldn’t feel like I had delivered a well-constructed CMS-based site if, in order to add a new Q&A pair my client had to know how insert the new Q&A pair in and mark up with HTML.  And again, once entered into the system as a “Page of FAQ’s” vs. Q&A pairs you will only ever be able to use that content as a page.

The site I was working on today needed an FAQ - but the design also called for the 3 newest questions to appear in the footer of every page.  Because I had implemented the section using a dedicated weblog & field group it was a simple matter to pull off, and should the FAQ ever be updated the footer will follow suit dynamically (will it in reality? I don’t know, but at least my part is done well).

And - the FAQ was a simple example mentioned to illustrate a point.  Content types vary widely, and I just can’t see how - at least for the business-oriented sites I seem to get involved in - using one weblog would to a simpler user experience overall. 

While your weblog list would be shorter I can’t see how the content entry experience can’t get more complex out of necessity as markup would have to be added in posts in order for more generic field sets to accommodate a wide range of content types. 

It seems with the one-weblog approach EE becomes less a CMS than a “Page Management System” - which would be a tough acronym to sell..😉

😊 well at least “PMS” would be catchy…joking.
Sure, the same way you did FAQs is how I have them setup…I can pull “what we do” though site and pages…it just made more sense and re-usability was instant.
I guess ultimately I was looking for ‘a way of thought’ to get very small sites onto EE and stop thinking in terms of entries and blogs and publications and booking-what-have-ya-systems…in other words when content is short and sweet.

Sometimes I get buried into possibles and everything looks like a weblog 😊 so it is good to see other peoples perspectives and choice patterns.
Thanks everyone!

Hi there,

Little up on this post about this :

If the weblogs share the same field group, then you can move an entry from one to the other. A “Weblog” drop-down should show up under the Options tab in that case.

I don’t know if I’m doing something wrong, but I can’t get the drop-down with anything else than the original “weblog”.
My problem is that I have had an EE website for a couple of years now, with only one weblog, I’d like to separate its content into two weblogs, meaning move posts from a weblog to another. But I can’t get the new weblog in that dropdown menu…