#1147 Add revised content
Merged 3 months ago by darknao. Opened 4 months ago by t0xic0der.
t0xic0der/fedora-websites revising-documentation  into  main

file modified
+1 -1
@@ -14,5 +14,5 @@ 

  # This lists all the menu definitions of your component.

  nav:

  - modules/ROOT/nav.adoc

- - modules/runbook/nav.adoc

+ - modules/engg/nav.adoc

  - modules/dev/nav.adoc

empty or binary file added
file modified
+6 -3
@@ -1,3 +1,6 @@ 

- * xref:fedora-release.adoc[Fedora Beta/GA Release]

- * xref:translation-flow.adoc[Translation flow]

- * xref:fedora-annual-banner.adoc[Fedora Annual Survey Banner]

+ * xref:index.adoc[Websites & Apps Team]

+ * xref:objective.adoc[Council Objective]

+ * xref:tasks.adoc[Our tasks]

+ * xref:representatives.adoc[Representatives]

+ * xref:resources.adoc[Resources]

+ * xref:contact.adoc[Contact us] 

\ No newline at end of file

@@ -0,0 +1,27 @@ 

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = Contact us

+ 

+ Have questions or want to know more?

+ 

+ == Connect with us

+ 

+ Get in touch with our team in the following places:

+ 

+ === Asynchronous

+ ** link:{COMMS-DISCOURSE}[Fedora Discussion]

+ ** link:{COMMS-LISTSERV}[Mailing list]

+ 

+ === Synchronous

+ ** link:ircs://{COMMS-IRC-SERVER}:{COMMS-IRC-SERVER-PORT}/{COMMS-IRC}[IRC]

+ ** link:https://chat.fedoraproject.org/#/room/#websites:fedoraproject.org[Fedora Chat]

+ ** link:{COMMS-MATRIX}[Matrix]

+ 

+ == Membership

+ 

+ In order to become a member of the Fedora Website & Apps Team, the applicant must be register at link:++https://accounts.fedoraproject.org++[Fedora Accounts] and set up an account with the link:++https://pagure.io++[Pagure] VCS forge.

+ 

+ By becoming a Fedora Contributor, you accept these terms.

+ 

+ * link:++https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement++[Fedora Project Contributor Agrement (FPCA)]

+ * link:++https://docs.fedoraproject.org/en-US/project/code-of-conduct/++[Code of Conduct]

@@ -1,140 +1,73 @@ 

  include::ROOT:partial$attributes.adoc[]

  

  = Fedora Websites & Apps

- Rick Elrod; Ryan Lerch, Justin W. Flory

- :page-authors: {author}, {author_2}, {author_3}

- :toc:

  

  Welcome to the official documentation for the Fedora Websites & Apps Team.

  

- 

  [[about]]

  == About our team

  

- The Fedora Websites & Apps Team improves Fedora's image and creates user-friendly interfaces for users and contributors on the Internet.

- We are a community-led team compromised of contributors from around the world.

- The key goals of the team includes the following activities:

+ Our websites being our representation to the wider community of users and contributors over the internet, the team works on designing, developing and maintaining these user-friendly interfaces. The community-led team consists of voluntary contributors from around the world and are involved loosely in the following activities.

  

- * Consolidate key Fedora Project websites into a single uniform scheme.

- * Develop front-end and back-end components of Fedora's online web applications.

- * Maintain content that doesn't fall under any particular sub-project.

- * Generally, making the sites as fun and exciting as the project they represent!

+ === Consolidate key Fedora Project websites into a single uniform scheme

+ In terms of design (look/feel and UI/UX), engineering (tech stack and implementation) and operation (navigation and content), the team attempts to maintain the websites as consistently as possible.

  

- [[about-revamp]]

- === Websites & Apps Community Revamp Objective

+ === Develop frontend and backend components of Fedora's web applications

+ With the use of frontend tools (HTML, CSS, JavaScript and the related frameworks) and backend tools (Python, Ansible, JavaScript and the related frameworks), the team develops the web applications.

  

- The team was rebooted in 2021 as part of the https://fedoraproject.org/wiki/Objectives/Websites_%26_Apps_Community_Revamp[Websites & Apps Community Revamp Objective].

- We are a growing team of developers with a range of skills and interests.

- This Objective started for a few reasons:

+ === Making websites as fun and exciting as the project they represent

+ A book might not be judged by its cover but a project is likely to be judged by the website it is represented by. The team ensures that the websites precisely represent the project's details and offerings.

  

- * Better coordination to facilitate a growing interest in Fedora's web presence

- * Involving diverse contributors to take part in a knowledgeable group helping maintain the Fedora Project's websites and apps in line with modern web standards.

+ === Help maintain content that doesn't fall under any particular subproject

+ The team works on maintaining the content on certain online elements are very generic in nature, like documentation, community wiki, event banners which do not fit in a certain subteam or SIG.

+ 

+ [[about-revamp]]

+ == Websites & Apps Community Revamp Objective

  

+ The team was rebooted in 2021 as a part of the https://fedoraproject.org/wiki/Objectives/Websites_%26_Apps_Community_Revamp[Websites & Apps Community Revamp Objective]. With the onset of this council objective, the team has been growing ever since with developers, designers and project managers having a wide range of skills and interests. Please refer to [this] documentation to learn more about the council objective's purpose and functions.

  

  [[collaborations]]

  == Our collaborations

+ In order to work in a community with as many diverse projects and stakeholders as the Fedora Project, the team aims to communicate and collaborate regularly with different community members from various subprojects, SIGs and workgroups within Fedora. The activities on specific websites and applications are coordinated by the relevant points of contacts.

  

- In order to work in a community with as many diverse projects and stakeholders as the Fedora Project, our team aims to communicate regularly with different community members in Fedora.

- Work on specific websites is coordinated by the appropriate sub-projects and/or project lead(s).

- 

- Here is a list of our frequent collaborators:

- 

- [[collaborations-fedora]]

- === Fedora sub-projects

- 

- * https://fedoraproject.org/wiki/Design[*Design Team*]:

-   Create designs, wireframes, and other visual content to guide development efforts

- * *Infrastructure*:

-   Support on back-end technologies and hosting official Fedora Project infrastructure.

- * *Localization Team*:

-   Translates strings across Fedora websites and apps into different languages.

- * xref:mindshare::index.adoc[*Mindshare Committee*]:

-   W&A Team holds one seat on the Fedora Mindshare Committee.

- 

- [[collaborations-friends]]

- === Friends of Fedora

- 

- * xref:cpe::index.adoc[*Red Hat Community Platform Engineering* (CPE)]:

-   A Red Hat team dedicated to the Fedora and CentOS projects where they contribute to the infrastructure and release engineering.

- * https://www.redhat.com/en/blog/channel/red-hat-open-source-program-office[*Red Hat Open Source Program Office engineers*]:

-   A Red Hat team that supports various Open Source technology initiatives across the Red Hat technology ecosystem.

- 

+ Here is a list of our active collaborators:

  

- [[work]]

- == Our work

+ [[collaboration-subteams]]

+ === Our subteams

+ The team is further assisted with three subteams that are distinct in function but integrated in purpose.

  

- The W&A Team updates and maintains the code bases for Fedora's websites and web applications.

- We work on a variety of tasks suitable for both new and experienced contributors.

+ ==== Fedora Websites Revamp Stakeholder Team

+ The subteam consists of folks from the design team and various other subprojects, SIGs and workgroups where they come up with mockups for the offerings websites, review them and improve upon them continually.

  

- [[work-tasks]]

- === Example tasks

+ ==== Fedora Websites Engineering Team

+ The subteam looks into the technical side of things - helping with developing and maintaining the websites in the state that they are in for now, assisting with the issue tickets and onboarding/mentoring contributors.

  

- * Adding temporary content to websites

- * Coding design mockups provided by the Design Team

- * Updating server-side code

- * Improving language and accessibility support

- * Revamping websites to improve user experience

- * Writing documentation for contributors

+ ==== Fedora Websites and Apps Objective Co-leads Team

+ The subteam looks into the cohesion of the aforementioned two teams - introspecting the current state of the teams, ensure contributors feel rewarded and that the objective outcomes are met.

  

+ [[collaborations-subprojects]]

+ === Fedora sub-projects

  

- [[bug]]

- == Report a bug

- 

- Find a bug on one of our websites?

- See https://fedoraproject.org/wiki/How_to_fix_bugs_on_the_Fedora_Project_website[these instructions on fixing bugs].

- Otherwise please report them on our https://pagure.io/fedora-websites[Pagure repository].

- 

- 

- 

- [[contact]]

- == Contact us

- 

- Have questions or want to know more?

- Get in touch with our team in the following places:

- 

- * *Asynchronous*:

- ** link:{COMMS-DISCOURSE}[Fedora Discussion]

- ** link:{COMMS-LISTSERV}[Mailing list]

- * *Synchronous*:

- ** link:ircs://{COMMS-IRC-SERVER}:{COMMS-IRC-SERVER-PORT}/{COMMS-IRC}[IRC]

- ** link:{COMMS-MATRIX}[Matrix]

- ** link:{COMMS-TELEGRAM}[Telegram]

- 

- == Membership

- 

- In order to become a member of the Fedora Website & Apps Team, the applicant must be register at link:++https://accounts.fedoraproject.org++[Fedora Accounts] and set up an account with the link:++https://pagure.io++[Pagure] gitforge.

- 

- By becoming a Fedora Contributor, you accept these terms.

- 

- * link:++https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement++[Fedora Project Contributor Agrement (FPCA)]

- * link:++https://docs.fedoraproject.org/en-US/project/code-of-conduct/++[Code of Conduct]

+ ==== https://fedoraproject.org/wiki/Design[*Design Team*]

+ The subproject has been actively helping with creating mockups and wireframes, evaluating user interfaces and providing visual content.

  

- == Are You New to Web Development?

- We flag tickets that are suitable for new contributors and those whom are newer to html, css, js, and python. If you aren't sure where to start, or cannot find documentation that you are looking for, get in touch with one of our team members and they will help point you in the right direction.

+ ==== https://fedoraproject.org/wiki/Infrastructure[*Fedora Infrastructure*]

+ The subproject assists the development and maintenance efforts by providing support on backend technologies and hosting.

  

- One of the goals of our revamp is to offer mentorship to those who are new to the field, or just interested in advancing their skills. If you are interested in mentorship, get in touch with one of our admins and they will help connect you with someone for mentorship opportunities.

+ ==== https://fedoraproject.org/wiki/L10N[*Localization Team*]

+ The subproject supports with translating content strings across various Fedora Websites and Applications into different languages/dialects.

  

- == Are you an experienced Web Developer?

- We often have tickets that demand more advanced knowledge of the technologies in our stack, and as web development is such a fast moving field, we are always interested to work with developers that bring something new to the table. Do you see something that you would like to work on? Please get in touch with us.

+ ==== https://docs.fedoraproject.org/en-US/mindshare-committee/[*Mindshare Committee*]

+ There is a representative for the team in the Fedora Mindshare committee for outreach leadership and unifying/sharing working progress.

  

- == Fedora's Website Tech Stacks

- * Fedora Community Blog: Wordpress

- * Fedora Websites: Flask, Jinja, HTML, CSS3, JavaScript, Python 3

- * Fedora Docs: Asciidoc

+ ==== https://docs.fedoraproject.org/en-US/program_management/[Program Management Team]

+ The subproject helps plan, schedule, track and coordinate tasks that help achieve the outcomes of the council objective and of the team.

  

- == Resources

- The W&A Team is made up of people who work on all levels of the tech stack. We value perspectives and experience from all positions of the tech stack. Check out these resources for your own setup. We are always working to expand our instructional material and documentation.

+ [[collaborations-friends]]

+ === Friends of Fedora

  

- === Documentation

- * link:++https://fedoraproject.org/w/uploads/1/19/Websitesandappsrevamp_logicmodel.png++[Fedora Websites Revamp Logic Model]: An overview of the Websites Team revamp

- * link:++https://developer.fedoraproject.org/tech/languages/python/python-installation.html++[Fedora Developer Python]

- * link:++https://developer.fedoraproject.org/tech/languages/python/flask-installation.html++[Fedora Developer Flask]

- * For those interested in php and working with the link:++https://communityblog.fedoraproject.org++[Fedora Community Blog]

- * link:++https://fedoramagazine.org/howto-install-wordpress-fedora/++[Wordpress Local Setup Instructions]: This article will help you setup a local wordpress deployment on Fedora.

+ ==== https://docs.fedoraproject.org/en-US/cpe/[*Red Hat Community Platform Engineering team*]

+ A Red Hat team dedicated to the Fedora and CentOS projects where they contribute to the infrastructure and release engineering.

  

- == Code Repositories

- * link:++https://pagure.io/fedora-websites++[Fedora Websites]

- * link:++https://pagure.io/fedora-web/websites/++[Fedora Main Website]

- * link:++https://github.com/fedora-infra/fedbadges++[Fedora Badges]

- * link:++https://github.com/fedora-infra/noggin++[Fedora Account System(FAS)]

- * link:++https://pagure.io/fedora-docs/docs-fp-o++[Fedora Docs]

+ ==== https://www.redhat.com/en/blog/channel/red-hat-open-source-program-office[*Red Hat Open Source Program Office engineers*]

+ A Red Hat team that supports various Open Source technology initiatives across the Red Hat technology ecosystem.

@@ -0,0 +1,73 @@ 

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = Council Objective

+ 

+ We started off some months ago with a successful objective proposal to put the time and effort into revamping not just the websites and applications that we maintain, but the way the community around it is organized.

+ 

+ == People involved

+ 

+ === Co-leads

+ * https://fedoraproject.org/wiki/User:T0xic0der[Akashdeep Dhar]

+ * https://fedoraproject.org/wiki/User:Grahamwhiteuk[Graham White]

+ 

+ === Support

+ * https://fedoraproject.org/wiki/User:Jflory7[Justin W. Flory]

+ * https://fedoraproject.org/wiki/User:Riecatnor[Marie Nordin]

+ * https://fedoraproject.org/wiki/User:Siddharthvipul1[Vipul Siddharth]

+ 

+ === Other teams

+ * https://docs.fedoraproject.org/en-US/cpe/[Red Hat Community Platform Engineering]

+ * https://www.redhat.com/en/blog/channel/red-hat-open-source-program-office[Red Hat Open Source Program Office]

+ 

+ == Mission

+ To reboot the websites team to include webapps in the scope of work and set up the team so that they can grow capacity in the future to build new exciting apps to meet community needs.

+ 

+ === Logic Model

+ image::logic-model.png[]

+ 

+ == Vision

+ Fedora has an active, engaged team that takes care of our main websites and all of our various community webapps. New folks who show up with an interest in code contributions find this an easy place to jump in. Members of the team are empowered to do the work they’re interested in and are connected to the other parts of the project related to getting those things done.

+ 

+ == Outcomes

+ 1. The team is happy, excited, recognized, and rewarded.

+ 2. The team has experience and ability with updating legacy Fedora webapps and sites.

+ 3. The Fedora websites are reliably updated when new Fedora Linux releases come out.

+ 4. The team knows what they’re focused on, and that focus meets user needs.

+ 5. Information about Fedora Websites & Apps is accessible and easy to find.

+ 6. It’s easy to find tasks for every skill level and interest.

+ 7. Requests and PRs are handled promptly.

+ 8. Mentorship is available, both for interested new members and for all members needing to get things done in Fedora infrastructure.

+ 9. Websites team is participating in the Mindshare Committee.

+ 

+ === Outputs

+ 1. Badges! Team swag!

+ 2. At least one webapp (møte) is modernized, as well as one web site (spins/labs).

+ 3. A documented plan for updating websites on new Fedora Linux releases, with understood team roles and responsibilities.

+ 4. A selected list of apps and websites with service level expectations. The websites in use are the most maintained ones.

+ 5. A continuously curated list of issues and tasks, organized by skillset and interest.

+ 6. Updated Fedora Websites documentation that explains the inventory of websites and how to get involved.

+ 7. A documented process is in plce for making sure requests (both PRs and requests for work) are triaged in a timely manner.

+ 8. "Websites Apprentices" program in place, and connections with Fedora Infrastructure team established.

+ 9. Fedora Mindshare Committee has an active, engaged representative to represent Fedora's Websites & Apps community.

+ 

+ === Activities

+ 1. Create team badges https://badges.fedoraproject.org/badge/rock-the-web%21 Request team swag.

+ 2. Develop new version of møte. Update [spins website](https://spins.fedoraproject.org) to new framework. [Link to tasks]

The link here is not formatted correctly. Should be

Update https://spins.fedoraproject.org[spins website] to new framework

+ 3. Document new release procedures and roles. Document specific team member responsibilities for release days and other critical needs.

+ 4. Inventory the existing apps and websites and decide what can be done about each. Where possible, mark older versions of websites as "outdated" and redirect to proper place. Encourage users (via design, documentation, and communication) towards the newer, maintained tools.

+ 5. Add new modules to the Fedora Websites docs based on different apps. Gradually migrate old docs in GitHub to the Docs repository.

+ 6. Regular meetings for the team that include triaging the W&A repo. [Smaller task: update repo with new tags]

+ 7. Continuous review of incoming work; create reports showing response time and regularly reflect on those metrics.

+ 8. Define Website Apprentice & mentorship role.

+ 9. Create updated process for Web & Apps Team Rep to Mindshare and implement.

+ 

+ == Resources

+ 1. Badges team to create badges. FCAIC and Design team for team swag. #action riecat

+ 2. Developers working on møte. Infra team or CPE for updating where it runs. Rick to mentor in porting Spins website?

+ 3. Program management team to help with documented processes. (#action bcotton). Docs skills to update team docs.fp.o website (#action relrod+jwf).

+ 4. OSPO and CPE list of existing apps. _Someone_ to build a comprehensive map. Designers to work on best pratices for unified UX.

+ 5. Fedora Docs team for documentation operations ("doc ops"). Websites & Apps team to maintain the documentation content.

+ 6. The team and people interested in doing the triage work. Program Management team may help here too?

+ 7. As #6!

+ 8. Interested team members. Mentorship training provided by Council.

+ 9. Mindshare team to help onboarding. Someone to update docs in project docs.

@@ -0,0 +1,42 @@ 

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = Representatives

+ 

+ The Websites and Apps Team is currently looking for a representative to Mindshare. If you happen to be interested in being one, please reach out to our channels to express your interest and we can take the discussion further from there. The responsibilities of the representative involves representing the team to the Mindshare committee and collaborate with other groups/teams/SIGs that work with them. Being a conduit between the two teams, the representative is expected to invest a fair amount of time and have good communication skills.

+ 

+ == Representatives

+ 

+ === Current representative

+ * We are looking for one.

+ 

+ === Previous representatives

+ * Rick Elrod

+ 

+ == Responsibilities

+ 

+ Representatives are critical in keeping communication between the team and Mindshare flowing. As a Mindshare representative, you will be involved in the following activities:

+ 

+ - Participate in the fedora-mindshare IRC/Matrix channel's weekly meetups

+ - In the fedora-mindshare Pagure repo, review and comment on tickets

+ - Work closely with the representatives from the other outreach teams to ensure that the most effective decisions are made

+ - Give the Mindshare Committee valuable input

+ - Share best practises: one of Mindshare's objectives is to remove any hurdles or impediments to sharing best practises

+ - Ascertain that the team is represented, and bring any challenges or barriers they may encounter to Mindshare meetings

+ - Ascertain that the Fedora budget is managed efficiently across all locations

+ - Listen to the Fedora community's needs, problems, and hopes and transmit them to the Mindshare Committee

+ 

+ == Duration of service

+ The service will last for two Fedora release cycles, or a year. However, depending on the personal circumstances of those serving as Representatives, terms may be shorter or longer. In the odd case that the representative(s), Mindshare Committee, or the Websites and Apps Team choose to change representation, they must show appropriate justification. The Websites and Apps Team will then choose a new representative based on the SOP.

+ 

+ == Selection

+ This section outlines the process of nominating and selecting representatives. The selection procedure outlined below begins when a current representative, the Mindshare committee, or the Fedora Council requests a rotation of representatives.

+ 

+ === Nomination

+ Potential delegates will have a two-week period to nominate themselves. Nominees can be self-nominated or nominated with the approval of other members of the Websites and Apps Team. Nominees must be members of the said team, have a basic understanding of various Fedora sub-projects, and have enough time to complete the essential obligations.

+ 

+ If no nominees are found, the Websites and Apps Team will collaborate with the Mindshare Committee to extend the search message and request more time. If no nominees are discovered after that, the role will be rotated among current Websites and Apps Team members until a new representative is found.

+ 

+ == Teams you will be closely working with

+ - Fedora Mindshare

+ - Websites and Apps Team and Subteams

+ - Various other Outreach teams as required

@@ -0,0 +1,21 @@ 

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = Resources

+ 

+ The Websites & Apps Team is made up of people who collaborate on all levels of design, operations and technology. They value perspectives, opinions and experiences from a various points of views. Please check out these resources for your own local setup.

+ 

+ We are continually working to expand our established processes, instructional materials and documentation.

+ 

+ == Documentation

+ * link:++https://fedoraproject.org/w/uploads/1/19/Websitesandappsrevamp_logicmodel.png++[Fedora Websites Revamp Logic Model]

+ * link:++https://developer.fedoraproject.org/tech/languages/python/python-installation.html++[Python - Fedora Developer]

+ * link:++https://developer.fedoraproject.org/tech/languages/python/flask-installation.html++[Flask - Fedora Developer]

+ * For those interested in PHP and working with the link:++https://communityblog.fedoraproject.org++[Fedora Community Blog]

+ * link:++https://fedoramagazine.org/howto-install-wordpress-fedora/++[Wordpress Local Setup Instructions]

+ 

+ == Code Repositories

+ * link:++https://pagure.io/fedora-websites++[Fedora Websites]

+ * link:++https://pagure.io/fedora-web/websites/++[Fedora Main Website]

+ * link:++https://github.com/fedora-infra/fedbadges++[Fedora Badges]

+ * link:++https://github.com/fedora-infra/noggin++[Fedora Account System(FAS)]

+ * link:++https://pagure.io/fedora-docs/docs-fp-o++[Fedora Docs]

@@ -0,0 +1,53 @@ 

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = Our tasks

+ 

+ The team designs, develops and maintains the Fedora's websites and applications.

+ 

+ These involve a variety of tasks suitable for both newcomers and experienced contributors.

+ 

+ [[division]]

+ == Something for everyone

+ Web technologies, being a very widespread technological stack and an avid point of interest for those involved in marketing, product design, project management etc., the team is in constant need of community contributors who are willing to work on these.

+ 

+ === Are you a newcomer to web development?

+ It is highly recommended for newcomers to web development to join us in our periodic meetings and introduce themselves to start with. According to the level of experience, the team members would help curate issue tickets suitable for them and provide mentorship/guidance wherever necessary in technological stacks like HTML, CSS, JavaScript and Python. This documentation should also consist enough information to help them get started with contributing.

+ 

+ === Are you an experienced in web development?

+ The team often has an array of tickets that demand more advanced knowledge and experience in our technological stack and management operations, and they could always use all the help that we can get. They are always interested to work with developers that bring something new to the table and actively assist in maintaining the status quo of the team. The contributors are requested to participate in the periodic meetings and reach out to the team.

+ 

+ [[tasks]]

+ == Example tasks

+ 

+ === Adding temporary content to websites

+ Temporary elements such as beta release indicators on the Fedora Linux offering websites, and banners for surveys and events are to be placed periodically.

+ 

+ === Developing approved design mockups

+ After the design mockups have gone through a review process and ready for implementation, they need to be developed into a final interactive project.

+ 

+ === Participating in the periodic meetings

+ The team connects periodically on a meeting to discuss updates, blockers and plans on activities, either synchronously on call or asynchronously on chat.

+ 

+ === Updating server-side code

+ Websites and applications need to be hosted on a relevant environment (development. staging or deployment), depending on the phase and maturity of the project.

+ 

+ === Improving language and accessibility support

+ This involves working alongside the localization teams for translating the available content to various languages and provide accessibility options.

+ 

+ === Revamping websites to improve user experience

+ In order to keep up with the current internet standards, older websites need to be rebooted using newer design methodologies and tech stacks.

+ 

+ === Writing documentation for contributors

+ Establishing processes and ensuring reproducibility of the activities is better supported by documentation to guide contributors through them.

+ 

+ === Creating issue tickets and triaging them

+ To note the tasks involved in making the aforementioned activities happen and to prioritize them, the team uses certain issue trackers and task boards.

+ 

+ [[bug]]

+ == Report a bug

+ 

+ Did you find a bug on one of our websites?

+ 

+ Please see these https://fedoraproject.org/wiki/How_to_fix_bugs_on_the_Fedora_Project_website[instructions on fixing bugs].

+ 

+ Otherwise, please report them on our https://pagure.io/fedora-websites[repository].

@@ -6,7 +6,7 @@ 

  :comms-matrix: https://matrix.to/#/#fedora-websites:matrix.org

  :comms-telegram: https://t.me/joinchat/hWQIgi7L79k3Nzk5

  :comms-video: https://meet.jit.si/fedora-websites-apps-meeting

- :comms-video-name: Jisti Meet

+ :comms-video-name: Jitsi Meet

  :meeting-day: Tuesday

  :meeting-time: 15:00 - 16:00 UTC

  :year: 2021

@@ -1,3 +0,0 @@ 

- * xref:index.adoc[*Development*]

- ** xref:setup-containers.adoc[Set up your environment (using containers)]

- ** xref:setup.adoc[Set up your environment (old method)]

@@ -1,7 +0,0 @@ 

- = Developer documentation

- Websites & Apps Team; Justin W. Flory

- :page-authors: {author}, {author_2}

- 

- This section of the W&A Team documentation is focused for developers and on day-to-day development.

- The purpose of this documentation is to gather the various documentation sources on different websites and collect them here.

- This is like an index of Fedora's website documentation.

empty or binary file added
empty or binary file added
empty or binary file added
@@ -0,0 +1,14 @@ 

+ * xref:index.adoc[Engineering team]

+ ** xref:meetings.adoc[Meetings]

+ ** xref:websites.adoc[Per-project Tech Stack for Websites]

+ ** xref:applications.adoc[Per-project Tech Stack for Applications]

+ ** xref:fedora-annual-banner.adoc[How to add the Fedora Annual Survey Banner]

+ ** xref:old-websites-release.adoc[Websites Release SOP (Legacy)]

+ ** xref:new-fedora-release.adoc[Websites Release SOP (Modern)]

+ ** xref:setup-legacy.adoc[Set up your environment (Legacy)]

+ ** xref:setup-modern.adoc[Set up your environment (Modern)]

+ ** xref:newcontent.adoc[Creating New Content]

+ ** xref:newcontent-edition.adoc[New Edition]

+ ** xref:newcontent-site.adoc[New Site]

+ ** xref:translation-flow.adoc[Translation Flow]

+ ** xref:contact.adoc[Contact us] 

\ No newline at end of file

@@ -0,0 +1,129 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

+ = Per-project Tech Stack for Apps

+ 

+ This document elaborates upon the tech stacks that we use to develop and maintain the applications under our remit.

+ 

+ [[infographic]]

+ == Infographic

+ image:applications-A.png[]

+ image:applications-B.png[]

+ 

+ [[remit]]

+ == Our remit and tools

+ 

+ Following is a list of applications that we help develop and maintain.

+ 

+ '''

+ 

+ === Badges

+ * Hosted at https://badges.fedoraproject.org/

+ * Maintained at

+  - https://github.com/fedora-infra/fedbadges

+  - https://github.com/fedora-infra/tahrir

+  - https://github.com/fedora-infra/tahrir-api

+ 

+ ==== Requires

+ - Pyramid

+ - Tahrir API

+ - Requests

+ - SQLAlchemy

+ 

+ '''

+ 

+ === AskNot-NG

+ * Hosted at http://whatcanidoforfedora.org/

+ * Maintained at https://github.com/fedora-infra/asknot-ng

+ 

+ ==== Requires

+ - JavaScript

+ - Mako

+ - PyYAML

+ 

+ '''

+ 

+ === Elections

+ * Hosted at https://elections.fedoraproject.org/

+ * Maintained at https://github.com/fedora-infra/elections

+ 

+ ==== Requires

+ - Flask

+ - Fedora Messaging

+ - Python Fedora

+ - FASJSON

+ 

+ '''

+ 

+ === Nuancier

+ * Hosted at https://apps.fedoraproject.org/nuancier/

+ * Maintained at https://github.com/fedora-infra/nuancier

+ 

+ ==== Requires

+ - Flask

+ - JavaScript

+ - SQLAlchemy

+ - Python Fedora

+ 

+ '''

+ 

+ === Fedocal

+ * Hosted at https://calendar.fedoraproject.org/

+ * Maintained at https://github.com/fedora-infra/fedocal

+ 

+ ==== Requires

+ - Flask

+ - Fedora Messaging

+ - SQLAlchemy

+ - Python Fedora

+ 

+ '''

+ 

+ === Mote

+ * Hosted at https://meetbot.fedoraproject.org/

+ * Maintained at https://github.com/fedora-infra/mote

+ 

+ ==== Requires

+ - Flask

+ - Fedora Messaging

+ - Bootstrap 5

+ 

+ '''

+ 

+ === Commblog

+ * Hosted at https://communityblog.fedoraproject.org/

+ 

+ ==== Requires

+ - Wordpress

+ - PHP

+ 

+ '''

+ 

+ === Easyfix

+ * Hosted at https://fedoraproject.org/easyfix/

+ * Maintained at https://pagure.io/fedora-gather-easyfix

+ 

+ ==== Requires

+ - Jinja

+ - Urllib3

+ - Bugzilla

+ - MWClient

+ 

+ '''

+ 

+ === Magazine

+ * Hosted at https://fedoramagazine.org/

+ 

+ ==== Requires

+ - Wordpress

+ - PHP

+ 

+ '''

+ 

+ === Ambassador

+ * Hosted at https://fedoracommunity.org/

+ * Maintained at https://pagure.io/fedora-websites/blob/main/f/fedoracommunity.org

+ 

+ ==== Requires

+ - TBD

+ 

+ ''' 

\ No newline at end of file

@@ -0,0 +1,27 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

+ = Contact us

+ 

+ Have questions or want to know more?

+ 

+ == Connect with us

+ 

+ Get in touch with our team in the following places:

+ 

+ === Asynchronous

+ ** link:{COMMS-DISCOURSE}[Fedora Discussion]

+ ** link:{COMMS-LISTSERV}[Mailing list]

+ 

+ === Synchronous

+ ** link:ircs://{COMMS-IRC-SERVER}:{COMMS-IRC-SERVER-PORT}/{COMMS-IRC}[IRC]

+ ** link:https://chat.fedoraproject.org/#/room/#websites:fedoraproject.org[Fedora Chat]

+ ** link:{COMMS-MATRIX}[Matrix]

+ 

+ == Membership

+ 

+ In order to become a member of the Fedora Website & Apps Team, the applicant must be register at link:++https://accounts.fedoraproject.org++[Fedora Accounts] and set up an account with the link:++https://pagure.io++[Pagure] VCS forge.

+ 

+ By becoming a Fedora Contributor, you accept these terms.

+ 

+ * link:++https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement++[Fedora Project Contributor Agrement (FPCA)]

+ * link:++https://docs.fedoraproject.org/en-US/project/code-of-conduct/++[Code of Conduct]

docs/modules/engg/pages/fedora-annual-banner.adoc docs/modules/ROOT/pages/fedora-annual-banner.adoc
file renamed
+7 -4
@@ -1,11 +1,12 @@ 

- = How to add the Fedora Annual Survey Banner

+ include::engg:partial$attributes.adoc[]

  

+ = How to add the Fedora Annual Survey Banner

  

  == Add into start.fedoraproject.org

  

  * https://pagure.io/fedora-websites[fedora-websites] repo, https://start.fedoraproject.org[*Start Fedora Project*]:

  * data/templates/docs-header.html

- * add a div with the link information 

+ * add a div with the link information

  * `<div class="col-xs-12 col-sm-3 bluebox border">`

  * NOTE: use col-sm-3 instead of 4 to fit 4 elements

  * this will make it consistent with other on the page
@@ -14,14 +15,16 @@ 

  

  == How to remove the Fedora Annual Survey Banner

  

- == Removing From start.fedoraproject.org

+ === Removing From start.fedoraproject.org

  

  * In https://pagure.io/fedora-websites[fedora-websites] repo, go to https://start.fedoraproject.org[*Start Fedora Project*]:

  * edit data/templates/docs-header.html

  * remove div and containing elements for the survey

  * make sure to change the class to `<div class="col-xs-12 col-sm-4 bluebox border">`

  

- === Second method (NOTE MIGHT NOT WORK, CURRENTLY TESTING THIS WITH NEST BANNER)

+ === Second method

+ 

+ NOTE: MIGHT NOT WORK, CURRENTLY TESTING THIS WITH NEST BANNER

  

  * add a image to the data/content/index.html within the grey container

  * use the class `col-xs-12 top-margin` and set padding with `style="padding:10px 0"`

@@ -0,0 +1,20 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

+ = Fedora Websites & Apps Engineering Team

+ 

+ Welcome to the official documentation for the Fedora Websites & Apps Engineering Team.

+ 

+ == Points of contact

+ - https://fedoraproject.org/wiki/User:darknao[Francois Andrieu]

+ - https://fedoraproject.org/wiki/User:thunderbirdtr[Onuralp Sezer]

+ 

+ == Purpose

+ The team takes care maintenance and development of websites and applications while constantly keeping up with UI/UX reviews, mentoring contributors and organizing meetings.

+ 

+ == Function

+ 1. Multiple contributors from Design team, Server WG, Workstation WG, Kinoite subteam, Fedora Infra subteam, NeuroFedora SIG etc. have been participating in discussions over at the Fedora Websites Revamp 1 chat.

+ 2. Members from the design team have been continually instrumental in coming up with various mockups and improving upon them by getting reviews from within the team and the outer community (Discussion fp.o)

+ 3. Design team representative, Mairin Duffy had been mentoring a set of interns, Emma Kidney and Jess Chitas as well with her endeavours of creating mockups for the Fedora Linux websites.

+ 4. Planning and updates are now recorded in a GitLab subgroup - the creation of which was pursued by the members of this team, contributors from Fedora Infra and those from the Community Platform Engineering team.

+ 5. Meetings have been organized by Pawel Zelawski and participated by the members every after a certain period of time to catch up on the progress, perform stakeholder reviews and plan on the next tasks.

+ 6. With active representation in the events like Nest With Fedora and Fedora Linux Release Parties, the team had been reaching out to garner more feedback on the work done so far and acquire contributors for assistance.

@@ -0,0 +1,91 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

+ = Meetings

+ 

+ The team members collaborate periodically over synchronous and asynchronous meetings.

+ 

+ [[video-conference]]

+ == Video conference meetings

+ 

+ The Websites & Apps Engineering Team meets weekly as long as there are at least four active participants available. Should that not be the case - updates, plans and blockers are conveyed asynchronously in the Fedora Chat channel by the members.

+ 

+ [[conference-details]]

+ == Details

+ * Location - link:{COMMS-VIDEO}[*{COMMS-VIDEO-NAME} room*]

+ * Day - *{MEETING-DAY}s*

+ * Time - *{MEETING-TIME}*

+ 

+ [[agenda]]

+ == Agenda

+ A video conference meeting is a fleeting afair and hence, it is important to use every moment of the meeting wisely to discuss important topics.

+ 

+ === Flow of discussion

+ * [_5m_] Roll call / greetings / welcomes

+ * [_5m_] Any announcements to share with group?

+ * [_5m_] Follow-ups on past actions, if any

+ * [_10m_] Engineering updates

+ * [_10m_] Council Objective updates

+     - [_3m_] Mindshare updates

+     - [_3m_] Stakeholder updates

+     - [_4m_] General discussion

+ * [_remaining_] Discussion on plans and blockers

+ * Pick a chair for next time!

+ * [_5m before end_] Wrap-up and open floor discussion

+ 

+ === Example

+ The following is a Markdown-styled example agenda to extend from.

+ [source]

+ ----

+ ## FORMAT

+ 

+ ### Chair

+ - ADD YOUR NAME(S) HERE

+ 

+ ### Attendees

+ - ADD YOUR NAME(S) HERE

+ 

+ ### Check up

+ - How are you doing?

+ - How's the weather there?

+ 

+ ### Agenda

+ - ADD ITEMS HERE

+ ----

+ 

+ == How to chair team meetings?

+ Anyone can be a chair for the Websites and Apps Engineering Team, and we encourage everyone to try chairing our weekly team meetings at least once to get an experience. The team is supportive of newcomers and experienced folks alike who are trying to chair a meeting for the first time so one needs not worry about anything going wrong midway.

+ 

+ The chair should

+ 

+ * Be one of the first ones to join the meeting as they would be the ones coordinating with the attendees and carrying the meeting forward

+ * Have the agenda document open on a side to read topics from, add names to the agenda list and make notes/summaries/action-items discussed on

+ * Make sure that all the points from the slated agenda are discussed during the meeting and that the action items, if any, are accounted for

+ * Ensure that the attendees feel comfortable enough and get a fair amount of time to put their points forward and that there points are considered

+ * Act as an arbitrator to settle disputes, if there are any, among the attendees and try best to reach the middle ground by avoiding conflicts.

+ * Keep track of "raised hands" in order to ensure that every attendee in the meeting get their opportunity to speak in the order of "hands raised"

+ * Let the team know well in advance if they are not able to make it to the meeting that they volunteered to chair for to help get a replacement

+ * Attempt to prevent diversions in the meeting, be them caused by either themselves or the attendees and try to maximally utilize the meeting time

+ * Motivate communication in an accessible manner - so folks who are unwilling to use camera and/or microphone should be encouraged to use the chat

+ * Conduct an in-meeting poll, discussion, opinions, debate in an unbiased and fair manner to all the attendees to avoid any possible conflicts

+ * Feel comfortable to pass on their turn to someone else mid-meeting, should something important come up or if they cannot attend anymore

+ * Avoid a survivorship bias by passing on the updates shared and progresses made on the meeting to the wider community using relevant channels

+ * Make notes on the developments made in a meeting, summarize discussions, plans and action items, or find an assignee from the attendees to do it

+ * Ensure that they are attending the meeting from a noise-free and disturbance-free environment and are not distracted by any other work or social media

+ * Use an accessible and simple vocabulary to convey their statements for maximum participation, and wait enough after each point for attendees to reflect

+ 

+ [[guidelines]]

+ == Participation guidelines

+ * Please focus on listening, and on appreciating what others are trying to say, not only on what you are hearing.

+ * Wherever possible, please refrain from multitasking on email or social media and strive to remain fully present and tuned in to what others are saying and feeling.

+ * Please assume best intent in everyone's comments and strive to keep a constructive tone in your own.

+ * Please use simple, accessible language. In particular, please avoid jargon and acronyms, so that all may fully participate.

+ * When you speak, please make just one point and then let others speak. We want everyone to have an equal chance to speak. In a group of "n" people, speak no more than "1/nth" of the time.

+ * Please speak for yourself when making comments, using "I". Please don't speak for the assembled group by speaking as "we".

+ * Help us be mindful of the schedule and stay on time; we anticipate many people will have much they want to say, but please support us in moving the dialog forward.

+ 

+ [[self-aware]]

+ == Please be a self-aware participant!

+ * Please indicate you want to speak by raising your hand on video or with the button in Jitsi Meet; if you are not able to use or raise your hand, feel free to speak up but please try not to interrupt others.

+ * Please stay muted when you are not speaking.

+ * Please be mindful of background noise and join the call from a quiet location. Construction sites, windy gardens and non-quarantined internet cafes do not qualify as quiet locations.

+ * All parents and caregivers shall enjoy an irrevocable "background/foreground kid and dependent noise" exception at all times, but muting etiquette still applies.

docs/modules/engg/pages/new-fedora-release.adoc docs/modules/ROOT/pages/fedora-release.adoc
file renamed
+3 -3
@@ -1,6 +1,6 @@ 

- = Fedora Release

- Rick Elrod

- :page-authors: {author}

+ include::engg:partial$attributes.adoc[]

+ 

+ = Fedora Release (Modern)

  

  == Introduction

  

docs/modules/engg/pages/newcontent-edition.adoc docs/modules/runbook/pages/newcontent-edition.adoc
file renamed
+2 -2
@@ -1,6 +1,6 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

  = New Edition

- Rick Elrod; Justin W. Flory

- :page-authors: {author}, {author_2}

  :page-aliases: websites::newcontent-edition.adoc

  

  == Introduction

docs/modules/engg/pages/newcontent-site.adoc docs/modules/runbook/pages/newcontent-site.adoc
file renamed
+2 -2
@@ -1,6 +1,6 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

  = Creating A New Site

- Rick Elrod; Justin W. Flory

- :page-authors: {author}, {author_2}

  :page-aliases: websites::newcontent-site.adoc

  

  In rare cases, you might need to create an entirely new site, rather than an

docs/modules/engg/pages/newcontent.adoc docs/modules/runbook/pages/newcontent.adoc
file renamed
+2 -2
@@ -1,6 +1,6 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

  = Creating New Content

- Rick Elrod; Justin W. Flory

- :page-authors: {author}, {author_2}

  :page-aliases: websites::newcontent.adoc

  

  Content can be broken into several different components, although some of the

docs/modules/engg/pages/old-websites-release.adoc docs/modules/ROOT/pages/old--websites-release.adoc
file renamed
+6 -5
@@ -1,6 +1,8 @@ 

- == Webites Release SOP

+ include::engg:partial$attributes.adoc[]

  

- === Preparing the website for a new release cycle

+ = Websites Release (Legacy)

+ 

+ == Preparing the website for a new release cycle

  

  * Obsolete GPG key

  +
@@ -70,10 +72,9 @@ 

  `+http://localhost:5000/en/keys+` and

  `+http://localhost:5000/en/verify+`.

  +

- [NOTE]

- .Note

+ 

  ====

- NOTE: the tool will give you an outdated output, adapt it to the new

+ NOTE: The tool will give you an outdated output, adapt it to the new

  websites and bootstrap layout!

  ====

  

docs/modules/engg/pages/setup-legacy.adoc docs/modules/dev/pages/setup.adoc
file renamed
+3 -3
@@ -1,13 +1,13 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

  = Set up your environment (old way)

- Rick Elrod; Justin W. Flory

- :page-authors: {author}, {author_2}

  :page-aliases: websites::setup.adoc

  

  [NOTE]

  ====

  We now have documentation on using the `Dockerfile` which ships in the Fedora websites repository.

  We and trying that method before using the method outlined on this page.

- See xref:setup-containers.adoc[this tutorial].

+ See xref:setup-modern.adoc[this tutorial].

  ====

  

  == Preliminary Notes

docs/modules/engg/pages/setup-modern.adoc docs/modules/dev/pages/setup-containers.adoc
file renamed
+2 -2
@@ -1,6 +1,6 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

  = Set up your environment (using containers)

- Rick Elrod; Justin W. Flory

- :page-authors: {author}, {author_2}

  :page-aliases: websites::setup-docker.adoc

  

  

docs/modules/engg/pages/translation-flow.adoc docs/modules/ROOT/pages/translation-flow.adoc
file renamed
+2 -5
@@ -1,6 +1,6 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

  = Translation flow (for Fedora websites)

- Jan Kuparinen

- :page-authors: {author}

  

  == General

  
@@ -80,6 +80,3 @@ 

  ====

  Technically scripts can be run without using podman, but will then require proper setup in the local machine. The instructions given above are safer for generic users.

  ====

- 

- 

- 

@@ -0,0 +1,124 @@ 

+ include::engg:partial$attributes.adoc[]

+ 

+ = Per-project Tech Stack for Websites

+ 

+ This document elaborates upon the tech stacks that we use to develop and maintain the websites under our remit.

+ 

+ [[infographic]]

+ == Infographic

+ image:websites.png[]

+ 

+ [[remit]]

+ == Our remit

+ 

+ Following is a list of websites that we help develop and maintain.

+ 

+ [[get]]

+ === GetFedora

+ * Hosted at https://getfedora.org/

+ * Maintained at https://pagure.io/fedora-web/websites/

+ 

+ [[spins]]

+ === Fedora Spins

+ * Hosted at https://spins.fedoraproject.org/

+ * Maintained at https://pagure.io/fedora-websites/blob/main/f/spins.fedoraproject.org

+ 

+ [[labs]]

+ === Fedora Labs

+ * Hosted at https://labs.fedoraproject.org/

+ * Maintained at https://pagure.io/fedora-websites/blob/main/f/spins.fedoraproject.org

+ 

+ [[arm]]

+ === Fedora ARM

+ * Hosted at https://arm.fedoraproject.org/

+ * Maintained at https://pagure.io/fedora-websites/blob/main/f/arm.fedoraproject.org

+ 

+ [[alt]]

+ === Fedora Alternative Downloads

+ * Hosted at https://alt.fedoraproject.org/

+ * Maintained at https://pagure.io/fedora-websites/blob/main/f/alt.fedoraproject.org

+ 

+ [[community]]

+ === Fedora Community

+ * Hosted at https://fedoracommunity.org/

+ * Maintained at https://pagure.io/fedora-websites/blob/main/f/fedoracommunity.org/

+ 

+ [[start]]

+ === Fedora Start

+ * Hosted at https://start.fedoraproject.org/

+ * Maintained at https://pagure.io/fedora-websites/blob/main/f/start.fedoraproject.org

+ 

+ [[flock]]

+ === Flock to Fedora

+ * Hosted at https://flocktofedora.org/

+ * Maintained at https://pagure.io/fedora-websites/blob/main/f/flocktofedora.org

+ 

+ [[docs]]

+ === Fedora Docs

+ * Hosted at https://docs.fedoraproject.org/en-US/docs/

+ * Maintained at https://docs.fedoraproject.org/en-US/docs/

+ 

+ [[tools]]

+ == Our tools

+ 

+ Following is a list of tools that we make use of.

+ 

+ [[genshi]]

+ === Genshi

+ Genshi is a template engine for XML-based vocabularies written in Python. Genshi is used to easily insert generated output into XML-based languages, usually HTML, and reuse elements between documents. Genshi's syntax is based on Kid, but its architecture is different.

+ 

+ [[lxml]]

+ === LXML

+ The lxml XML toolkit is a Pythonic binding for the C libraries libxml2 and libxslt. It is unique in that it combines the speed and XML feature completeness of these libraries with the simplicity of a native Python API, mostly compatible but superior to the well-known ElementTree API.

+ 

+ [[jinja]]

+ === Jinja

+ Jinja is a web template engine for the Python programming language. It was created by Armin Ronacher and is licensed under a BSD License. Jinja is similar to the Django template engine but provides Python-like expressions while ensuring that the templates are evaluated in a sandbox.

+ 

+ [[frozen]]

+ === Frozen Flask

+ Frozen-Flask freezes a Flask application into a set of static files. The result can be hosted without any server-side software other than a traditional web server. Frozen-Flask is only about deployment: you can use Frozen-Flask to only have static HTML files on your server.

+ 

+ [[rss]]

+ === Python RSS

+ RSS (Rich Site Summary) is a format for delivering regularly changing web content. Many news-related sites, weblogs and other online publishers syndicate their content as an RSS Feed to whoever wants it. Feedparser and similar libraries are made use of while using Python 3.

+ 

+ [[flask]]

+ === Flask

+ Flask is a micro web framework written in Python. It is classified as a microframework because it does not require particular tools or libraries. It has no database abstraction layer, form validation, or any other components where pre-existing third-party libraries provide common functions.

+ 

+ [[scss]]

+ === SCSS/CSS

+ SCSS stands for the Sassy Cascading Style Sheets. The more advanced variant of CSS is SCSS. It was created by Chris Eppstein and Natalie Weizenbaum and designed by Hampton Catlin. It is also referred to as Sassy CSS due to its advanced features.

+ 

+ [[python]]

+ === Python 3

+ Python is a high-level, general-purpose programming language. Its design philosophy emphasizes code readability with the use of significant indentation. Its language constructs and object-oriented approach aim to help programmers write clear, logical code for small and large-scale projects.

+ 

+ [[antora]]

+ === Antora

+ Antora is a modular, multi-repository site generator designed for creating documentation sites from content composed in AsciiDoc® and processed with Asciidoctor. Antora’s toolchain and workflow help documentation and engineering teams manage documentation sites.

+ 

+ [[asciidoctor]]

+ === AsciiDoctor

+ Asciidoctor is a fast, open source, Ruby-based text processor for parsing AsciiDoc® into a document model and converting it to output formats such as HTML 5, DocBook 5, manual pages, PDF, EPUB 3, and other formats. Docs of the said format are fed into Antora for being parsed.

+ 

+ [[make]]

+ === Make

+ In software development, Make is a build automation tool that automatically builds executable programs and libraries from source code by reading files called Makefiles which specify how to derive the target program. It remains widely used amidst the more prevalent IDE build features.

+ 

+ [[podman]]

+ === Podman

+ Podman is an open-source project that is available on most Linux platforms and resides on GitHub. Podman is a daemonless container engine for developing, managing, and running Open Container Initiative (OCI) containers and container images on your Linux System.

+ 

+ [[ansible]]

+ === Ansible

+ Ansible is an open-source software provisioning, configuration management, and application-deployment tool enabling infrastructure as code. It runs on many Unix-like systems, and can configure both Unix-like systems as well as Microsoft Windows.

+ 

+ [[html]]

+ === HTML

+ The HyperText Markup Language or HTML is the standard markup language for documents designed to be displayed in a web browser. It can be assisted by technologies such as Cascading Style Sheets and scripting languages such as JavaScript for enhancing the design or adding interactivity.

+ 

+ [[javascript]]

+ === JavaScript

+ JavaScript, often abbreviated JS, is a programming language that is one of the core technologies of the World Wide Web, alongside HTML and CSS. Over 97% of websites use JavaScript on the client side for web page behavior, often incorporating third-party libraries.

empty or binary file added
@@ -0,0 +1,12 @@ 

+ :comms-discourse: https://discussion.fedoraproject.org/c/project/websites/66

+ :comms-irc: #fedora-websites

+ :comms-irc-server: irc.libera.chat

+ :comms-irc-server-port: 6697

+ :comms-listserv: https://lists.fedoraproject.org/archives/list/websites@lists.fedoraproject.org/

+ :comms-matrix: https://matrix.to/#/#fedora-websites:matrix.org

+ :comms-telegram: https://t.me/joinchat/hWQIgi7L79k3Nzk5

+ :comms-video: https://meet.jit.si/fedora-websites-apps-meeting

+ :comms-video-name: Jitsi Meet

+ :meeting-day: Tuesday

+ :meeting-time: 15:00 - 16:00 UTC

+ :year: 2021

@@ -1,5 +0,0 @@ 

- * xref:index.adoc[*Runbook*]

- ** xref:newcontent.adoc[Creating New Content]

- *** xref:newcontent-edition.adoc[New Edition]

- *** xref:newcontent-site.adoc[New Site]

- ** xref:meetings.adoc[Meetings]

@@ -1,16 +0,0 @@ 

- = Websites & Apps Runbook

- Websites & Apps Team; Justin W. Flory

- :page-authors: {author}, {author_2}

- 

- This Runbook documents information about the Fedora Website and Apps team and our core operations.

- It is a living collection of documents that explain the governance and organization of our team.

- The Runbook is a reference for current and future members of the community to learn about the inner-workings of what we do.

- 

- [[who]]

- == Who is the Runbook for?

- 

- The Runbook is a resource for anyone who wishes to participate in Fedora's Websites & Apps community.

- Anyone is welcome to review the Runbook and make suggestions.

- 

- The Runbook is officially maintained by Websites & Apps Team leads.

- However, all members of the community are welcome and encouraged to keep their processes or areas of knowledge regularly updated.

@@ -1,35 +0,0 @@ 

- include::ROOT:partial$attributes.adoc[]

- 

- = Meetings

- Justin W. Flory

- :page-authors: {author}

- 

- The Websites & Apps Team meets weekly:

- 

- * Location:

-   link:{COMMS-VIDEO}[*{COMMS-VIDEO-NAME} room*]

- * Day:

-   *{MEETING-DAY}s*

- * Time:

-   *{MEETING-TIME}*

- 

- 

- [[activities]]

- == Activities

- 

- Our weekly meeting includes these topics:

- 

- * Review tickets and pull requests

- * Discuss on team direction

- * Check in with each other

- * Plan activities

- 

- Feel free to attend a meeting and ask any questions you have.

- If you want to flag a topic for discussion or to be addressed by the group, message a team lead in advance so we can plan a slot in our agenda.

- 

- 

- [[resources]]

- == Resources

- 

- Links, notes, and shared content for our meetings.

- To be updated soon.

file modified
+1 -1
@@ -17,5 +17,5 @@ 

    destinations:

    - provider: archive

  runtime:

-   pull: true

+   fetch: true

    cache_dir: ./cache

Signed-off-by: Akashdeep Dhar akashdeep.dhar@gmail.com

Feel free to check it out though ;P

EDIT - The PR is no longer WIP and is ready to be reviewed/merged.

1 new commit added

  • Remove redundant table of contents
4 months ago

1 new commit added

  • Complete the list of applications
4 months ago

I've merged this PR on staging, which is now available here: https://docs.stg.fedoraproject.org/en-US/websites/

As discussed in the meeting yesterday, we would merge this to prod once the PR has lived a week on the staging with no suggestions made to it.

1 new commit added

  • Add docs - Chairing meetings and Mindshare rep
4 months ago

The link here is not formatted correctly. Should be

Update https://spins.fedoraproject.org[spins website] to new framework

and everything else looks good to me.
Will merge it later tonight.

Metadata Update from @darknao:
- Request assigned

3 months ago

Pull-Request has been merged by darknao

3 months ago
Metadata
Changes Summary 36
+1 -1
file changed
docs/antora.yml
+0
file added
docs/modules/ROOT/assets/images/logic-model.png
+6 -3
file changed
docs/modules/ROOT/nav.adoc
+27
file added
docs/modules/ROOT/pages/contact.adoc
+42 -109
file changed
docs/modules/ROOT/pages/index.adoc
+73
file added
docs/modules/ROOT/pages/objective.adoc
+42
file added
docs/modules/ROOT/pages/representatives.adoc
+21
file added
docs/modules/ROOT/pages/resources.adoc
+53
file added
docs/modules/ROOT/pages/tasks.adoc
+1 -1
file changed
docs/modules/ROOT/partials/attributes.adoc
-3
file removed
docs/modules/dev/nav.adoc
-7
file removed
docs/modules/dev/pages/index.adoc
+0
file added
docs/modules/engg/assets/images/applications-A.png
+0
file added
docs/modules/engg/assets/images/applications-B.png
+0
file added
docs/modules/engg/assets/images/websites.png
+14
file added
docs/modules/engg/nav.adoc
+129
file added
docs/modules/engg/pages/applications.adoc
+27
file added
docs/modules/engg/pages/contact.adoc
+7 -4
file renamed
docs/modules/ROOT/pages/fedora-annual-banner.adoc
docs/modules/engg/pages/fedora-annual-banner.adoc
+20
file added
docs/modules/engg/pages/index.adoc
+91
file added
docs/modules/engg/pages/meetings.adoc
+3 -3
file renamed
docs/modules/ROOT/pages/fedora-release.adoc
docs/modules/engg/pages/new-fedora-release.adoc
+2 -2
file renamed
docs/modules/runbook/pages/newcontent-edition.adoc
docs/modules/engg/pages/newcontent-edition.adoc
+2 -2
file renamed
docs/modules/runbook/pages/newcontent-site.adoc
docs/modules/engg/pages/newcontent-site.adoc
+2 -2
file renamed
docs/modules/runbook/pages/newcontent.adoc
docs/modules/engg/pages/newcontent.adoc
+6 -5
file renamed
docs/modules/ROOT/pages/old--websites-release.adoc
docs/modules/engg/pages/old-websites-release.adoc
+3 -3
file renamed
docs/modules/dev/pages/setup.adoc
docs/modules/engg/pages/setup-legacy.adoc
+2 -2
file renamed
docs/modules/dev/pages/setup-containers.adoc
docs/modules/engg/pages/setup-modern.adoc
+2 -5
file renamed
docs/modules/ROOT/pages/translation-flow.adoc
docs/modules/engg/pages/translation-flow.adoc
+124
file added
docs/modules/engg/pages/websites.adoc
+0
file added
docs/modules/engg/pages/websites.png
+12
file added
docs/modules/engg/partials/attributes.adoc
-5
file removed
docs/modules/runbook/nav.adoc
-16
file removed
docs/modules/runbook/pages/index.adoc
-35
file removed
docs/modules/runbook/pages/meetings.adoc
+1 -1
file changed
site.yml