Projects' descriptions follow these conventions. {icon paint-brush color=lightbluetext} **Colors** Colors allow to identify and organize elements. | **Type of project** | **Label hue** | **Image hue** | **Example** | ----- | ----- | ----- | ----- | Tags | orange | navel orange | #easy | Infrastructure | grey | gemstone | #servers | Projects with a part in production | blue | tropical blue | #tools | Projects in development, not yet released | blue | wide open sky | #databases | Shipped and released software | green | lustrous verdant | #source_templates_generator {icon eyedropper color=lightbluetext} **Green or blue?** * Blue are for Nasqueron projects * Green are for software released, used or reasonably usable outside Nasqueron. * Actually, some software will be pure internal DevOps scrips and will be linked so be grey, as t hey're infrastructure related. Another way to see the split is "software as services", blue, released software, green. {icon font color=lightbluetext} **Case** * Adjectives are in lowercase — e.g. #easy * Other names are in uppercase — e.g. #servers

Projects' descriptions follow these conventions. {icon paint-brush color=lightbluetext} **Colors** Colors allow to identify and organize elements. | **Type of project** | **Label hue** | **Image hue** | **Example** | ----- | ----- | ----- | ----- | Tags | orange | navel orange | #easy | Infrastructure | grey | gemstone | #servers | Groups, teams, etc. | violet | merlot | #Nasqueron_Docker_deployment_squad | Sprints | indigo | khaki | #ops-sprint-2015-12-01 | Projects with a part in production | blue | tropical blue | #tools | Projects in development, not yet released | blue | wide open sky | #databases | Shipped and released software | green | lustrous verdant | #source_templates_generator {icon eyedropper color=lightbluetext} **Green or blue?** * Blue are for Nasqueron projects * Green are for software released, used or reasonably usable outside Nasqueron. * Actually, some software will be pure internal DevOps scrips and will be linked so be grey, as t hey're infrastructure related. Another way to see the split is "software as services", blue, released software, green. {icon font color=lightbluetext} **Case** * Adjectives are in lowercase — e.g. #easy * Other names are in uppercase — e.g. #servers

Projects' descriptions follow these conventions. {icon paint-brush color=lightbluetext} **Colors** Colors allow to identify and organize elements. | **Type of project** | **Label hue** | **Image hue** | **Example** | ----- | ----- | ----- | ----- | Tags | orange | navel orange | #easy | Infrastructure | grey | gemstone | #servers | Groups, teams, etc. | violet | merlot | #Nasqueron_Docker_deployment_squad | Sprints | indigo | khaki | #ops-sprint-2015-12-01 | Projects with a part in production | blue | tropical blue | #tools | Projects in development, not yet released | blue | wide open sky | #databases | Shipped and released software | green | lustrous verdant | #source_templates_generator {icon eyedropper color=lightbluetext} **Green or blue?** * Blue are for Nasqueron projects * Green are for software released, used or reasonably usable outside Nasqueron. * Actually, some software will be pure internal DevOps scrips and will be linked so be grey, as t hey're infrastructure related. Another way to see the split is "software as services", blue, released software, green. {icon font color=lightbluetext} **Case** * Adjectives are in lowercase — e.g. #easy * Other names are in uppercase — e.g. #servers