Current preview: https://eclipsefdn-asciidoc-wg.netlify.app/membership/

The current content is implemented as two short-codes. The content of the short-codes is HTML.
Instead of two short codes (that are only used in this location) the content could be written as simple AsciiDoc.

Current page: https://github.com/EclipseFdn/asciidoc.eclipse.org/blob/main/content/membership/_index.adoc

Short codes: https://github.com/EclipseFdn/asciidoc.eclipse.org/tree/main/layouts/shortcodes/membership

This is about the text displayed in the "hero" on the start page just below "AsciiDoc Working Group"

The current preview: https://eclipsefdn-asciidoc-wg.netlify.app/

Content is the "tagline" in the following file: https://github.com/EclipseFdn/asciidoc.eclipse.org/blob/main/content/_index.adoc

This can be taken from the charter.

The AsciiDoc WG now has it's own issue tracker located at https://gitlab.eclipse.org/eclipse-wg/asciidoc-wg/asciidoc-wg/-/issues. Since this website is meant to be a portal for all orders of business of the AsciiDoc WG, I think it should be possible to navigate to this issue tracker from the website.

What I'm not sure yet is where this link would go. It would make sense for it to be shown next to the link for the mailing list. However, that link to the mailing list isn't currently in the navigation hierarchy. I suppose we could put it below the mailing list link on the home page, but that could look too busy.

Instead, I think we need a new item in the navigation somewhere named "Participate". This heading is consistent with Eclipse's own working group home page. Under this heading could be "Mailing list", "Issue tracker", and perhaps other communication channels in the future. I would even be open to putting the Participate heading under a "More" entry in the navbar if it's taking up too much space.

For examples, see https://www.eclipse.org/org/workinggroups/ and https://edgenative.eclipse.org/

Describe the bug
Project tags generate an URL (ie. http://{domain}/technology_types/java/) that does not exists.
For example the following project

Has Java tag which points to https://{domain}technology_types/java/.

To Reproduce
Steps to reproduce the behavior:

1. Add new project with content

---
Title: Eclipse Austen
license: Eclipse Public License 2.0
is_incubated: true
website: https://projects.eclipse.org/proposals/eclipse-austen
github: https://myrepo.com
technology_types: [Java]
---
A description.

2. Build preview accorfing to instructions in README (currently: npm install && hugo server --destination=public)
3. Go to http://localhost:1313/projects/
4. Click on the tag
5. 404 screen

Expected behavior
At least not to fail.

Screenshots
n/a

Desktop (please complete the following information):

• OS: Linux 5.11.14-1-MANJARO
• Browser: Firefox
• Version: 88.0 64bits

Smartphone (please complete the following information):
n/a

Additional context
https://asciidoc-wg.eclipse.org/technology_types/java/ also returns a 404.

There are at the moment two mailing lists (see https://accounts.eclipse.org/mailing-list).

Visitors see this as a first and low entry barrier way to participate.

This page should list all members with their logo, name and a short description

The current preview is available here:

https://eclipsefdn-asciidoc-wg.netlify.app/membership/members/

Content goes here: https://github.com/EclipseFdn/asciidoc.eclipse.org/tree/main/content/membership/members

The current preview: https://eclipsefdn-asciidoc-wg.netlify.app/about/faq/

Page for the FAQ: https://github.com/EclipseFdn/asciidoc.eclipse.org/blob/main/content/about/faq/index.adoc

Content of the FAQ: https://github.com/EclipseFdn/asciidoc.eclipse.org/blob/main/data/en/faq.json

The current preview: https://eclipsefdn-asciidoc-wg.netlify.app/about/

The current content: https://github.com/EclipseFdn/asciidoc.eclipse.org/blob/main/content/about/_index.adoc

The description of this GitHub repo still links to the Netlify site.

Current status (Screenshot):

As the site is now live, this should change to https://asciidoc-wg.eclipse.org/

Also adding "AsciiDoc" as a tag would be nice.

If I'm a reader or reviewer of the website, and I see a problem, I need to know how to suggest or propose a fix. Therefore, there should be a link from the website to this repository.

One approach is to add an "Edit this Page" link to every page. That would make it easy to find the link from every page. The downside is that it makes the website look more collaborative than it is. It's meant to be more for relying information than collaborating on it.

So an alternative is to add a link on the home page that reads "Have you found an error on this site? Report it or propose a fix here".

A third approach is to add a link somewhere in the navbar. Perhaps About > Report website issue.

I'm leaning more towards option (b).

We noticed that the site is using the same banner image as eclipse.org, which may be confusing for some people. To help give AsciiDoc it's own look we have mocked up a couple of options for updated banner images. Let us know which (if either) you prefer and we can add the image files to the bug once you've provided your feedback.

Option A:

Option B:

I think we should replace (or at least move it lower on the page) the "Eclipse Foundation Events" as it can be a bit misleading.

Here's the current content:

As you can see "Eclipse Foundation Events" section takes a lot of space and even draw the attention away from the hero section.

I think we should instead use this section to describe the purpose/mission of the Working Group.
Here's an example:

https://science.eclipse.org/

The AsciiDoc Working Group will have two web sites:

• one to promote the language (asciidoc.org)
• one to introduce the working group and its members

To make a better distinction of the two, the website of the working group steering committee decided that the working group website should be named asciidoc-wg.eclipse.org

@eclipsewebmaster - could you please

• rename this repository from asciidoc.eclipse.org to asciidoc-wg.eclipse.org
• rename the preview from https://eclipsefdn-asciidoc.netlify.app/ to https://eclipsefdn-asciidoc-wg.netlify.app/ (and change

Thanks!

The start page should contain a link to the AsciiDoc Language project (https://projects.eclipse.org/projects/technology.asciidoc), perhaps next to the charter

Current preview: https://eclipsefdn-asciidoc-wg.netlify.app/

There is a list of all working groups here: https://www.eclipse.org/org/workinggroups/explore.php

All working groups with a homepage have a "Learn more" link, the AsciiDoc WG doesn't have that link yet.

This issue is about changing this.

A few Working Groups are using this design and I think it looks nice:

Current	Proposal

References:

• https://edgenative.eclipse.org/
• https://openmobility.eclipse.org/
• https://jakarta.ee/
• https://ecdtools.eclipse.org/

What do you think?

Describe the bug

I created PR71 to update the Registered Symbol to AsciiDoc and would like to preview my changes, but couldn't make it work.

With all 3 dependencies installed mentioned in README file - Node and NPM (14.7.1), Hugo, and Asciidoctor, when I run "hugo server --destination=public" command, I will get this error:

After I change

_build:
  render: never

to

_build:
  render: false

The error above would gone, but then I will get this error:

I am using Windows 10 - WSL2 - Ubuntu.
Not sure if I missed something or did something wrong?

The updated README should be updated to contain:

• the scope of the web site it supports (asciidoc-wg.eclipse.org vs. asciidoc.org)
• Ammend authors of the repo (as possible contacts for people to ask questions) - adding different roles to different people; for example Guillaume and Alex maintaining content, Chris creating the original template and infrastructure setup
• Adding AsciiDoc as a trademark to the list

The FAQ could be populated with answers to the following questions:

• “Why do we need a working group?”,
• “Why now?”, and
• “Why do we need a specification?”

Current link to the FAQ: https://asciidoc-wg.eclipse.org/about/faq/

Content: https://github.com/EclipseFdn/asciidoc-wg.eclipse.org/blob/main/data/en/faq.json

A list of approved meeting minutes (or a link to a folder that contains them)

The contributing document for the asciidoc-lang project contains a description of the mailing list(s): https://gitlab.eclipse.org/eclipse/asciidoc/asciidoc-lang/-/blob/main/CONTRIBUTING.adoc

These should be synced to https://asciidoc-wg.eclipse.org/about/

This will be done once all content is ready for the first publishing of this site.

All content that should be part of this is marked as Milestone "M1"

Pre-requisite: #3 (rename from asciidoc to asciidoc-wg)

I made the initial commit for this project. I did my best to include variations of the different things you can do with our template.

For example, I added a menu, sidebar menu, and dropdown menus in https://github.com/EclipseFdn/asciidoc.eclipse.org/blob/main/config.toml

The content of the main branch is available via https://eclipsefdn-asciidoc.netlify.app/. However, the plan would be to host the site on EF infra under asciidoc.eclipse.org.

GETTING STARTED:
https://github.com/EclipseFdn/asciidoc.eclipse.org#getting-started

Hugo Documentation:
https://gohugo.io/documentation

Theme Documentation:
https://eclipsefdn-hugo-solstice-theme.netlify.app/

Eclipse Foundation Hosted Services Privacy and Acceptable Usage Policy:
https://blogs.eclipse.org/post/christopher-guindon/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy

@rkratky @ahus1 Please let us know if you have any questions via this issue!

In issue #29 and PR #34 / 3c37500 we've replace the "featured content" (at that time mentioning the "Eclipse Foundation Events") with content hosted in the AsciiDoc WG Git repo describing the "purpose" of the AsciiDoc working group.

As pointed out by @chrisguindon, the Eclipse Marketing team maintains and updates the content delivered for the "featured content" widget on the site.
@shanda-eclipse let us know that we can send content to her via email: [email protected]

This is a follow-up issue to find out:

• what are the trade-offs of using the "featured story" mechanism delivering dynamic content vs. static content on the working group's start page?
• who is responsible/the driver for the content of the "featured story" - the working group or the Eclipse Marketing team?
• what are recommendations/best practices of the Eclipse Marketing team to have on a working group's start page?

Possible outcomes of this issue:

• stay with having the content in the git repository OR using the featured story mechanism with content maintained by the Eclipse Marketing team
• stay with the "purpose" content OR come up with different content that fits better to the start page

The site will have an overview of all Partner members and Committer members (#4).

To add names and faces to the steering group, there should be content on each appointed partner member seat and each elected community seat.

This continues the work started in #4.

We are using a "strong" color on the breadcrumbs and I find I think it's too colorful:

Current	Proposal

Is your feature request related to a problem? Please describe.
Projects right now display a "Website" button in the summary in single views.
I'd be nice to also link the code repo url when this is setup.

Describe the solution you'd like
Same format and style as "Website" button is good for now.
As nite-2-have, maby explore adding a git tree icon to make it git-provider agnostic.

Describe alternatives you've considered
n/a

Additional context
Related conversation: #64 (comment)

This will allow dependencies to be updated semi-automatically by an automatically created pull request by dependabot.

Describe the bug

After PR #70 the changes from the build are not visible on the production site yet (the meeting minutes of 2021-05-11 haven't been added to https://asciidoc-wg.eclipse.org/committees/).

@mbarbero - I see you committed some changes to the repo (see 1d76f84), are you working on this issue already?

Thanks,
Alexander

The project Eclipse Austen currently being setup/created. https://projects.eclipse.org/proposals/eclipse-austen

Once it is ready, it should be on the WG's project list: https://asciidoc-wg.eclipse.org/projects/

@abelsromero - could you please take on this task once Eclipse Austen should appear on the WG's site?

Content goes here: https://github.com/EclipseFdn/asciidoc-wg.eclipse.org/tree/main/content/projects
The Hugo setup would require a new folder austen as a sibling to the folder asciidoc-lang with similar content.

Thanks!

As @Mogztter has shown commitment to improve this site in several ways I asked him to join this repo as a committer. I'm happy to write that he agreed!

@eclipsewebmaster - could you please add permissions for @Mogztter to this repo? He should basically have the same permissions as Robert and me.
Thanks!

(Quote of the day: "To infinity and beyond!" / Buzz Lightyear)