Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I have themes, subthemes, and modules, that I want to contribute. I want to be able to set them out for the community to use and feedback. The theming includes my admin/form interface additions for popular themes - so the admin items look like this: http://striderlance.com/repository/images/theme-dark-stylesheet.jpg (for the dark stylesheets).
Among my modules are the user action tracking to csv, module to assign a different logo on different OG pages (taking it from the CCK field).
My desire is to open them to helpful criticism and grow as an active participant of Drupal community.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | canvas_theme.zip | 80.29 KB | alexrayu |
| #2 | og_logo_mod.zip | 26.28 KB | alexrayu |
| #2 | saen_mod.zip | 4.88 KB | alexrayu |
Comments
Comment #1
sunThanks for your application.
Why can't you contribute these additions to the original/actual themes instead?
Since you intend to create modules, we need at least one module for review, along with a description of what it does, and how it compares to existing modules that offer the same functionality.
Comment #2
alexrayu commentedHere is a canvas theme based on fusion (it is used to build themes of, taking advantage of interface additions like admin page elements, inputs, etc. Based on Fusion. og_logo module - that allows to set an own logo on each og page, taking it from a cck field. And a saen module. It works - but needs lots of constructive criticism and further development. Its function is to save user activity to csv files. (used for tracking survey usability). I did css formatting for the saen module - but the og_logo and the canvas have css in my favorite way - selector per line, rather than an attribute per line. A click to format in eclipse though, so if a certain way of css format is required - will not be a problem.
Comment #3
alexrayu commentedYes, I intend to contribute to existing themes as well. I especially would like to contribute to the Bartik (http://groups.drupal.org/node/65608). But in the case with the admin interface, it is an addition, which brings in certain preset to the existing themes. I noticed that admin elements in Drupal are quite flat - but also need lots of time to theme. And I did that. Yet, you can't use it for every site. For many minimalistic sites, you don't want such additions. So I realize it's not practical to include them into the actual themes.
Then, the modules - I included two. I have not seen direct analogs of these. They are small but helpful tools that do their specific tasks. Something which a client says "Can we..." and we can't easily do it without such module. Except maybe install a number of other power-hungry stuff and wire them together - like contexts, spaces - which may not be needed except just for that. Thats my rationale.
But thats not my sole motivation. For me, access to cvs is not only a way to contribute these two modules - but to closer integrate and participate in productive work, and open it for criticism and suggestion.
Comment #4
alexrayu commentedJust FUI - please see the data attached above.
Comment #5
avpadernoWe just review one module / theme per applicant. Let us know which module you prefer to be reviewed.
As per the theme, I think that sun is correct in what he reports.
Then, you don't have access to themes created by others, if the maintainers of those themes don't accept you as co-maintainer. Forking a third-party module, or them is so far not considered a good practice, in Drupal.org.
Comment #6
alexrayu commentedOk please review og_logo module then. Its less complex than the saen module.
Comment #7
avpadernoComment #8
alexrayu commentedI see. No need to review. Will use GitHub.
Comment #9
avpaderno