Bildy For Dummies

Good day! I open this topic for its future replenishment of the ready-made solutions.

The point is simple.

I (or who want to) ask questions to how and what to do, and the developers or people who know the answer - answer.

Then, these responses will be collected, verified and presented in the general form of a wiki (or other way).

P.S. I really like Buildy, but I'm used to learning with ready solutions by readiness decisions and analyze them for making a conclusion.

The system documentation have examples of the use of a B:tags, but no examples of integrated solutions (if you know what I mean).

That's a great point and also a great first question.

There is an easy way to do this, but it requires a feature that isn't ready for prime time use yet. I'll email you the code and details so that you can start using it right away.

If anyone else is interested, just let me know and I'll mail it to you as well. We will be publishing the solution for public once we've finalized the the feature and completed documentation around it (the solution is broader issue than just tags).

Next question will be more easier...

How we can make multilingual sites with The Bildy?

I think it will be something like this (using page catalog):

- English
-- News
--- Page
--- Page
-- Contact
- Other Language
-- Some Page
--- Page in Some Page
-- Some Page

Did I think a right way? Or we can make it some other way?

My experience is: translated sites are never the same as the original site. So don't set up to create a clone.

I'd do the same as what you're describing above. For http://valvira.fi we created "home page" datamodel that had distinct fields for homepage use. The main language was located at the site root and for each language the corresponding content was under its homepage. URLs were generated from a dedicated fields, so we could then have content like http://valvira.fi/en and http://valvira.fi/en/chemicals Clear, understandable urls.

Each home page was set "hidden from navigation" so they wouldn't be part of the automatic navigation generation. We then placed liks to other languages by hand.

You can best create navigations by using <b:structure> tag. If you wan't list subpages for top level items, use <b:structure.recursion/>

I made an example of that in the <b:structure.recursion/> documentation page: http://bit.ly/4IfNDv

Is there easy way add buttons to mooeditor? Specially looking buttons for basic html functions like (h1, h2, h3, p, clean paste)?

I noticed that there is init and extend fields on mooeditable on configurations, but i was only capable to make dumb buttons (which doesn't make a thing.. ).