• delete profile
• delete event

There should be a robots.txt generated by @nuxtjs/robots with the following content:

User-agent: *
Disallow: /robots.txt
Allow: /
Sitemap: https://maev.si/sitemap.xml

Where the sitemap value comes from the NUXT_ENV_STACK_DOMAIN variable.

• add event groups
• get rid of event_groupings
• allow to create an event similar to an existing one

Decide for a theme color, set it, then use realfavicongenerator.net to generate favicons.

Allow mails to and from *@maev.si.

The icon that appears as long as there is no color-scheme information available is displayed too large and thus moves other page content for a very short time on page load.

When adding or deleting pictures.

Otherwise one cannot delete their own account.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The event descriptions preview in the event list should not display markdown control characters.

Allow invitees to request the common +1 (or +n) additional guest(s).

Data displayed should be live.

• https://www.graphile.org/postgraphile/subscriptions/
• https://apollo.vuejs.org/guide/apollo/subscriptions.html

Hint: maevsi on Nuxt 3 uses urql as graphql client, not apollo anymore.

418

Add a page /privacy-policy that displays the following content: https://codimd.jonas-thelemann.de/s/HJcQBXUOD
I can take care of the translation.

Add a link to the footer (

@goatfryed, while you're at it, you might be interested in that too :)

Currently, after registration, one is logged in immediately.

The list of the currently stored invitation codes should show the corresponding events and codes should be removable individually.

Currently, the cookie is only invalidated, so that a following login cannot succeed.

• <meta property="og:title" content="<title>" />
• <meta property="og:type" content="<type>" />
• <meta property="og:url" content="<url>" />
• <meta property="og:image" content="<image-url>" />

Example: https://github.com/nuxt/nuxtjs.org/blob/master/pages/index.vue

Add brotli compression for the production server.

Reference:

• https://github.com/google/ngx_brotli/
• https://github.com/thetre97/gridsome-plugin-brotli

Do not store JWTs in local storage, use refresh tokens in httpOnly, sameSite cookies, in a manner that supports SSR (#29).

https://hasura.io/blog/best-practices-of-using-jwt-with-graphql/

Follow https://github.com/semantic-release/semantic-release for automatic releases.

Version 3 urql allows for more detailed cache modifications.

<meta name="description" content="page description">

https://www.npmjs.com/package/nuxt-i18n

Add translations:

• German

Evaluate https://gridsome.org/plugins/@gridsome/plugin-sitemap or maybe https://www.npmjs.com/package/@nuxtjs/sitemap when switching to Nuxt.

We don't generate static pages from APIs only, so Nuxt is the more complete framework.

After #29: https://github.com/anthonygore/vue-cli-plugin-critical

When logged in (only) the firefox console display "Uncaught (in promise) DOMException: Node.appendChild: Cannot add children to a Comment" on page load and "TypeError: t is undefined" when navigating.

It's unidirectional and seems more contemporary than stomp.

The current implementation that refreshes the JWT does not work. It wasn't expected that expired JWT cannot be used to refresh themselves. A proper refresh procedure is to be implemented that replaces the current – hacky – solution.

It would be nice to be able to get an iCal file - preferably via E-Mail, so it is easy to save the event to a personal calendar.

Especially respects users with slow internet connections.

Add a page /imprint that displays the following content: https://codimd.jonas-thelemann.de/s/ByX5SMAVP
If possible in English too (see other pages for i18n).

Add a link to the footer (

@goatfryed, you might be interested in that ;)

e.g. for path /123 too.

File upload, for example for profile pictures, should be stored as hash, to prevent duplicates. For this tusd hooks look like the appropriate solution.