jimbobsquarepants / zoombraco

:zap: A lean boilerplate for rapidly developing strong-typed Umbraco websites.

Zoombraco

This repository contains a lean boilerplate for rapidly developing fast, scalable, easy to maintain, strong-typed Umbraco websites.

Zoombraco is designed to be lean yet exceptionally powerful and flexible allowing you to create your own websites on a firm foundation. Zoombraco lets you concentrate on the fun features of your site while enabling you to maintain a strong MVC architecture.

Features

• Three strong-typed Base-Class-Types Page, Component, NestedComponent
• Base Controllers, Views
• Strong-typed ContentHelper for document traversal.
• Automatic mapping of Nested Content
• Automatic XML sitemap generation
• Language aware Metadata
• All properties can be made language aware and map automatically
• Faceted, language aware search engine with fragment highlighting
• Multitentant aware codebase
• Image CDN url generation.

Documentation

Documentation can be found via the Wiki and is open for collaboration.

Consuming the Solution

At the moment the codebase is there but I'm lacking a complete web demo. I'll get round to it though as I am writing documentation and an accompanying set of articles.

Nightlies are available from MyGet

A sample Nuget.config file is as follows:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="nuget.org" value="https://www.nuget.org/api/v2/" />
    <add key="myget.ditto" value="https://www.myget.org/F/umbraco-ditto/" />
    <add key="myget.zoombraco" value="https://www.myget.org/F/zoombraco/api/v3/index.json"/>
  </packageSources>
</configuration>

Eventually there will be a Nuget package for consuming the library once the Ditto dependency is released.

Having a play around is encouraged, I'm always looking for feedback.

The demo website login details are:

• Username : zoombraco
• Password : password

zoombraco's Issues

Multilingual search

James,

Not really an issue more an observation, the multilingual content is all being stored in the one index and using the one analyser set in examine config. Issue with that is you cannot then apply different analysers that are language specific. So where you are doing

e.Fields[string.Format(ZoombracoConstants.SearchConstants.MergedDataFieldTemplate, languages[i].CultureInfo.Name)] = mergedDataStringBuilders[i].ToString().Trim();

You have fields for each language instance but they are all using standard analyser. Ideally arabic should be using arabic analyser as that will give you better tokens than standard. For chinese korean languages as they are pictorial and as far as i am aware each pictogram can be more than one word. Standard analyser tokenises on space. Where as cn analyser does morphological analysis for creating tokens. Also language specific analyser will remove stop words and stem.

You could implement document writing and then index a specific field using a specific analyser but at that point you would need to get the vorto property and figure out its language then use appropriate analyser for it. I'm thinking better route would be on the property in the poco another field attribute that allows you to specify the analyser to use for a specific language instance.

Loving the project have sent it to cogworks team to have a play.

Ismail

Minor typo in the Controllers documentation

I think the description of ZoombracoController and ZoombracoApiController should be swapped, so should look like below.

https://github.com/JimBobSquarePants/Zoombraco/wiki/Controllers

The classification of these types is as follows:

• ZoombracoApiController The base controller for all WebApi controllers.
• ZoombracoController The base controller for all render and surface controllers.