|
| 1 | +title: Creative Commons Chapter Websites network |
| 2 | +--- |
| 3 | +categories: |
| 4 | +wordpress |
| 5 | +website |
| 6 | +chapters |
| 7 | +--- |
| 8 | +author: hugosolar |
| 9 | +--- |
| 10 | +pub_date: 2019-07-03 |
| 11 | +--- |
| 12 | +body: |
| 13 | + |
| 14 | + |
| 15 | +This year, Creative Commons launched a new communication tool to improve the chapters work around the world. The rationale behind this tool is to "*Ensure the network is creating value for members*" providing a site network that try to be a useful and easy to use tool for the Creative Commons chapters. |
| 16 | + |
| 17 | +## Technology |
| 18 | +This network was built in WordPress in its "Multisite" mode. This means we can create multiple websites with a single Wordpress install, this has a lot of benefits in terms of administration and visual consistency. |
| 19 | + |
| 20 | + |
| 21 | + |
| 22 | +*CC Netherlands homepage from beta testing stage* |
| 23 | + |
| 24 | +### Theme |
| 25 | +The work behind this network is based in a single [WordPress theme](https://github.com/creativecommons/wp-theme-cc-chapter) which is assigned by default in every new site created. This theme uses all the capabilities availables on WordPress such as `Custom post types`, `Custom Taxonomies`, `Widgets`, `Metaboxes` and so on. To ease the backend development work I choose a Development Toolkit for WordPress named [Queulat](https://github.com/felipelavinz/queulat), which provide a lot of powerful tools to create and maintain Custom Post types and its own queries, metabox creation and a powerful form factory with many useful elements. |
| 26 | +The theme file structure is aim to be as logical as posible and following the [recommended structure](https://developer.wordpress.org/themes/basics/organizing-theme-files/) from WordPress in order to keep the files in a semantic order ready for community colaboration. |
| 27 | +The theme front page was built using sidebars and widgets in order to increase its flexibility, there are a lot of widgets for each website content which can be configured and placed into homepage sidebars and splitted in columns as needed. |
| 28 | + |
| 29 | + |
| 30 | + |
| 31 | +*Event Post type with custom data metabox* |
| 32 | + |
| 33 | +### Gutenberg |
| 34 | +The new WordPress editor is a whole new experience for me, as they say "*We call the new editor Gutenberg. The entire editing experience has been rebuilt for media rich pages and posts. Experience the flexibility that blocks will bring, whether you are building your first site, or write code for a living.*" |
| 35 | +I decide to take advantage of this new feature by creating customizations for the websites like custom styles, a custom color palette for button block, and responsive support for most common Gutenberg blocks to keep the content as flexible as posible |
| 36 | + |
| 37 | + |
| 38 | + |
| 39 | +*Gutenberg custom button block* |
| 40 | + |
| 41 | +### Frontend |
| 42 | +Thinking on scalability and maintenance I like to build website styles using [SASS](https://sass-lang.com/) preprocessor. For layout, I like to modularize elements and use a standardizing format like the Microformats specification (in this case [hAtom](http://microformats.org/wiki/hatom)), this helps new developers to understand the layout and the code in a better way and also helps to optimize crawling from search engines. |
| 43 | + |
| 44 | +## The future |
| 45 | +We're working on improve this website network and pushing forward a lot of new features requested by the community. They can be [tracked here](https://github.com/creativecommons/wp-theme-cc-chapter/milestone/2). Some of the most important features in the future will be: |
| 46 | +- CCsearch Integration |
| 47 | +- Easy Attribution |
| 48 | +- Post formats compatibility (Image, video, gallery) |
| 49 | +- More post types and widgets |
| 50 | + |
| 51 | +Also, we're planning on providing the chapters data via the WP-API so it can be used in other CC websites (The CC Global Network for instance), so we can show information from what's going on in the whole network |
0 commit comments