DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Issues at hand
There seems to be an issue with the proliferation of image repositories both on the wiki and the ooo-site. This proposal is to perform an overall cleanup and possibly suggest some enhancements and clarity to the way the the website and other related projects (marketing, branding) are structured.
Planning
The proposal includes certain conventions and sub proposals:
- Cleanup of the ooo-site/images folder, eliminate unused and unnecessary content from the folder.
- Improve the name convention to a more canonical file name.
- Consolidate repositories for all of the above
- Decide whenever content should still be kept in www-site as opposed to wiki
Goals
Provide a simpler and easier way to identify images through simplicity. As a community, future web developers will engage on this work and is important not only to document the work, but also make it easy enough for new comers to get a handle of the assets and structure.
Current work
The ooo-site has the following file structure:
Root files:
about.html faq.html news.html
brand.mdtext favicon.ico OOo_cake_smaller.png
CommunityNewsRightColumn.html.html footer.mdtext OO_thankyou.odt
contact_us.html google-analytics.js privacy.mdtext
contributing.html gulleggs_ooorc.gif project_issues.html
custom_404.html.html home.css quickbugzilla.html
custom_404.html.ja index.html redirect.html*
doctype.mdtext index-image-passthru.html right.gif
DomainFAQ.html.html index_new.html robots.txt
DomainFeedback.html.html index-old.html sitemap.css
DomainFeedback.html.ja lang.mdtext sitemap.html
DomainHome.html.html left.gif styles.css
DomainHome.html.ja license.html style-test.mdtext
DomainTermsOfUse.html.html LiveSearchSiteAuth.xml terms_of_use.html
donate-thanks.html lspintro.html topnav.mdtext
exceptions.css mail_list.html
extensions.html ml_guidelines.html
images/
action-bg.png action-social.png language.png logo-twitter-24.png
action-clipart.png action-templates.png licensing.png logo-twitter-32.png
action-contract.png aoo-logo-100x100.png logo-apache-16.gif marketing.png
action-dictionaries.png AOO_logos/ logo-apache-24.gif money.png
action-download.png apache-incubator-logo.png logo-facebook-16.png ooo-logo.png
action-expand.png art.png logo-facebook-24.png programming.png
action-extend.png asf-logo.png logo-facebook-32.png quality.png
action-help.png campaign-divider.png logo-googleplus-16.png ux.png
action-info.png distribution.png logo-googleplus-24.png valid-xhtml10-blue.png
action-link.png download-bg.png logo-googleplus-32.png writing.png
action-participate.png feather-small.gif logo-rss-16.png
action.png help.png logo-twitter-16.png
AOO_Logos/
AOO4_logo_cropped.png get-aoo-300x100.png
AOO4_website_logo.png IMLD_OO.png
AOOfeather_logo_webSite.png ooo-logo.png
AOO-logo-hires.jpg OOo_Website_v2_copy.png
AOO_orb2_logo_webSite.jpg orb.jpg
Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png orb.png
christmas-logo.png svg/
dfd-site-log.jpg
AOO_Logos/svg/
AOOfeather_logo_website.svg get-aoo_300x100.svg ooo-logo.svg OOo_Website_v2_copy.svg orb.svg
Legacy conventions
Certain convention on the filename can be identified on the images folder, a pre-identifier such as action as well as logo. The exception seems to be the asf-logo.png
AOO Logo folder uses AOO and AOO4 to dientify the core logos althought there are many files that don't follow such convention, such as Apache_OpenOffice_Logo...OOo_Website get-aoo-300x100 ooo-logo.png christmas-logo.png and dfd-site-log
SVG source folder follows no conventions.
New conventions
introduce the following conventions:
- main: for root-level html files
- logo: update logos with the <entity>-logo convention
- svg: adjust svg to only the AOO related logos (including event-type logos like www, dfd or christmas)
A good proposal is to also include other web project related sources like wiki, forums, extensions, templates, etc. A counter proposal is to get rid of the svg folder all together. Another proposal is to start using SVG as part of the website.