Meta tags:
keywords=tapestry, apache, apache tapestry, framework, java, web, component, open source, application, dynamic, scalable, robust, servlet;
description=Apache Tapestry is a open-source component-oriented framework for creating dynamic, robust, highly scalable web applications in Java. Tapestry complements and builds upon the standard Java Servlet API, and so it works in any servlet container or application server.;

Headings (most frequently used words):

siteexporter, confluence, site, setup, overview, wiki, formatting, guidelines, website, structure, updating, the, template, how, works, manual, intervention, changing, itself, related, articles, post, processing, html, pages,

Text of the page (most frequently used words):
the (93), apache (31), and (25), page (25), tapestry (23), pages (19), are (17), #confluence (15), for (13), siteexporter (13), with (13), code (11), site (11), template (10), that (10), source (9), you (8), should (8), org (8), html (7), exported (6), use (6), change (6), svn (6), all (5), other (5), this (5), user (5), guide (5), file (5), not (5), links (5), names (5), cxf (5), from (5), https (5), hour (5), setup (5), license (4), trademarks (4), component (4), web (4), about (4), edit (4), getting (4), documentation (4), changes (4), see (4), link (4), above (4), have (4), include (4), banner (4), proposed (4), after (4), tags (4), repos (4), image (4), software (3), foundation (3), may (3), logo (3), java (3), works (3), mailing (3), reference (3), project (3), subversion (3), each (3), also (3), navigation (3), small (3), most (3), just (3), lead (3), word (3), related (3), main (3), name (3), since (3), font (3), headings (3), http (3), wiki (3), program (3), detected (3), when (3), post (3), minutes (3), developer (3), version (2), feather (2), servlet (2), api (2), any (2), thanks (2), security (2), sponsorship (2), events (2), issues (2), development (2), tapestry5 (2), apachetapestry (2), involved (2), support (2), stackoverflow (2), lists (2), community (2), faq (2), apidocs (2), started (2), download (2), commit (2), repository (2), macro (2), numbers (2), way (2), our (2), described (2), adds (2), contents (2), well (2), index (2), footer (2), includes (2), features (2), paragraph (2), generally (2), title (2), following (2), wikipedia (2), articles (2), content (2), example (2), more (2), foo (2), line (2), where (2), its (2), child (2), don (2), which (2), deprecated (2), images (2), noformat (2), output (2), default (2), only (2), first (2), put (2), top (2), annotation (2), annotationtype (2), original (2), currently (2), same (2), used (2), can (2), but (2), will (2), changing (2), pagecache (2), needed (2), asf (2), trunk (2), infra (2), websites (2), production (2), cache (2), files (2), public (2), embedded (2), export (2), cwiki (2), run (2), makes (2), list (2), changed (2), commits (2), how (2), information (2), copyright, 2020, licensed, under, marks, mentioned, registered, their, respective, owners, complements, builds, upon, standard, container, application, server, open, oriented, framework, creating, dynamic, robust, highly, scalable, applications, social, docs, principles, introduction, team, home, your, find, check, out, must, committer, otherwise, write, access, updating, hls, noticed, footnotes, combined, render, correctly, footnote, anchors, reset, back, included, perhaps, there, fix, glues, everything, together, appropriate, places, except, breadcrumbs, blog, posts, plain, parts, addition, exist, key, website, structure, phrase, bold, start, right, floated, box, provides, cookbook, cheat, sheets, etc, than, subsections, briefly, discuss, topics, fully, covered, article, localization, section, templates, explicit, rely, bottom, carry, over, macros, mark, new, diagrams, sized, thumbnails, centered, border, console, listings, path, class, qualified, method, property, somemethod, myproperty, multi, capitalized, naming, conventions, words, captialized, treat, were, element, level, sections, within, type, current, precede, hyperlinked, character, outside, formatting, guidelines, pick, compare, unmodified, copy, written, dan, kulp, camel, geronimo, struts, possibly, others, customized, proceed, caution, because, customizations, make, harder, pull, future, likely, versions, itself, cause, republished, deleting, repo, usually, whole, manual, intervention, children, handled, one, another, causing, regenerated, autoamtically, including, examples, syntaxhighlighter, javascript, added, empty, removed, breadcrumb, updated, tagsoup, clean, processed, several, ways, before, being, committed, here, few, things, going, processing, velocity, time, between, saving, seeing, result, depending, save, minute, publish, then, wait, almost, unfortunately, img, pointing, origial, urls, unless, manually, linked, static, has, been, done, every, attachments, roughly, command, hourly, buildbot, service, call, rss, feed, actually, get, last, formatted, those, processes, below, finally, into, part, nearly, instantly, available, emails, sent, details, readme, instance, isn, capable, handling, lot, incoming, requests, spaces, statically, responsible, once, gets, automatically, notable, exception, javadoc, kept, overview, bible, release, process, building, document, describes, what, search, roadmap,

Text of the page (random words):
confluence site setup apache tapestry apache tapestry getting started documentation download community mailing lists stackoverflow support getting involved edit this page apachetapestry tapestry5 development source code issues roadmap apache about apache events sponsorship license security thanks search apache tapestry documentation developer information confluence site setup confluence site setup this document describes our web site setup what is where and how it works related articles page building tapestry from source page release process page version numbers page developer bible page developer information page confluence site setup overview most of the web site and documentation with the notable exception of the javadoc api pages are kept in confluence since the confluence instance at https cwiki apache org confluence isn t capable of handling a lot of incoming requests all wiki spaces are statically exported the siteexporter program is responsible for that once a page in confluence changes that page gets re exported automatically how siteexporter works for more details see the siteexporter readme siteexporter is a command line java program that is run hourly currently at 19 minutes after the hour from apache s buildbot it makes a web service call to confluence to its rss feed actually to get a list of pages that have changed since the last run and the html formatted export of those pages for each it post processes the file described below finally siteexporter commits all changed html files into tapestry s part of the apache subversion repository which nearly instantly makes it available to the public at http tapestry apache org and commit emails are sent to tapestry s commits mailing list attachments to confluence pages are exported in roughly the same way unfortunately wiki pages with embedded images will export with img tags pointing to the origial cwiki apache org urls unless you manually change the image in the confluence page to be linked to the exported static image file this has been done for the banner image but not every embedded image the time between saving a change in confluence and seeing the result on the public site is at most 1 hour depending on when you do it if you save a change at 18 minutes after the hour you ll see the change in about a minute if you publish it at 20 minutes after the hour then you ll have to wait almost an hour html files in svn https svn apache org repos infra websites production tapestry cache file https svn apache org repos infra websites production tapestry content cache main pagecache siteexporter source https svn apache org repos asf tapestry tapestry site trunk velocity template https svn apache org repos asf tapestry tapestry site trunk template template vm post processing html pages html pages exported from confluence are post processed in several ways before being committed to svn here are just a few of the things going on tagsoup is used to clean up the html the breadcrumb links are updated empty paragraph p tags are removed from the top of the page code macro output code examples are detected and syntaxhighlighter javascript links are added to the page when needed include tags when one confluence page includes another are detected causing the including page to be regenerated autoamtically children tags are also detected and handled manual intervention you can cause the whole site to be republished by deleting the main pagecache file above in the subversion repo this is usually only needed after changing the template changing siteexporter itself currently the siteexporter source code is an unmodified copy of a program of the same name written by dan kulp for the apache cxf project and also used by camel geronimo and struts and possibly others it can be customized but proceed with caution because any customizations will make it harder to pull in future changes from the original cxf siteexporter code the cxf siteexporter is likely to change as confluence versions change to pick up changes to the original cxf siteexporter code just compare the tapestry source code with the cxf source code wiki formatting guidelines precede annotation names with if the annotation name is hyperlinked put the character outside of the link annotationtype http annotationtype html the first reference to a type on a page should be a link to http tapestry apache org current apidocs or the component reference treat the page title as if it were an h0 element and put top level sections within the page as h1 page names as headings should have all words captialized for other headings only the first word of multi word headings should be capitalized e g h2 naming conventions following wikipedia use code font for method and property names myproperty somemethod use the default font for class names qualified or not use the default font for path names use code for listings not noformat use noformat for console output images and diagrams should be small sized thumbnails centered with no border use the since and deprecated macros to mark new or deprecated features proposed each page should include explicit links to its child pages don t rely on the child pages links at the bottom which don t carry over to the exported site proposed in pages other than the user guide pages subsections that briefly discuss topics that are more fully covered in the user guide should lead with a main article foo line where foo is the name of the page in the user guide example the template localization section of component templates proposed user guide pages should generally start with a right floated related articles box that provides links to related content in the faq cookbook cheat sheets etc example proposed the lead paragraph should generally lead with the title word or phrase in bold following wikipedia website structure the index page includes the banner and key features pages as well as the blog posts most other pages are just plain pages and may or may not include other parts in addition the navigation small banner and footer pages exist our siteexporter template described above glues everything together it adds the contents of the navigation and footer pages in the appropriate places and on all pages except the index page it also adds the contents of the small banner page as well as the breadcrumbs navigation hls i ve noticed that pages with footnotes that are combined with the include macro do not render correctly the footnote numbers and anchors reset back to 1 for each included page perhaps there s a way to fix that with the template updating the template you must be a tapestry committer or otherwise have write access to the subversion repository see link above to edit the template check out the siteexporter source project see link above find and edit the template vm file commit your changes apache tapestry tapestry apache the apache feather logo and the apache tapestry project logo are trademarks of the apache software foundation apache tapestry home download team license documentation introduction principles getting started user guide docs component reference apidocs faq community mailing lists stackoverflow support getting involved edit this page social apachetapestry tapestry5 development source code issues apache about apache events sponsorship license security thanks about us apache tapestry is an open source component oriented framework for creating dynamic robust highly scalable web applications in java tapestry complements and builds upon the standard java servlet api and so it works in any servlet container or application server apache tapestry apache and the apache feather logo are trademarks of the apache software foundation all other marks mentioned may be trademarks or registered trademarks of their respective owners copyright 2020 the apache software foundation licensed under the apache license version 2 0