Variabili Comus
Fondamentalmente il modello è controllato da {{macros}} speciale che si posiziona sulla tua pagina web, i macro dicono a Comus Thumbs dove si desidera posizionare le cose, Comus quindi scansiona la pagina del modello, e inserisce i link e i pollici come si desidera, o eseguirà operazioni speciali sulla pagina, il nsaves il risultato in una nuova pagina e directory di vostra scelta. |
| Terminologia Macros,Variables,Extensions,Modifiers,Links,Thumbs. |
| Una rapida panoramica della terminologia |
Questa sezione fornisce un'introduzione ai blocchi di costruzione dello script, fornisce un primer per le informazioni più dettagliate che seguono. |
FORMAT: {{category-type-index}}
Where category is either 'all' or the case sensitive name of a chosen category, and type is one of [link or archivelink] and index is the selector of which link in thelist to use.
EXAMPLE: The 1st, 3rd and 2nd link in the list, taken from only the teen category.
| Lesbians - Young Lesbian Closeup | Babes - Busty Aria Giovanni | Teens - Cute Brunette Poser | Lesbians - Young Lesbian Closeup |
NOTES: You would use this type, if you wanted very specific control over your layout, maybe you want to place banners and blind links in the middle of your table, this is a perfect use for Singular links.
-Singular links do not need table tags, unless you define the link template in such a way to require them.
-If singular links do not find any images in a particular category, or do not have enough images to complete the list, then they will search at random throughout your gallery listings, to make up the difference.
-By default images have priority over links, but once used as an image or a link the gallery will be flagged and will not be available to the other lists.
-Note in this example I deliberately doubled up on the 1st teen link, the script automatically places the first occurance of the link in both locations.
-Indexes start at 1 and run sequentially upwards, if you miss an index (1,2, ,4,5) then the script will drop your last images, in this case it would see there were only 4 links requested, and it would have no image avail for index 5.
FORMAT: {{category-type-index}}
Where category is either 'all' or the case sensitive name of a chosen category, and type is one of [thumb or archivethumb] and index is the selector of which link in the list to use.
EXAMPLE: A custom table of 3 by 3 thumbs, taken from the teen database
 |
 |
 |
 |
 |
 |
 |
 |
 |
-The lower the number the higher the priority of that image in your list. So index=1 is the very first thumb pulled from your list, depending on how you have ordered your list, this could be a high priority image. By default, images are sorted at random but weighted by the rank you assign to them through the approval process. Each prefered submitter can have his own default rank that you can assign, and each standard submitted gets a default vote of 7. This gives you 3 levels of downgrade and 6 levels of upgrade to play with. Each level represents approximately a 10% jump, so votes of 1 should consistently fall somewhere within the top 10%, as the votes fall more towards the extremities they become less eratic, while votes in the mid ranges will tend to bounce around a lot. This is done so votes you upgrade, will tend to get sent to the top of the list, and votes you down grade will tend to randomize at the bottom, while votes in the middle will get a fair jumbling.
-archivethumb types are explained below, but basically pull from the list after all links and thumbs have been processed.
FORMAT: {{category-type-index}} Where category is either 'all' or the case sensitive name of a chosen category, and type is one of [link or archivelink] and index is the selector of which link in the list to use.
EXAMPLE: A custom table of 3 by 3 links
| Fetishbizarre - Slut Gets Spanked | Amateurs - Amateur Panties | Teens - Tawnee Vids/pics |
| Babes - Babe In Stocks | Anal - Anal Please | Fetishbizarre - Hard Bondage |
| Teens - Beautiful Erotic Brunette | Interracial - Sluts W Huge Cock | Lesbians - First Lesbian Experience |
FORMAT: {{include-(path or url)sourcefile}} Where include is the keyword to trigger this macro, and sourcefile is the name of the file to include.
ALIAS: This command is an Alias for {{showfile-sourcefile}}
EXAMPLE: A default include file has been set up for this demo. It contains a single thumb and a short messge. The file itself is created in the next section, note that because of the forward reference that any changes to the file will not be reflected until the next refresh of the page.
This is an included document test_out.txt
-Included files do NOT get interpreted by the template processor, they just get added to the current output, to process macros on a page file, see below.
-By default files are extracted from the /templates folder, but you can use ../ path modifications to reach the rest of your drive, or you can just use a direct http:// url, but note where you use the url it will interpret your page first.
-Includes allow you to use special sections like 'headers' and 'footers' which are built into your pages at compile time, allowing you the benefit of shtml/php/asp includes without having to have a runtime script while in production. That means you can run the TGP side of your site entirely in HTML only mode, reducing server overhead and costs considerably.
-Includes can also be used to load your archives or the results of custom template builds. (see next section for info on custom templates)
FORMAT: {{makefile-(path or url)sourcefile-targetfile}}
Where 'template' is the keyword to trigger this macro, and sourcefile is the name of the file to load and process and targetfile is the name of the file to save results to.
EXAMPLE: Building a custom template
When this macro is placed on a page, it will first check to see if a rebuild is required, if it is then it will load the desired template from your /templates directory by default, or it will search the path, or load from the http:// URL you have specified.
-The source file can also execute the same macros as your makefile template. It can build and include pages and write them to disk (into the templates folder by default). You can also specifiy other locations by adding relative path information to the filename. IE. {{makefile-testin.txt-../../testout.txt}} would take the file testin.txt, parse it and write the results 2 folders up from the ct/templates folder. (Assuming Comus is in the subfolder /ct/ then it would write the file into the main index folder of your site.
-You might need to make sure that PHP has permissions to read/write the files. New target files will usually complain about permission errors, you will need to chmod 777 the target file, so that both you and Apache have read/write/execute to the target file.
-Templates can be used to create Archive pages. The script will start pulling thumbs from the top most 'makefile' macro found within Templates Control Center and then execute the 'makefile' macros found within each source template. The lowest macro on the page, gets the eldest thumbs. Remember this if you are trying to lay pages out and are wondering why your new thumbs are not showing up.
-Once you have created a page, to reference or link to the page you can either { include } it using the method mentioned above, or you can include it using a php or an SSI include. Or if you have designed your template so that the page can stand completely alone, you can name it with a .html extension and reference it directly.
-The macro works on both templates and the Make Files Section found inthe Templates control center.
-Note that no links or code are created ON the page that actually invokes this macro. If you need to link to the resulting page, or if you need to view the results, then you will either have to create a link to the page, or you will need to use an include to load the results into a page. So for example, you could use an include to load the template result onto your main page.
-If you use this feature it is best to try and build the template, before you try to include it.
-A resulting template page can only be manipulated by the first macro which calls it, subsequent requests to write to the same file during the same session, will be ignored.
-Your target filenames can have any extension they like, and so your templates can be in any scripting language you like.
-You have the option of loading the template file with any language you like, Comus's include method should be the fastest during run time, because it compiles the code right into the page so that it can be static. But you can load the page dynamically at load time if you like with PHP/ASP/SSI/JS or whatever.
NOTES: Archive galleries are the galleries that remain after all the current galleries have been extracted.
-By placing multiple makefile macros in the makefile template it gives you the option of creating separate pages which contain archived links and thumbs.
The method we use for accessing the archive galleries is to simply control the order in which we request the pages from within the master Makefile template.
[START MAKEFILE]
{{makefile-indexpage.txt-../../index.shtml}}
{{makefile-archivepage.txt-../../archive.shtml}}
[END MAKEFILE]
Will process your indexpage.txt file FIRST and write it to index.shtml in your web root folder, pulling the most current galleries. It will then use what remains in your pool to create the archives.
NOTE:You need to make sure you use macros within the archive pages which only look for thumbs which are 1 day or older say with an query-age1}} extension, or your archive page will probably try to pull fresh galleries, as all basic non extended macros will always try to grab fresh thumbs by default.
For example.
The system has a default query for pulling galleries of one day older or more.
{{all-links-20-1-query-age1}}
Will list a vertical column of 20 links, which are 1 day or older.
-The idea is that you create a separate template page to your main page for holding your archived galleries, and then on this archive page you place your {{category-type-dimension}} macros.
-Then you either place a direct link to the resulting file, from your main page, or you can include the resulting page, by using a macro/shtml/php/or the scripting language of your choice. Note because of the nature of the macro ordering, when using {{include}} for displaying archived gallery pages you will have to display the archives from the previous build, or in other words, the archive listings will be 1 build old, when displayed. (hope it makes sense as to why)
| Local Variables-Only avail within link and thumb templates | |
| Variable | description |
| %onpage% | The number of times the gallery has been displayed on a page, or actually used in a build, this ONLY increases when the gallery is actually used. |
| %clickperiods% | The number of times galleries have been built since this gallery was listed as new, note that this increments regardless of whether the gallery was actually used on a page. |
| %periodsshown% | The number of DAYs passed since the gallery was newly used on the site. |
| %clicks% | The number of clicks on the gallery. |
| %ctr% | The Click Through Ratio for this gallery, a score defined as clicks/clickperiods. |
| %cat% | The condensed category taken from the database as entered in the [Category] section. |
| %category% | The category taken from the macro - IE shows 'all' for all. |
| %rawcategory% | The category taken from the database without condensing (no removed spaces). |
| %url% | The target url. |
| %overurl% | The target url, used for mouse overs (without trade script). |
| %domain% | The domain only of the target URL |
| %desc% | The truncated description, (max length set by you) |
| %description% | The full description |
| %uid% | The unique id assigned to the gallery |
| %id% | The true id for the gallery |
| %nick% | Submitters name |
| %thumbname% | The actual file name to the thumb |
| %thumbheight% | The thumb image width |
| %thumbwidth% | The thumb image height |
| %thumbsize% | For compatibility, width of square thumbs |
| %numpic% | Number of pics in the gallery (always 2 chars, ie 00...08,09,10,11) |
| %piccnt% | A running count of the total links and thumbs displayed |
| %numlist% | A running count of the links and thumbs in this set only |
| %thumbsize% | For compatibility, width of square thumbs |
| %vote% | The ranking score (1-10) assigned to the gallery |
| %rank% | The ranking score assigned by you |
| %clicks% | The number of times the gallery has been clicked |
| %dis_date% | Custom formatted date of submittal |
| %TODAYS_DATE% | Non formatted day of the month, with no leading 0's |
| %submit_date% | Custom formatted date of submittal |
| %submit_hour% | 00-24 hour of submittal |
| %submit_day% | 01-31 day of submittal |
| %submit_month% | 01-12 month of submittal |
| %submit_year% | xxxx year of submittal |
| %accept_date% | formatted date of approval |
| %accept_hour% | 00-24 hour of approval |
| %accept_day% | 01-31 day of approval |
| %accept_month% | 01-12 month of approval |
| %accept_year% | xxxx year of approval |
| %listed% | formatted date of first listing |
| %listed_date% | formatted date of first listing |
| %listed_hour% | 00-24 hour of listing |
| %listed_day% | 01-31 day of listing |
| %listed_month% | 01-12 month of listing |
| %listed_year% | xxxx year of listing |
| Global Variables-Available Anywhere | |
| Variable | description |
| %this_date% | formatted date of today |
| %this_HOUR% | 00-24 hour of today |
| %this_hour% | 00-12 hour of today |
| %this_day% | 01-31 day of today |
| %this_month% | 01-12 month of today |
| %this_YEAR% | xxxx year of today |
| %this_year% | xx year of today |
| %sitename% | The domain name of your site without http:// |
| %siteowner% | The name you chose for yourself in setup |
| %tgpemail% | your registered email address |
| %recip% | Your recip link with http:// info |
| %refreshperiod% | The current refresh period |
| %this_period% | The current refresh period |
| %totalposts% | Total number of posts made |
| %logins% | Total number of webmaster logins |
| %hits% | Total hits on the page |
| %total_galleries% | Total approved galleries in the system |
| %updates% | Number of days passed since the site was new, the actual age of your site. |
| Local Variables-Only avail within link and thumb templates | |
| Variable | description |
| %lshave% | Text Link Shave value, will be replaced by either the 'lshave' value from Category Control Center or the #80# modifier value from within the macro, the macros have priority over category settings, there is one other thing that can affect lshave and that is the proxy capping settings. |
| %tshave% | Just like lshave only it is intended to affect the thumbed listings |
| %group% | Taken from the {{GROUP#SHAVE#category-type-index}} GROUP modifier can be used to send trades to your trade groups. |
| %category% | Feeds a compressed category tracking code to your trade script, you canuse this to track link popularity. |
| %proxy% | Feeds a code to the script of 'p' for a proxy click or a 'n' for a normal click. You can use this to track outgoing proxy traffic to identify hitbots. |
This would allow you to dynamically control shave ratios based on macro position, or category, it would also pass link tracking information through to the script, which would look like, p_TXT_Teen for a click on a teens text link from someone on a proxy server. (FYI Abnormal outgoing Proxy server traffic is an indication of someone using a hitbot on you, and can be used to monitor cheaters, if your ratio.)
FORMAT: {{category-type-index-query-"string"}} | {{category-types-rows-columns-query-qindex}} where query is a keyword to trigger this macro extension and qindex is an index to preset query (See below)
{{all-thumbs-3-3-query-"description like '%blonde%' or url like '%blonde%'"}} EXAMPLE {{setquery-1-"description like '%blonde%' or url like '%blonde%'"}} {{all-thumbs-3-3-query-1}}
This would first define a query and give an id of 1, the second macro then uses the defined query to search descriptions and urls for anything containing blonde. Note that the query is a mySQL WHERE clause and must be within double quotes ""
NOTES: Advanced capability, highly flexible and powerful. Finally, as I started thinking about all the options that I could build lists with, I decided to just expose the database query string and structure to you. So whatever your imagination can think of, is available to you. You will need to know how to structure a mySQL WHERE clause - so go look up queries on mysql.org.
Basically it gives you the ability to build custom lists and filters using less than, greater than, equal to, similar to, starts with, ends with,etc,etc and order them in any way you please. (If the script does not detect an ORDER BY, then it will assign its default ordering algorithm of date desc,rand()*vote.)
NOTE: It is not a full query, but just a WHERE clause.
You can use the 'query' capability of the post/review/search page to test the results of your queries, before you actually use them.
See the next section for an advanced application and examples of this option.
| Available fields | |
| Field | Description |
| id | Unique ID code |
| ip | IP of submitter |
| nickname | Name the submitter gave |
| Email address the submitter gave | |
| url | URL of gallery |
| category | Gallery Category |
| description | the full string of what the user gave the gallery |
| date | The date it was subitted in YYYYMMDDHH format |
| newpost | Yes if not yet approved |
| accept | Waiting/Yes/No |
| vote | 1=good ... 10=poor |
| recip | 'Yes'=has recip |
| sessionid | A unique 6 char string |
| numpic | Number of pics linked to images found in the gallery |
| filesize | Byte size of html page |
| thumbname | If blank then a link else if has a name then we have a thumb |
| mailme | Wants contact if approved |
| listed | The time that the gallery was listed in YYYYMMDDHH format |
| mgdate | The time that you approved the gallery in YYYYMMDDHH format |
| thumbwidth | The pixel width of the thumb |
| thumbheight | The pixel height of the thumb |
| clicks | The total number of times the link was clicked |
| timespent | The estimated time people have spent looking at the gallery in secs |
| exitclicks | The number of people who never return from the gallery |
| periodsshown | The number of times you have listed this gallery |
NOTES:This uses a combination of features built into Comus, and works with the custom 'Query' capabilities of the script.
To invoke counting set 'click counting' to Yes in the config setup page, this will modify all outgoing links on the page to re-route via cc.php and then on to your trade script.
The script will keep a running count of clicks and impressions and time spent at every gallery, now you can start using it in custom queries to build lists.
1 Gallerie più frequentate per il giorno
{{setquery-1-" periodshown=1 ordine per clic DESC"}}
2 Il più popolare per la settimana
(Assume il periodo di aggiornamento è giornaliero, altrimenti regolare di conseguenza)
{{setquery-2-" periodshown < 8 E periodi mostrati > 0 ORDINANZA DA clic DESC"}}
3 Random ma ponderato con clic
{{setquery-3-" periodi indicati >0 ORDINE PER (click*rand()))+(click*rand()))+(click*rand())) DESC"}}
4 Gallerie medie superiori ponderate per voto
{{setquery-4-" periodi indicati >0 E click > somma(click)/count(*) ORDINE PER (vota*rand())))+(vota*rand()))+(vota*rand())))"}}
5 Selezioni di categoria multiple
(assicuratevi di usarlo come tipo di categoria 'all' prima) e poi lo script si filtra per voi.
{{setquery-multicat-"(categoria LIKE '%teen%' O categoria LIKE '%amateur%')"}}
6 Domande combinate, top classificato con scelte casuali dal mese di priorità voti prima, clic secondi
{{setquery-7-"(vote=1 OR (periodosshown < 30) ORDINE DA voto,clicca DESC"}}
Si noti come non si è limitati a utilizzare solo i numeri per l'identificatore di query? come in [query-multicat] e anche che è possibile utilizzare il %global variables% definito sopra nelle query pure.
Ora per implementare effettivamente una di queste domande nella tua lista si estenderebbe la macro aggiungendo il -query-query name}} alla fine della tua macro, IE:
 |  | |
 |  |  |
 |  |  |
C'è una macro di debugging speciale che vi mostrerà la lista di query disponibile, questo potrebbe essere utile se si sta pensando di costruire una query personalizzata. Potremmo aver già definito uno come query di sistema predefinito, e si può solo utilizzare che invece, o perhps utilizzarlo per costruire una query personalizzata. Per mostrare l'elenco di tutte le query attive che è possibile utilizzare,{{showqueries}. Per usare le query semplicemente usare il [chiave] come il vostro 'query identifier'
query[age0]=" periodsshown >-1 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) )"query[age1]= "periodsshown > 0 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) )"query[age2]= "periodsshown > 1 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age3]= "periodsshown > 2 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age4]= "periodsshown > 3 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age5]= "periodsshown > 4 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age6]= "periodsshown > 5 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age7]= "periodsshown > 6 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age14]= "periodsshown> 13 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age21]= "periodsshown > 20 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age28]= "periodsshown > 28 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[days most clicked]=" periodsshown=1 order by clicks DESC, mgdate DESC"query[this weeks most clicked]= "periodsshown < 8 AND periodsshown >0 order by clicks DESC, mgdate DESC"query[last weeks most clicked]= "periodsshown < 15 AND periodsshown >7 order by clicks DESC, mgdate DESC "query[random by click]= "periodsshown>0 ORDER BY (clicks*rand())+(clicks*rand())+(clicks*rand()) DESC "query[above average]= " clicks > sum(clicks)/count(*) ORDER BY vote*rand()"query[last weeks best]= " ((vote= 1AND periodsshown >7 AND periodsshown < 15 ) ORDER BY clicks DESC "query[weeks best]= " ((vote< 4 AND periodsshown < 7) ORDER BY clicks DESC,vote*rand() "query[months best]= " ((vote< 4 AND periodsshown < 30) ORDER BY clicks DESC,vote*rand() "NOTA: Queste sono solo alcune delle domande disponibili, fare una discarica per vedere se ho aggiunto o modificato.
Skim trade ratios per MacroQuesto viene fatto tramite un modificatore macro, dove prefiggete la vostra categoria con un valore del rapporto skim, come {{#80#all-thumb-1}}
Questo fornirà il valore di 80 attraverso il %lshave% o %tshave% variabile all'interno del prefisso dello script di commercio e le definizioni suffissi (che si trovano all'interno del centro di controllo). Si noti che lshave e tshave non devono essere un numero, possono anche essere stringhe di testo che alimentano altri argomenti per il tuo script commerciale, o anche argomenti multipli, IE{{#p=50&x=latin#all-thumb-1}} Questa forma di modifica dello script di commercio assume una maggiore priorità rispetto ai rapporti commerciali per le definizioni di categoria descibed successivo.
Rapporto commerciale per categoriaÈ possibile alimentare i rapporti commerciali attraverso i vostri script commerciali su base di categoria utilizzando le variabili %tshave% e %lshave%. Troverete i rapporti di skim per questi all'interno del Centro di Controllo Categoria.
Totalmente disabilitando lo script commerciale per solo 1 paginaÈ inoltre possibile disabilitare ogni commercio su una pagina, utilizzando la macro {{notrades}}. Posizionare questa macro vicino alla parte superiore della pagina, in modo da essere sicuri che è attivato per l'intera pagina. Può essere utilizzato su pagine di archivio per rimuovere efficacemente lo script di scambio completamente.
Disabilitare lo script commerciale per una sezioneÈ un'idea migliore per modificare il rapporto a 100 che per rimuovere il tuo script commerciale dall'equazione, perché altrimenti non sarà in grado di misurare i clic in arrivo / in uscita, e potrebbe rovinare le statistiche e il software di analisi.
FORMAT:{{setlinktemplate-new link template}} | {{setthumbtemplate-new link template}} dove setlinktemplate e setthumbtemplate sono parole chiave speciali per attivare questa macro e new link template è qualsiasi cosa mettereste in un link o un modello di pollice
ESEMPIO{{setlinktemplate- %cat%
NOTE: Questo cambia tutta la formattazione del link sul modello corrente. È possibile utilizzare questo per modificare il formato di link o tabella su una sezione per base di sezione, ma è necessario combinare le opzioni di costruzione include e template, perché questa macro colpisce TUTTI i collegamenti su un modello. Pertanto, se si desidera sostituire il vostro stile di collegamento per una sola sezione, allora è necessario mettere le sezioni in diversi modelli, attivare questa macro sul nuovo modello, e quindi tornare alla pagina principale e includere il risultato.
Se si utilizza questo su un modello e poi includere un altro modello il vostro stile non sarà ereditato dal modello incluso, a meno che il modello non ha anche un modificatore setlinktemplate su di esso.
FORMAT:%this weekday-index% in cui l'indice è un valore da 0 a 6 che rappresenta 0 a 6 giorni fa.
ESEMPIOSe oggi era lunedì sul server allora,
%this weekday-0% = Mon
%this weekday-1% = Sole
NOTE: Questo crea un codice 3 lettere che rappresenta il giorno della settimana, il codice 3 lettere è caso sensibile. 'Mon,Tue,Wed,Thu,Fri,Sat,Sun' È possibile utilizzare questo quindi per creare un insieme di file di immagine che rappresentano intestazioni per i vostri giorni feriali. IE: Se avessi una serie di intestazioni chiamate, 'Lunedì.gif, Tueday.gif, Wedday.gif,Friday.gif,Satday.gif,Sunday.gif' (Nota l'ortografia), allora il tuo campo src img sembrerebbe come img src="%this weekday-0%day.gif".
Si noti che ci sono 2 variabili in gioco qui. Comus la ricostruirà una volta al giorno con nuove gallerie, all'ora in cui si imposta la richiesta a. Ma può anche essere fatto per rinfrescarsi periodicamente per riflettere i cambiamenti nei conteggi di clic ecc, dire una volta ogni 10 minuti, questo è controllato tramite il periodo di aggiornamento.
Puoi avere tutti i file che ti piace nel tuo sito. Per impostazione predefinita, lo script cercherà di assicurarsi che nessuno dei file utilizzi le stesse immagini due volte, anche se è possibile sovrascrivere questo, e tirare nuovamente le immagini per pagine personalizzate.
Di solito si desidera costruire il file di pagina principale prima, e poi costruire le sotto pagine, e poi infine costruire le pagine di archivio. L'ordine è importante, perché lo script eseguirà il Make File costruendo le pagine come le trova, e tirando dalle gallerie come va.
Il comando principale del makefile Template è la macro {{makefile-sourcefile-targetfile}}, dovemakefileè il comando di invocare questa macro efile sorgenteè il nome del file da utilizzare come modello sorgente, eProfilo targetè il nome dello script risultante o del file HTML che conterrà tutti i collegamenti e i pollici.
Puoi avere un numero illimitato di Template Files e puoi scrivere a un numero illimitato di Target Files. Quasi ovunque sul disco, a condizione di avere autorizzazioni.
Ogni file di destinazione è una pagina statica precompilata, e può essere di qualsiasi estensione o tipo di file. Si consiglia di fare html solo File di destinazione, perché caricano più velocemente, con meno carico del server, e sono meno costosi da eseguire.
Progettare un sito per Comus è praticamente lo stesso di qualsiasi altro sito web, con un ulteriore passo, di compilare effettivamente le pagine del sito attraverso lo script. È ancora possibile utilizzare i vostri strumenti di sviluppo standard, semplicemente caricare i file nella cartella /templates contenente tutte le macro, e poi lasciare Comus fare il resto, la costruzione e la pubblicazione dei file nel vostro sito.