Cookies
This website uses cookies. Find out more here.
If you continue using our website, we'll assume that you are happy to receive cookies.
This website uses cookies. Find out more here.
If you continue using our website, we'll assume that you are happy to receive cookies.
This website uses cookies. Find out more here. If you continue using our website, we'll assume that you are happy to receive cookies.
This website uses cookies. Find out more here. If you continue using our website, we'll assume that you are happy to receive cookies.
This website uses cookies. Find out more here. If you continue using our website, we'll assume that you are happy to receive cookies.
This website uses cookies. Find out more here. If you continue using our website, we'll assume that you are happy to receive cookies.
This website uses cookies.
Find out more here.
This website uses cookies.
Find out more here.
This website uses cookies. Find out more here.
This website uses cookies. Find out more .
This website uses cookies. More .
This website uses cookies. More .
CTC Cambridge

How to write an article for the website

After you publish or update an article you should always review what it looks like on the website. To do this, move the mouse over the article name and then click on the "view" button. This will open the page on the CTC Cambridge website.

When reviewing a published article try clicking on a photo and check that it appears appropriately in the photo viewer, and whether any caption you supplied is displayed below the photo in the photo viewer.

Caching

Please be aware that after you publish an article, the page content will be cached on the web server. The  cache will be automatically rebuilt after a time. However this means that if you update an article and then look at it on the website you will probably not see your latest changes.

You can "refresh" the cached page content by carefully appending ?refresh to the page URL. Refreshing a page may take 30-60 seconds.

Labels

When you publish (or update) an article you are creating a new page on the website. However until you define a "label" your article will not appear in the index and will not be linked from anywhere, so it will only be visible to people who know the URL. This gives you an opportunity to double-check your article before adding it to the index.

To allow readers to find your article, add one of the following labels:

Ride reports

  • For ride reports, add the label news. This adds it to the "ride reports" index. It also adds a link to the "latest ride reports" section of the front page.

    (Yes, using the label "news" is a bit odd for ride reports, but we're stuck with it) 

Campaigning articles

  • For campaigning articles, add the label campaigning. This adds it to the "campaigning" index.

News items and other articles for the front page of the website

  • You can display short news items and other announcements on the front page of the website (as well as on their own page) by giving them the label frontpage-top, frontpage-large or frontpage-small

    • frontpage-top will position articles at the top of the page,
    • frontpage-large will position articles below them, and
    • frontpage-small will position articles at the bottom in one of two narrow columns (suitable for extremely short articles only).

    Only the webmaster, club secretary or runs secretary should do this. If you're not sure you can always publish the article and then ask the webmaster to add the label to put it on the front page.

    After adding one of these labels you can see what the front page of the website looks like by visiting https://ctccambridge.org.uk/?refresh (this refreshes any cached version and takes 30-60 seconds).

    To add an article to the "news archive", add the label announcement. This allows people to find your news item, even if it is no longer displayed on the front page.

    To create an "advert" for the article, add the label advert. This causes the latest three articles with this label to be promoted by small rectangular "adverts" which appear on the left-hand side (on large displays) or at the top (medium displays) of the page. You can use this for news items, campaigning articles or any other article.

  • Other possible labels are frontpage-top-test, frontpage-large-test, frontpage-small-test or advert-test. These can be used for testing. They are used by the staging website (or a local website) but are ignored by the production website.

General website articles

If your article isn't a ride report, a news item or a campaigning article then you may want to add it to the main index, which is the first thing people see when they click on the "Index" button. 

Publish the article as usual, without setting any labels. Then send the link to the webmaster and ask for it to be added to the main index.

Using "See more..." in front page announcements

If you're writing an announcement for the front page of the website, and your article is slightly too long, you can write a short introduction and hide the rest of the article behind a light-grey "See more..." link. If your article is very long then don't do this: it's better to write a separate news article which links to the full article.

Introductory text text.&nbsp;&nbsp;<div class="hideinitially">
<p>
More text text text.
</div>

Note that when the same article appears on its own page the "See more..." is omitted and the whole page is always displayed.

You can replace the text "See more..." with different words by setting the attribute data-showanchortext as follows:

Introductory text text.&nbsp;&nbsp;<div class="hideinitially" data-showanchortext="Show FAQs...">
<p>
More text text text.
</div>

This feature is ignored on actual blog pages. So a blog post that contains "See more..." links when it appears on the front page of the website will be displayed in full when it appears on its own page (e.g. when accessed via the index). However you can override this by adding the following to the top of your post:

<!-- enable the use of hideInitially constructs on this blog page -->
<script>let useHideInitially=true;</script>