GIMP is a cross-platform image editor available for GNU/Linux, OS X, Windows and more operating systems. It is free software, you can change its source code and distribute your changes. Whether you are a graphic designer, photographer, illustrator, or scientist, GIMP provides you with sophisticated tools to get your job done. When we do talk about open source web design software, we talk about WordPress, and occasionally the GIMPor something. In this article, I wanted to highlight some other open source projects that are active, lesser-known, and rather promising.
GNU Website Guidelines
Our goal is to get information to people. Keeping the sitedesign simple helps accomplish that.
- The GNU web server has only free software available. We prefer that only free software be used to prepare pages for the GNU web server. The GNU website lists and links only to free software. The software's source code and executables have to be freely redistributable and modifiable to and by all people and organizations.
- Amin is a free software activist, a GNU maintainer, and a GNU webmaster since early 2016. Brett joined the GNU webmastering team in late 2019. In addition to free software advocacy, he also champions functional programming, formal mathematics in software design, as well as hygienic and ethical computing practices.
Please be considerate of all who access our web pages, and accommodatethem, including those who use text-only browsers or old browsers, as wellas those with slow connections. We wish to prevent HTML design that looksgreat under one version of one browser, and ugly under many others. Ofcourse, please don't install any of the proprietary software browsersavailable if you don't already use them anyway.
Table of Contents
- Appendix 2 - Working with Web CVS Repositories
General Guidelines
- The GNU web server has only freesoftware available. We prefer that only free software be used toprepare pages for the GNU web server.
- The GNU website lists and linksonly to free software. The software's source code andexecutables have to be freely redistributable and modifiable to and byall people and organizations. If in doubt, ask <[email protected]>.
- The GNU website gives priority to software covered by eitherthe GNU General Public License or GNU Lesser General PublicLicense.
- The GNU website is more interested in substance than style.The use of graphics should be minimized so pages load fast overslow links.
- Offer a document in as many formats as the GNU Project has it.For an example, see The GNU FreeDocumentation License. This lets users get the document in theformat most useful to them.
- In addition to copyright and licensenotices, all pages should have contact info for both the FSF (orresponsible party) and the address for bug reports (webmasters forgeneral pages, but project-specific addresses otherwise) at the bottomof each page. The reason to note this at the bottom is so the useralways finds this information at the same place on each page.
- Before you take any graphics or text from another website,please ask for permission to use it. It's polite to do so. It is alsoessential for us to avoid copyright infringement.
- Before adding a link, check that it follows our linking criteria.
- Do not list an address of an individual, including themaintainer of a GNU package, unless explicitly asked to have itlisted. Most GNU maintainers do not want a lot of extra mail and preferto get bug reports, etc. from the GNU bug report mailing lists.
- On pages with dated entries (e.g., /philosophy/latest-articles.html),the newer entries should be first (i.e., reverse chronological order).
- Pages should not load CSS from servers other than those runby the FSF.
- Generally, the use of JavaScript is not allowed. Exceptions tothis need to be reviewed and approved by the Chief GNUisance on acase-by-case basis.
Copyright Guidelines
- Every page should have a copyright notice. See the boilerplate, referred below.
- Every page should have a notice giving everyone permissionto distribute it. If you cannot get such a permission from the author,please discuss the issue with the webmasters before posting it. Thisapplies to CSS as well as to HTML.
- Normally you shouldn't post a page that isn't copyright FSF unlesswe have permission to modify the version we publish. If you cannotget such a permission from the author, please discuss the issue withthe FSF before posting it. This applies to CSS as well as to HTML.
- If ultimately we decide to post a new page we don't have permission tomodify, put the text “Posted in 20XX without FSF permission tomodify” inside an HTML comment, just after the copyright notice.
- The user of our pages should always find the copyright informationat the same place on each page. If the page is copyrighted by someother person or entity, use per or its copyright notice instead of theFSF copyright notice. Use the rest of the FSF's normal footermaterial, except when there is a specific reason to change somethingin it.
- All pages that explain how to do something, such as how to usecertain programs, are documentation. This includes all the pages in
/software/
that describe specific programs. By ourprinciples, documentation must befree. So these pages must carrya freelicense. If such a page doesn't have a free license, please report theproblem to <[email protected]>. - For other pages, use the same license as some other page that servesa similar kind of purpose.
Spelling and Punctuation
- English pages should follow the standard American spelling,hyphenation and punctuation conventions.
- Since these conventions are not always very specific, especially asregards hyphenation and quotes, gnu.org adds its own rules for the sake ofconsistency:
- “Nonfree” is preferred over “non-free;” likewise, “noncommercial” over “non-commercial”.
- In ordinary text, HTML entities ““..”” and “‘..’” are preferred over straight quotes ('..' and '..'). This doesn't apply to script-generated documents.
- Where they exist, the double spaces after sentence breaks should be preserved. They enable Emacs sentence commands to do the right thing.
Filenames
- To make simultaneous edition of many files easier,try and give each HTML file a unique name; the filename
index.html
should only be used as a symbolic link, asexplained next. - Each directory in the web server tree should have asymbolic link named
index.html
to the top-level HTML filefor that directory. Use the.symlinks
file to handle this. - If you translate your web page in differentlanguages, please name the English file
ARTICLE.html
, andits translationsARTICLE.LANG.html
. LANG should contain thetwo-letter language code from ISO 639,and optionally an hyphen followed the two-letter country code given inISO 3166. For example, the German translation ofnot-ipr.html
should be namednot-ipr.de.html
; the Brazilian Portuguesetranslation should be namednot-ipr.pt-br.html
.
URLs
- Hand-written URLs that refer to other files on www.gnu.org should beabsolute, starting from the root page. That is, paths should startwith
/
(e.g.,/gnu/about-gnu.html
; nothttp://www.gnu.org/gnu/about-gnu.html
, and notabout-gnu.html
). This makes it easier to copy and pastelinks from other pages. Besides, links likehttp://www.gnu.org/
will be wrong when the visitor usesHTTPS. - Collections of files produced automatically from Texinfo sourcecontain links with relative file names. They always refer to anotherfile in the same directory. These relative links are to betolerated.
- Don't use just a directory name in a URL; always include thespecific filename. E.g., use
/gnu/gnu.html
, not just/gnu/
. Never useindex.html
in a URL. Both ofthese are kindnesses to the user, as browsers change the highlighting ona link after it has been visited. If links to a given file use severaldifferent URLs, the URLs that haven't been explicitly referenced willnot be highlighted as visited. So the user goes to pages he/she hasalready seen, which is irritating. Also, this eases maintenance of the siteas things get moved around. - Be sure to omit the filename entirely when linking to an anchor inthe same file.
- Consider others linking to your page when removing an anchor or
id
attribute. - Cite FTP locations of source code with the full URL of thedirectory they are in:which browsers display this way:
<a href='https://ftp.gnu.org/gnu/foo'>https://ftp.gnu.org/gnu/foo</a>
https://ftp.gnu.org/gnu/foo
We encourage FTP sites to use a directory for each package, and only putone package's files in each directory, so that the users can see whatversions of that package and related information can be downloaded(e.g., aREADME
file, information of what versions areavailable, documentations, fonts, etc.). Also, it means that the FTPlocation URLs do not need to be changed, on this and other sites, as newversions are released into that directory. - Cite people with e-mail addresses this way:which browsers display this way:
<a href='https://www.stallman.org/'>Richard Stallman</a><a href='mailto:[email protected]'><[email protected]></a>
Richard Stallman<[email protected]>
It is less confusing to the user, because it's clear what is ahttp(s):
link to another web page and what is amailto:
anchor thatwill bring up a mail form to fill out and send, if this issupported by the client. Also, if users save a copy of the page,they will have a copy of the e-mail address they can use withoutgoing back to their web browser. If the person doesn't have a webpage, leave the name unanchored. - When embedding static resources like videos that are not inthe
www
CVS repository along with the rest of thewww.gnu.org pages, it's important that the URL used to embed the assetbe a subdomain of gnu.org, so that the Third-party Request Blockeradd-on shipped with GNU IceCat would not consider it a third-partyasset which it would prevent from being loaded. For example, whenembedding videos from FSF campaigns on www.gnu.org, usestatic.gnu.org
rather thanstatic.fsf.org
.Both of these addresses have been set to point to the same machine, sothey can be used interchangeably.
HTML Guidelines
- HTML on the GNU web server should be strictly compliant withW3C standards.
- Please follow the above mentioned web standards strictly. Don'tneglect requiredelements such as <html> <head> <title><body>, etc. when using (X)HTML, and always include theappropriate DTD or Schema reference. This appeases overly pedanticbrowsers.
- Do not add comments at the top of a document. Web browsersexpect the doctype, XML declaration, or Schema to be at the top.Comments will confuse them, and often cause them toincorrectly interpret your markup.
- The <head> element should contain this line:Some browsers use this information to allow users to easily reportproblems they find on a page.
<link rev='made' href='mailto:[email protected]'>
- The first header tag, <h[n]>, should have its textduplicated at the start of the <title> tag. The <title> tagis used by many browsers in menus like the history and bookmarks lists,as a link to that page. Repeating the main heading in the <title>ensures that, whenusers click on an item in these menus, they get a page with the expectedheading. Please properly use your headers in numerical order: 1, 2,etc. These are not used for looks, but for the organization of thedocument.
- The <title> tag should include the phrases “GNU Project”and “Free Software Foundation” so the pages will be foundwhen web search engines are used. The default is to add this at theend:
- GNU Project - Free Software Foundation
. - Acronyms/abbreviations:
- Never use
<acronym>
: HTML5 obsoletes it in favor of<abbr>
. - Don't use
<abbr>
unless for a really compelling reason. Browsers render it in an ugly way. - When an abbreviation may be unfamiliar to a reader, give its expansion the first time it is used in a document, like this:
<abbr>EA</abbr>
orEA (Expanded Abbreviation)
. - Further occurrences, in any case, should be written without any markup: just
EA
. - For common-enough initialisms, such as GNU, FSF, BSD, RAM, HTML, DVD, and so on and so on, no markup is needed at all. Use your judgment.
- Never use
Tables and menus
- Please use tables to organize data, not the presentation of theweb page.
- Screen reader software used by most blind people reads the textfrom left to right, ignoring any tables that you make. If you usetables, you should make sure that reading a wholepage left to right doesn't confuse such software. Please follow theW3C web accessibility guidelinesto ensure that tables are properly marked for accessibility.
- Some people like to organize links as a menu tothe left or right of the main text when using graphical browsers. Thatdoes not work very well with text browsers since they will make themenu appear either on top of the page or at the bottom. If you havea menu that is more than 30 lines long, then it's very probablethat a user viewing the page will never bother to read the textbecause it will be too far down. You should make an effort to keepsuch menus under 20 lines long so that the beginning of the article isvisible on the first page when viewing it with a text browser. Amenu bar of one or two horizontal lines might accomplish yourpurpose as well. Providing a “skip link” to the main textis another option.
Using our page template
- To help people follow the above guidelines, a page template (or“boilerplate”) is provided for both the main part of the GNUwebsite, and the software projects. Its use is mandatory for new pages inwww.gnu.org, and highly recommended for software pages. Please don't startout with an existing page to create a new one; use the original source of the boilerplate instead, and follow the instructionsin it.
- The templated pages must follow the XHTML-1.0 guidelines.
- Our server-side includes declare UTF-8 as the character encoding, sousing any other encoding is problematic.
Styling
Styling of templated pages
- Generic styling for desktops and smartphones is provided by two CSS:
/reset.css
(from the YUI library, version 2), which normalizes the default rendering of allHTML elements by the various browsers, and/layout.css
, whichcontains gnu.org-specific formatting. A few responsive elements are definedin/layout.css
. They cover most of our use cases. - Mobile devices with very limited resources use
/mini.css
.This stylesheet is just the YUI (version 2) reset and base stylesheets, as thesedevices typically have minimal need for various fonts and no need forfancy layouts. - Printers use
/print.css
. Note that the header, navigationbars and footer (except copyright and license) are unprintable. - If some special styling is needed for a specific page, it should be addedto the page itself in a <style> element, between the SSI directivesthat include
header.html
andbanner.html
. If thestyle applies to a single element, it should normally be added as an attribute. - If you specify any color attribute in the HTML, you should specify all ofthem that are allowed for that tag. This is because some browsersallow users to specify defaults for the color attributes, and theuser's choices could conflict with your choices, as your choicesoverride the user's choices. In the worse case, the foreground andbackground could end up the same. Please use a stylesheet forthis, and not HTML 3.2 (HTML 4 Transitional) deprecatedmarkup.
- Note about grids: Very few pages currently use them. In theevent you'd like to create one that does, good starting points may befound in YUI version 3, and Pure Grids. The components provided bythese libraries are licensed under the modified (3-clause) BSD license.
Other stylesheets
- Historical pages (unmaintained translations for the most part) referto
/gnu.css
, which in turn loads/mini.css
,as these pages areusually very basic, plain pages with little or no formatting. - Some software manuals use a dedicated CSS,
/style.css
. - Translators maintain stylesheets (
/style.LANG.css
) thatmodify layout.css according to their own needs. The RTL languages (Arabic,Persian, and Hebrew) use/style.rtl.css
.
Use of Graphics
- The use of graphics should be minimized, so pages load fastover slow links, especially animations.
- We do not use background images on our pages, as they make textsignificantly harder to read.
- In the past, GIFs have had patent problems. However, now thatthe IBM and Unisys patents (and other patents worldwide that arerelevant to LZW compression) have expired, GIFs that are based on the87a or 89a standard are acceptable. Please be wary of proprietaryapplications that may include non-standard patented technologies (we'dprefer you use free software applications when authoring for ourwebsites). In general, PNG or JPEG format are still safe, and areprobably better from a technical standpoint. For details regarding theold GIF problem, see https://www.gnu.org/philosophy/gif.html.Other formats are also allowed, though JPEG is the one most widelyrecognized by web browsers (avoid JPEG 2000, and be careful with PNGalpha channels; the former is not widely supported, and the latter arenot fully supported by some older browsers).
- Before you take an image from another website, please ask forpermission to use it.
- Always have a textual alternative for in-line images, for peoplewho have text-only access to the web. For instance:We add the non-breaking spaces ( ) and square brackets toseparate the DESCRIPTIVE TEXT from adjacent text, and help the userrealize that this is a stand-in for an image. The point of usingnon-breaking spaces rather than normal ones is to make sure they findtheir way to the translatable strings that are extracted by thePO4A/Gettext tools.
<img src='/graphics/*.jpg'alt=' [DESCRIPTIVE TEXT] '>
- Make sure the image doesn't look too big or too smallwhen displayed at its original size, using the browser's default fontsize.
- Adjust image width or height in a style attribute, using scalableunits such as
em
or%
; for instance:Macbook air 2019 webcam.This way, the page will look the same if the reader increases ordecreases font size.<img src='/graphics/*.jpg'alt=' [DESCRIPTIVE TEXT] 'style='width: 10em' />
- If you are adding a small floating image to a page that uses
layout.css
(the stylesheet for templated pages),you may want to use theimgright
orimgleft
class(defined in the IMAGES section of the stylesheet). This will ensure thatthe floating direction is reversed if the page is translated into an RTLlanguage. - If the image you are adding is 12em wide or more, and the page istemplated, you may find it convenient to use one of the responsive
pict
classes that are defined in the IMAGES section oflayout.css
(you can adjust the width in a styleattribute if none of the predefined ones fits your needs); for instance:Note that the<divstyle='width: 25em'><img src='/graphics/*.jpg'alt=' [DESCRIPTIVE TEXT] '/></div>
div
container is necessary because some browsers (e.g.,NetSurf) don't know how to applymax-width
to images. - Link all images that are displayed throughout the website to therelevant page, usually inThis will allow users to quickly go to pages related to the pictures theyare interested in.
/graphics/
. This can be done withcode similar to this, which corresponds to the image on the left:
Appendix 1 - Linking Policies
One of the most complex aspects of maintaining web pages is following thelinking guidelines; however, it's also a very crucial aspect of the job.
We strive to ensure that all pages we promote—all pages which are givenlinks on our site—are friendly to the free software movement. Somepages will obviously not meet such standards; if the site flames the FreeSoftware Foundation, or has no apparent relation to free software andsurrounding issues, the link shouldn't be made. Beyond that, however,there are criteria used in determining whether or not it is appropriate toprovide a link to a page from ours. They are listed below, in order ofdescending general importance.
The link's purpose on our site will play a role in determining howstrongly it should be judged against the other criteria. Pageshosting GNU projects will be held to the highest standards. Pagesabout other free software and given high promotion—for example,included in a newsfeed on the main page—are a close second.Links on the philosophy page may be given more leeway in talkingabout proprietary software; GNU/Linux user group pages should callthe system GNU/Linux almost always but are hardly checked on othercriteria. Always keep this in mind when deciding how to weigh eachaspect of these policies.
The big point made by the free software movement is that proprietarysoftware presents an ethical dilemma: you cannot agree to suchnonfree terms and treat those around you as you would like to betreated. When proprietary software is promoted, people get theimpression that it is okay to use it, while we are trying to convincethem otherwise. As such, we avoid offering such free advertising,either directly on our site or indirectly through links.
What's tricky about this criteria is the “promotion” point: there'sa difference between mentioning proprietary software and making asales pitch for it. Indeed, the GNU Project website mentionsproprietary software throughout, but never gives people the impressionthat its use does not present ethical problems.
There are two things to keep in mind when determining whether areference to proprietary software promotes it, or simply mentionsit. First, how much information does it offer about the software?Second, how much information is the reader likely to actually gainfrom this page?
Different pages provide different amounts of information aboutproprietary software; the more it provides, the more of a problemit poses for us. For example, some pages may link to the primarysite for a proprietary software program. Others may describe itsfunctionality in detail. Even the product name given matters;there's a difference between “Windows” and“Microsoft Windows XP Home Edition.”
If the page requires nonfree,nontrivial JavaScript and has serious failures withJavaScript disabled, the link shouldn't be made. Similarly, if the pagehas embedded Flash that plays an important role, so that a person wouldbe missing something important if the videos do not play, the linkshould not be made.
The subject of the reference will also play a role in determininghow problematic a reference is. If the software is already verypopular, it's unlikely that a basic mention of it will be news tothe reader. Some examples of proprietary software which are commonenough to be considered “well-known” are major operating systems(Windows, Mac OS, Sun OS, HP-UX) and primary common applicationssuch as Office, Internet Explorer, Photoshop, Acrobat Reader, andFlash.
GNU software project pages feel the full force of this policy.Proprietary software should only be mentioned when the GNU softwareprovides support for it, or to compare it against the features ofwell-known proprietary software. For example, the followingtext—and not much else—would be acceptable:
w3 is a web browser for GNU Emacs, similar to Internet Explorer.It can run on all platforms GNU Emacs runs on, including GNU/Linux,proprietary Unix systems, and Windows.
Links which appear in other areas, such as the testimonials orphilosophy pages, as well as links to user groups may discuss suchsoftware in greater detail, but links and other methods ofencouragement to “learn more” should still be avoided.
Almost all pages which have links on our site should, at the veryleast, treat free software and open source equally. Failure to doso—whether it be by omitting free software or by implying thatopen source is superior—is usually unacceptable. GNU softwareproject pages should have little mention of open source. The GNOMEpage used to provide a good example of a tactful way to do it:
GNOME is part of the GNU Project, and is free software (sometimesreferred to as open source software).
Any exceptions to this rule should be apparent from the context.For instance, user groups pages may talk in greater detail aboutopen source; we state on the user groups page, “As with our linkspage, the FSF is not responsible for the contents of other websites,or how up-to-date their information is.”
Pages which we link to should treat the GNU Project well. Theprimary thing to look out for in this regard is whether the pagecalls the system GNU/Linux or just “Linux.” GNU software projectand user group pages should almost never, if ever, fail to do this.Again, exceptions for other pages should be apparent from context.
![Design Design](https://a.fsdn.com/con/app/proj/cbadvanced/screenshots/GIMP.jpg)
That said, certain parts of a page should not be considered against thesecriteria. For example, suppose we were to make a link to a page on a freesoftware news site. Any advertisements or reader comments attached to thearticle would not be considered when determining whether it met or linkingguidelines, since they're understood to be the opinion of their individualauthors. Similarly, on user group pages, the contents of forums and wikipages should not hold weight in these regards.
Finally, some sites are understood to always have exception with most ofthese guidelines. These sites are usually about issues which areimportant, but somewhat peripheral, to the free software movement. Severaltimes we have linked to the Electronic Frontier Foundation's site, eventhough they encourage the use of Flash and talked exclusively about opensource software. It's generally understood that since these pages are notprimarily about free software, the policies do not hold full force forthem.
As a final explanation (coming from RMS):Even for making links from www.gnu.org, we do not require thatpeople call the system GNU/Linux or use the term “free software”rather than “open source.” We do, however, require that they notpromote any nonfree software.
If all this seems complicated, that's because, unfortunately, it is. Don'tworry; a knack for it comes with time and experience. You may mis-evaluatea few pages as you're learning to get a feel for what's acceptable and whatisn't; please don't hesitate to get a second opinion from a moreexperienced webmaster, or someone in charge like the Chief Webmaster orRMS. New exceptions will always come up; keep an open mind to thatpossibility and be ready to handle them properly.
Appendix 2 - Working with Web CVS Repositories
Basic CVS commands
- Before the initial checkout, set the environment variable
CVS_RSH=ssh
. - If you have write access to www, check out the main www repositorywith your Savannah login:You will get a working directory,
www
, with the samestructure as our main website. - If you don't have write access to www, you can still make ananonymous checkout of www:
- Check out the web repository of the fooproject:You will get a working directory,
fooproject
, with the samestructure as thewww/software/fooproject
subdirectory. Note,however, that the fooproject and www repositories are independent. Theworking directories can be anywhere in your filesystem.Webmasters, please read Web pages forofficial GNU software before committing anything to the web repositoryof a software project. - Add a file or directory:
- Update before you edit a file:
- Check the changes you are going to commit:
- Perform the commit (no need for
cvs add
if the file isalready in the repository):This will open a text editor where you should enter a log message. Thecommit will occur upon saving the message.Without being excessively verbose, log messages should describeas clearly as possible the nature of the commit, including any relatedticket numbers from RT to allow future historians to understand why yourchanges were made.Whenever possible, changes to multiple files that share the same logmessage should be bundled in one commit. Do not bundle multiple unrelatedchanges in one commit.The changes (except to .symlinks files) shouldbe visible on www.gnu.org within minutes.
Free Software Gnu
For further details on CVS, such as reverting to a previous version, orlooking at the
diff
output of a particular change, see the CVS documentation. Moom 3 2 13 – versatile window manager.Symbolic links
Since CVS is not able to handle symbolic links directly, a separatemechanism has been implemented to allow webmasters to maintain symboliclinks, as follows. (Actual symbolic links are no longer created onwww.gnu.org; mod_rewrite rules are used instead. But we'llkeep this discussion talking about symlinks since it is easier tounderstand that way.)
Being a symlink means that relative links from the linked pagemay break when the symlink jumps to a different directory.
Special files, named
.symlinks
, when committedto the CVS tree, are interpreted as specifications to buildsymbolic links.Each symbolic link specification from the .symlinks file is honored,i.e., the symbolic link is created if it does not exist yet. If asymbolic link is found in the directory and is not listed in the.symlinks file, it is removed.The .symlinks files obey the
ln -s
format, as described below:- Lines starting with a sharp sign (“#”) are ignored.
- Lines that do not contain two strings separated by white space are silentlyignored.
Here is an example of a .symlinks file:
![List List](https://windowsreport.com/wp-content/uploads/2017/12/website-builder5.png)
On each line the first file name must be a relative path name to anexisting file. The second file name may not contain any slash; it is thename of the symbolic link to be created in the present directory. Forinstance, if a page named
DIR.html
exists in the/DIR
directory, and index.html
does not exist,/DIR/.symlinks
should contain a line like this:Gnu Software List
The
ln -s
analogy accounts for only part of the story.The current method actually takes advantage of the flexibility of URLrewriting. Thus a single HTML entry in the .symlinks file defines linksto all possible translations that follow our namingconventions. This makes it impossible to usesymlinks to redirect to and from HTML files whose names look liketranslations, that is, page.LL.html
orpage.LL-CC.html
, where LL and CC are two-lettercodes. When you need such redirections, use the htaccess mechanism.These days, the .symlinks handling happens on www.gnu.orgvia a cron job that runs twice an hour. Webmasters do not haveaccess to it.
.htaccess and redirections
To browsers, the symbolic links in the previous section areindistinguishable from the actual file. You may want an actualredirection in some cases. You can do this either in the top-levelcontrol file
.htaccess
, or by using something like this as thefile to be redirected:<meta http-equiv='refresh'>
Scripts
A description of scripts andsoftware used on www.gnu.org is available. Please read it beforewriting any scripts, and also update it as needed if you have writeaccess to www.
System administrators
The system administrators for GNU change from time to time. Full free video editing software. Pleaseemail the sysadmin list <[email protected]> rather than an individual,unless you have a specific reason to do so.
Useful Resources
- Outside gnu.org:
- We follow the guidelines of the Best Viewed with Any Browser campaign.
- Basic info on the web and its technical specifications can be found at The World Wide Web Consortium.
- Use of the ISO standard for the Hypertext Markup Language (HTML) allows for consistent backwards compatibility among web user agents.
- The GNU web server follows the w3.org Style Guide.
- On gnu.org:
- The GNU Website Guidelines;
- Guidelines for Web Page Creation at www.gnu.org;
- Appendix B Tips and Hints, and other style tips in the Texinfo Manual;
- GNU Accessibility Statement;
- Guide to translating GNU web pages into other languages;
- Tips for webmasters to make translators' job easier;
- Documentation for Savannah, the SourceForge clone dedicated to the GNU Project;
- README for the
/prep/gnumaint/
directory (those files are primarily used by GNU maintainer administrators, and occasionally by GNU webmasters, to update the/*/allgnupkgs.html
files in www). - Here is the help we need with our web server.
An open-source GUI prototyping tool that's available for ALL platforms.
Pencil is built for the purpose of providing a free and open-source GUI prototyping tool that people can easily install and use to create mockups in popular desktop platforms.
The latest stable version of Pencil is 3.1.0 which contains stability fixes and many new features. More details can befound in the releaste notes.
Download for Windows x64Version 3.1.0.ga, x64 .exe, ~83 MB
For other platforms? See all downloads »
Project News
Oct 19, 2019 Pencil 3.1.0 is released released.
Jun 27, 2017 Pencil 3.0.4 is released released.
Jun 06, 2017 Pencil 3.0.3 is released released.
May 11, 2017 Pencil 3.0.2 is released released.
Feb 20, 2017 Pencil 3.0.0 GA is now released.
Gnu Web Design Software Download
Feb 09, 2017 Pencil 3.0.0 rc2 is available for testing.
Gnu Project
November, 2015 Development for the new version of Pencil started.