Compony.io roadmap issueshttps://gitlab.com/Compony/compony-roadmap/-/issues2020-02-23T22:16:55Zhttps://gitlab.com/Compony/compony-roadmap/-/issues/103The Compony logo with the name2020-02-23T22:16:55ZMathieu SpillebeenThe Compony logo with the nameWe will be starting with [reaching out to Drupal/Front-end events globally to partner up in promotion](https://www.compony.io/promoting-your-event).
However, we don't have a logo yet, that conferences can use with the word "Compony" in....We will be starting with [reaching out to Drupal/Front-end events globally to partner up in promotion](https://www.compony.io/promoting-your-event).
However, we don't have a logo yet, that conferences can use with the word "Compony" in.
Therefor a ticket with some suggestions on branding. Let's have a comment per suggestion (as Gitlab supports threading)
/CC @thomasfavahttps://gitlab.com/Compony/compony-roadmap/-/issues/100Blogpost: The new concept of stimulating component variations2019-12-10T05:41:35ZMathieu SpillebeenBlogpost: The new concept of stimulating component variationsA front-ender is massively opinionated. So opinionated in fact that, they will rather give up their job, then to give up their opinion.
Compony.io differs from Drupal.org in it's way of how it motivates forking and variations.
This i...A front-ender is massively opinionated. So opinionated in fact that, they will rather give up their job, then to give up their opinion.
Compony.io differs from Drupal.org in it's way of how it motivates forking and variations.
This is one of the points I make in my presentation, but we should also explain that through the platform, as that is a quite essential piece for spreading the word on Compony.
Explenation from here: https://www.youtube.com/watch?v=XMkIjhxt0Jg&t=2200shttps://gitlab.com/Compony/compony-roadmap/-/issues/99A new process for installing and updating components2019-12-19T13:43:20ZMathieu SpillebeenA new process for installing and updating componentsHaving talked with a lot of people, there is a strong wish from the community to have an automated way of installing or updating components.
Therefor, we have a mini-series of blogposts on updatability:
* [The different update proces...Having talked with a lot of people, there is a strong wish from the community to have an automated way of installing or updating components.
Therefor, we have a mini-series of blogposts on updatability:
* [The different update processes currently in existence](https://www.compony.io/blog/labeling-different-update-processes).
* [The side-effects of each of these update processes](https://www.compony.io/blog/nuances-updatability).
* [Inspecting Composer and NPM’s updatability](https://www.compony.io/blog/inspecting-composer-and-npms-updatability).
* [Updating Compony components](https://www.compony.io/blog/how-update-your-downloaded-components).
This ticket is to gather feedback, explore ideas, iterate of brainstorm on a better approach of updating and installing components from Compony.https://gitlab.com/Compony/compony-roadmap/-/issues/98Find a second "contact for Code of Conduct"2019-11-19T11:50:04ZMathieu SpillebeenFind a second "contact for Code of Conduct"Inspired by https://gitlab.com/Compony/compony-roadmap/issues/84#note_246114868 it would be good to find another Contact for Code of Conduct.
This would mean that a person that is being harassed would be more inclined to contact someon...Inspired by https://gitlab.com/Compony/compony-roadmap/issues/84#note_246114868 it would be good to find another Contact for Code of Conduct.
This would mean that a person that is being harassed would be more inclined to contact someone that is not a dude for example.
This would need to be someone that has some experience in handling conduct, or is willing to learn.
Currently the only person is me (Mathieu): https://www.compony.io/contact-code-conducthttps://gitlab.com/Compony/compony-roadmap/-/issues/97Allow users to add projects built with Compony2020-01-10T18:24:03ZMathieu SpillebeenAllow users to add projects built with ComponyAs a follow up from https://gitlab.com/Compony/compony-roadmap/issues/96, It would be ideal if Compony.io users could add projects to their own profile page.
Then we could pull a list of all projects and show them on the frontpage (or m...As a follow up from https://gitlab.com/Compony/compony-roadmap/issues/96, It would be ideal if Compony.io users could add projects to their own profile page.
Then we could pull a list of all projects and show them on the frontpage (or make a landing page for them)https://gitlab.com/Compony/compony-roadmap/-/issues/96Add projects using Compony.2020-01-13T09:31:03ZMathieu SpillebeenAdd projects using Compony.Inspired by @ragnarkurm in https://gitlab.com/Compony/compony-roadmap/issues/95:
It would be good to show adoption of Compony, by contacting people that are already using Compony for some time, and ask which projects that are currently ...Inspired by @ragnarkurm in https://gitlab.com/Compony/compony-roadmap/issues/95:
It would be good to show adoption of Compony, by contacting people that are already using Compony for some time, and ask which projects that are currently already built using Compony.
On the homepage it would be good to show the logo's of the websites that are built using Compony as a part of their build.
The logo's could then link to the websites that were built (or not if you decide you don't want that)https://gitlab.com/Compony/compony-roadmap/-/issues/95Awareness: Testimonials2019-11-18T15:39:34ZRagnar Kurmragnar.kurm@gmail.comAwareness: TestimonialsAdd a written experience of a frontend developer to Compony pages?Add a written experience of a frontend developer to Compony pages?https://gitlab.com/Compony/compony-roadmap/-/issues/93Post the announcement on social media2019-11-17T13:17:27ZMathieu SpillebeenPost the announcement on social mediaAs part of #87:
When we launched Compony.io, we reached out to loads of Drupal communities on Slack, Facebook pages & groups, Linkedin groups and anyone else that could reach our global community.
While [our social page](https://www.c...As part of #87:
When we launched Compony.io, we reached out to loads of Drupal communities on Slack, Facebook pages & groups, Linkedin groups and anyone else that could reach our global community.
While [our social page](https://www.compony.io/social) is a good start, we should be able to harness the strength of individual community members Facebook pages and groups and letting people show their support by posting in their local group.
For this we should localise the announcement. So here follows a list of translated content:
More languages are very welcome! Also let us know where you spread the word!
## English
Announcing a new and opinionated approach to bring cutting edge Front-end to Drupal
🔥 A component-only theme
👩💻 A hand-tuned Gulp
🌈 A #frontend #Drupal platform for #themers and #designers to collaborate 👊🏾
Check check 👉🏻 https://www.compony.io/blog/what-compony |
## Swedish
Annonserar ett nytt tillvägagångssätt från det allra senaste inom front-end utveckling i Drupal
🔥 Ett komponent drivet tema
👩💻 En skräddarsydd Gulp uppsättning
🌈 En #frontend #Drupal plattform för #Teman och #Designers att samarbeta i 👊🏾
Kolla in 👉🏻 https://www.compony.io/blog/what-compony
## French
Une nouvelle approche surprenante s’annonce d’apporter de la technologie de pointe Front-end à Drupal.
🔥 Un thème composant-unique
👩💻 Le Gulp personnalisé, sur mesure
🌈 Une plate-forme #frontend #Drupal permettant au #themers et #designers de collaborer 👊🏾
Vérifiez, Vérifiez 👉🏻 https://www.compony.io/blog/what-compony
## German
Ankündigung: Ein neuer Ansatz um Drupal mit hochmoderner Front-end Technologie zu vereinen.
🔥 Ein Theme das vollständig auf Components basiert.
👩💻 Eine von Hand gecraftete Gulp-Konfiguration
🌈 Eine Drupal Front-end Plattform für Themer und Designer zur gemeinsamen Zusammenarbeit. 👊🏾
Schaut rein auf 👉🏻 https://www.compony.io/blog/what-compony
## Portuguese
??
## Spanish
Anunciamos un nuevo sistema con lo último en Front-end para usar en Drupal
🔥 Un tema basado en solo componentes
👩💻 Un Gulp manualmente optimizado
🌈 Una plataforma colaborativa Front-end para themers y diseñadores Drupal 👊🏾
https://www.compony.io/blog/what-compony
## Dutch
Een eigenwijze aanpak voor het moderniseren van Drupal Frontend.
🔥 Een theme die enkel bestaat uit componenten
👩💻 Een Gulp-setup gefinetuned specifiek hiervoor
🌈 Een #frontend #Drupal platform voor #themers en #designers om samen te werken 👊🏾
Check check 👉🏻 https://www.compony.io/blog/what-compony
## Romanian
Află despre un mod nou și structurat de lucru pentru Front-end de ultimă oră în Drupal
🔥 O temă bazată exclusiv pe componente
👩💻 Gulp personalizat
🌈 O platformă colaborativă de #Drupal #frontend pentru #themers și #designers 👊🏾
Vizitați 👉🏻 https://www.compony.io/blog/what-compony
## Arab
يسرنا ان نقدم لكم قالب كومبوني كومبوني ثيم, نهج جديد و فريد من نوعه لاحضار اخر التقنيات لبرمجة واجهة المستخدم فرونت اند لدروبال.
قالب يعتمد كليا على العناصر كومبوننت 🔥
يستخدم ملفات gulp مصممة خصيصا 👩💻
منصة #واجهة_المستخدم #لدروبال لتسهيل التعاون بين المصممين ومبرمجي واجهة المستخدم. 🌈
تعرف عليه هنا:
👉🏻 https://www.compony.io/blog/what-compony
## Italian
Annunciamo un nuovo modo per aggiungere il meglio delle tecniche di front-end a Drupal:
🔥 Un tema interamente basato su component
👩💻 Un setup per Gulp Ottimizzato
🌈 Una piattaforma #Drupal di collaborazione per #themers e #designers
Guardate qua: https://www.compony.io/blog/what-compony
## Turkish
Drupal'a gelişmiş bir arayüz vermek için yeni bir yöntemdir.
🔥 Sadece bir birleşen temasi
👩💻 Adapte edilmiş Gulp
🌈 #Themers ve #tasarımcıların işbirliği yapmak için #arayüz #Drupal platformu 👊🏾
Linke tıkla: 👉🏻 https://www.compony.io/blog/what-componyhttps://gitlab.com/Compony/compony-roadmap/-/issues/92Get promoted to the frontpage of Drupal.org2019-11-17T13:04:31ZMathieu SpillebeenGet promoted to the frontpage of Drupal.orgWhen we launched Compony.io, we filed a [request to be promoted to the frontpage of Drupal.org](https://www.drupal.org/project/content/issues/3053078)
This is currently still under review and seems to be blocked on something unknown.
T...When we launched Compony.io, we filed a [request to be promoted to the frontpage of Drupal.org](https://www.drupal.org/project/content/issues/3053078)
This is currently still under review and seems to be blocked on something unknown.
The current plan would be to wait until we fixed our transparency and then push this forward.https://gitlab.com/Compony/compony-roadmap/-/issues/91Collaborating with Lullabot2019-11-18T15:29:17ZMathieu SpillebeenCollaborating with LullabotAs a part of #87 and inspired by #89:
I think it would be wise to see if we could get hosted on [the podcast of Lullabot](https://www.lullabot.com/podcasts/lullabot-podcast) to talk about what Compony is for the Drupal community.As a part of #87 and inspired by #89:
I think it would be wise to see if we could get hosted on [the podcast of Lullabot](https://www.lullabot.com/podcasts/lullabot-podcast) to talk about what Compony is for the Drupal community.https://gitlab.com/Compony/compony-roadmap/-/issues/90Write for Hackernoon.com2019-11-18T21:04:57ZMathieu SpillebeenWrite for Hackernoon.comAs a part of #87:
As proposed by @ragnarkurm: We could post [our blogposts](https://www.compony.com/blog) also to hackernoon!
This would mean that we need to become a contributing writer? I have no experience in this.
If we spread o...As a part of #87:
As proposed by @ragnarkurm: We could post [our blogposts](https://www.compony.com/blog) also to hackernoon!
This would mean that we need to become a contributing writer? I have no experience in this.
If we spread one article, it should be this one: "[What is Compony](https://www.compony.io/blog/what-compony)"https://gitlab.com/Compony/compony-roadmap/-/issues/89Collaborating with the Drupal newsletter2019-11-18T15:24:28ZMathieu SpillebeenCollaborating with the Drupal newsletterAs part of #87:
As proposed by @ragnarkurm: we could contact the Drupal newsletter to spread the word.
If we only spread one article, it should be this one: "[What is Compony](https://www.compony.io/blog/what-compony)"As part of #87:
As proposed by @ragnarkurm: we could contact the Drupal newsletter to spread the word.
If we only spread one article, it should be this one: "[What is Compony](https://www.compony.io/blog/what-compony)"https://gitlab.com/Compony/compony-roadmap/-/issues/88Open sourcing the presentation and workshop2019-11-17T12:43:36ZMathieu SpillebeenOpen sourcing the presentation and workshopAs part of #87
I was thinking about open sourcing a fork of [my slides of my presentation](https://slides.com/mathieuspillebeen/deck-6-7-11#/) and [slides of my workshop](https://slides.com/mathieuspillebeen/deck-6-10-12#/) If anyone w...As part of #87
I was thinking about open sourcing a fork of [my slides of my presentation](https://slides.com/mathieuspillebeen/deck-6-7-11#/) and [slides of my workshop](https://slides.com/mathieuspillebeen/deck-6-10-12#/) If anyone would be interested in this: please let me know here! :)https://gitlab.com/Compony/compony-roadmap/-/issues/87Brainstorming: Spreading the word about Compony2019-11-17T13:17:27ZMathieu SpillebeenBrainstorming: Spreading the word about ComponyI have spent a lot of effort in spreading the word about Compony.
On http://www.compony.io/social we are linking all of our social media that we are pushing. While all social attention is good for spreading the word, we also have been p...I have spent a lot of effort in spreading the word about Compony.
On http://www.compony.io/social we are linking all of our social media that we are pushing. While all social attention is good for spreading the word, we also have been pushing on many other fronts too.
This ticket is about how others can spread the word too for Compony.https://gitlab.com/Compony/compony-roadmap/-/issues/86Research and investigate licensing for both Compony and components2019-11-21T05:42:59ZMathieu SpillebeenResearch and investigate licensing for both Compony and componentsAs suggested by @lauriii:
We should have an open source license for the Theming skeleton, one for the Gulp layer and then also have instructions on how we have licence(s) on contributed components.
I am however completely unaware of li...As suggested by @lauriii:
We should have an open source license for the Theming skeleton, one for the Gulp layer and then also have instructions on how we have licence(s) on contributed components.
I am however completely unaware of licences and how they work and where they need to be put. So would love some guidance on this.https://gitlab.com/Compony/compony-roadmap/-/issues/85More transparency for the repositories2019-11-13T19:39:07ZMathieu SpillebeenMore transparency for the repositoriesAs suggested by @lauriii:
Open source projects usually have a link on top somewhere, linking to their Github and Gitlab repositories, we should have ours too.
Currently for us, it looks like this:![2019-11-13_16-48-22](/uploads/6d73f3d...As suggested by @lauriii:
Open source projects usually have a link on top somewhere, linking to their Github and Gitlab repositories, we should have ours too.
Currently for us, it looks like this:![2019-11-13_16-48-22](/uploads/6d73f3d5378a85ed18f10f57b9fa3294/2019-11-13_16-48-22.jpg)
Because both the theme and the tooling workflow are separate repositories, the suggestion would be to link to the Gitlab organisation: https://gitlab.com/users/Compony/starred
Adding this link on every page, would defeat the purpose of Collection and Component nodes, so therefor we would need to add it to the homepage only. Which would be possible as far as I can see, but would it then be adding more transparency, or be more confusing?https://gitlab.com/Compony/compony-roadmap/-/issues/83Change the menu for anonymous users2019-12-06T11:33:15ZMathieu SpillebeenChange the menu for anonymous usersAs suggested by @lauriii It would be beneficial to add some better menu-items to the anonymous menu.
Currently anonymous users don't know they can register easily, so
- The link to "login", should be changed to "login / register" (thi...As suggested by @lauriii It would be beneficial to add some better menu-items to the anonymous menu.
Currently anonymous users don't know they can register easily, so
- The link to "login", should be changed to "login / register" (this would show that creating an account is for everyone)
- Add the link "Create component" to the menu (but make it redirect to the register page?) (This would make the benefit of the platform more clear, as it's user-driven)https://gitlab.com/Compony/compony-roadmap/-/issues/82Blogpost: How to add compony components to an existing not-yet-compony theme2019-11-26T10:27:42ZTamás HajasBlogpost: How to add compony components to an existing not-yet-compony themeCurrent draft: https://docs.google.com/document/d/1YByRW8vu1zxWOf5eVsQxzvhGRfqU7RcYBQhdqtzJxN4/edit?usp=sharing
It would be great to describe the process of transforming an existing, not Compony-based theme to be capable to use some Co...Current draft: https://docs.google.com/document/d/1YByRW8vu1zxWOf5eVsQxzvhGRfqU7RcYBQhdqtzJxN4/edit?usp=sharing
It would be great to describe the process of transforming an existing, not Compony-based theme to be capable to use some Compony components.
So not a full rebuild on Compony, just enhancing with it.
I think it should be possible, hope, I'm right. :slight_smile:https://gitlab.com/Compony/compony-roadmap/-/issues/79Blogpost: integrating javascript frameworks2019-10-21T12:15:59ZMathieu SpillebeenBlogpost: integrating javascript frameworksOver the last days I have been experimenting with integrating libraries in to Compony setup and I learned so much that I would love to share it.
Current draft: https://docs.google.com/document/d/1JDVWfoRCbDLU1KjFQtPDD4YQT2tmBAEZt49-ao8U...Over the last days I have been experimenting with integrating libraries in to Compony setup and I learned so much that I would love to share it.
Current draft: https://docs.google.com/document/d/1JDVWfoRCbDLU1KjFQtPDD4YQT2tmBAEZt49-ao8Ur9g/edit#https://gitlab.com/Compony/compony-roadmap/-/issues/78Compony and Drupal's Layout Builder2019-09-20T20:24:29ZTamás HajasCompony and Drupal's Layout BuilderDoes it need anything special? Documentation or blog post…Does it need anything special? Documentation or blog post…