Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Create a standard module with configuration, templates and services.
  • Replace JSP by FTL's
  • Better configuration
  • Add images videos or news informationsSpecialized Sitemaps (Specialized Sitemaps) ?
    • Mobiles
    • News
    • Video
    • Geo
    • Code Search
  • Add additional informations (linked to a page) to the SiteMaps ?
    • Images
    • Video
  • Add Junit tests.
  • Add an AdminCentral Tools menu to access the Edit page ?

...

Display a XML page containing site informations following the siteMap protocol.

Have a global Dialog that allows to

  • Define the sites to include in the output file
  • Define Mobile variation to incude to the output file
  • Define the output properties
    • One file per site
    • One single file

Have a configuration page (Dialog) that gives us the ability to define per output file

  • File name
  • File Location

Have a configuration page (Dialog) that gives the abitiy to define per page the:

  • Change frequence
  • Priority
  • visibility of the site page and children in the SiteMap xml.

...

  • Site variations:
  • Multi domains:
    'No. Please list only one version of a URL in your Sitemaps. Including multiple versions of URLs may result in incomplete crawling of your site'...
  • Uses of an external java library (Apache License 2.0)

Google SiteMap

...

Configuration

We should be able to configure:

  • Sites ans subSites to include in the SiteMap Url
    • Define if we add additional informations for Images Videos related to a page.
  • Mobile Sites and subSites to include in the SiteMap Mobile
  • Output Files Informations
    • File Name
    • Location
    • One file per Sites or a global File

Display Site and VirtualUri mappings in a xml format.
Sites to be displayed are defined in the configuration (see configuration section). If no sites are defined, the root of the website repository will be taken to display sites. 

Sites display
  • Display all mgnl:content nodes (including inherited nodes type) if they are not defined as not to be displayed (done in the configuration part by setting  a googleSitemapHide property)
  • Display subNodes of type mgnl:content if the parent node don't define to hide childrens (done in the configuration part by setting a googleSitemapHideChildren property)

In case of nultilang support, display the specific language sub pages. For example
.../ftl-sample-site/ftl-dialog-showroom.html
.../de/ftl-sample-site/ftl-dialog-showroom.html

VirtualUriMappings display

Display all virtualUriMapping nodes if they are not defined as not to be displayed (done in the configuration part by setting  a googleSitemapHide property)

SiteMap Configuration

Display a line for all Site contents and VirtualUri mappings showing their current settings. Access a dialog to change these definitions.

Sites configuration
  • Display all mgnl:content nodes (including inherited nodes type)
    • Display them in red if they are defined as not to be displayed
  •  Display subNodes of type mgnl:content
    • Display them in red if the parent node set hide subNodes
VirtualUriMappings configuration
  • Display all virtualUriMapping nodes.
    • Display them in red if they are defined as not to be displayed

Solutions

  • Create a configuration singleton used by the model and service (configure site to be displayed, date format, ...).
  • Create a Service responsible to perform the nodes search and convert these nodes to beans used for the rendering.
  • Create a new SiteMapModel  that uses the services and configuration singleton.
  • Create FTL's for rendering.

...