1<!DOCTYPE html> 2<html lang="en"> 3 4<head> 5 <meta charset="UTF-8"> 6 <title>About dev.events</title> 7 <meta name="viewport" content="width=device-width, initial-scale=1"> 8 <meta http-equiv="x-ua-compatible" content="ie=edge"><link rel="stylesheet" href="/assets/app.36f521bd.css" />
9<script src="/assets/app.f5189268.js" defer></script>
9 10</head> 11 12<body class="container mx-auto px-10 mt-16"> 13 <nav> 14 <a href="/">â Back to dev.events</a> 15 </nav> 16 <main> 17 <h1 class="text-5xl my-10 font-extrabold tracking-tighter">Frequently Asked Questions (FAQ)</h1> 18 <ul class="list-decimal flex flex-col gap-4"> 19 <li> 20 <h2 class="font-bold">What is dev.events?<h2> 21 <p>We are the most-visited tech conference, meetup, hackathon, and masterclass listing with over 250K monthly 22 views. </p> 23 </li> 24 <li> 25 <h2 class="font-bold">Who's behind the project?<h2> 26 <p>The project is coded and maintained under loads of caffeine by DevEvents LLC team. 8 The Green, Dover, Delaware 19901, United States. Events are contributed by conference organizers, tech community, and volunteers.</p> 27 </li> 28 <li> 29 <h2 class="font-bold">Where do you source events from?</h2> 30 <p>We automatically monitor various sources, manually check conference websites, and rely on organizers and 31 contributors for event submissions. It's a good mix of automation (20%) and manual work (80%). We also automatically source meetups from <a class="text-black underline" href="/communities">4050 tech communities</a>. If your community is not on the list and you want your events to appear on our site automatically, submit your event. Once approved, future events will be added automatically. 32 </p> 33 </li> 34 <li> 35 <h2 class="font-bold">How to keep up-to-date with new events?</h2> 36 <p>Simply sort events by 'newest first' so that the latest events appear at 37 the top, and then visit our website from time to time. Alternatively, you can subscribe to <a 38 class="text-black underline" href="https://dev.events/rss.xml">the 39 RSS 40 feed</a>, which includes 100 recently added events. In the feed you can distinguish between events types and topics by checking the *category* 41 tag. You can also filter the feed by categories. For example, <a class="text-black underline" 42 href="https://dev.events/rss.xml?category=masterclass&category=hackathon&category=conference">this feed</a> 43 lists 44 all events except meetups. You can refine event filtering by using a service like <a class="text-black underline" rel="nofollow noopener noreferrer" href="https://siftrss.com/">Siftrss</a>. 45 </p> 46 </li> 47 <li> 48 <h2 class="font-bold">How to filter conferences by CFP?</h2> 49 <p>We're not storing CFP information because it's not always published, and there's no standard way to apply for conferences â it could be through Sessionize, a form, or email. Moreover, many good conferences don't even have an official CFP, but it's still worth applying. If you're only tracking conferences with CFPs, you are missing out.</p> 50 </li> 51 <li> 52 <h2 class="font-bold">How to add an event?</h2> 53 <p>You can submit an event by clicking the *new event* button 54 at the bottom right corner of the website. Our 55 team will review the event and approve it within three working days if it meets the eligibility criteria. 56 </p> 57 </li> 58 <li> 59 <h2 class="font-bold">What are the eligibility criteria?</h2> 60 <p>The event should focus on tech, software, or product development. The event date, location, and registration 61 link should be clearly visible on your website. It should also include some speakers so we can verify the event's eligibility, if necessary, by contacting them. 62 </p> 63 </li> 64 <li> 65 <h2 class="font-bold">How to automate event submission?</h2> 66 <p> 67 If your event has been listed on dev.events before, we'll monitor your website for updates, specifically looking for structured metadata using the standard <a class="text-black underline" href="https://jsonld.com/event/">JSON-LD markup</a>. When a new event is detected, our mod receives a notification. If deemed valid, the event is published. 68 </p> 69 </li> 70 <li> 71 <h2 class="font-bold">How to request modification to an event?</h2> 72 <p>If you want to change dates, remove an event, or add a discount code, simply email us at <a class="text-black underline" href="/cdn-cgi/l/email-protection#e9818c858586a98d8c9fc78c9f8c879d9a"><span class="__cf_email__" data-cfemail="ec8489808083ac88899ac2899a8982989f">[email protected]</span></a>.</p> 73 </li> 74 <li> 75 <h2 class="font-bold">How to get listed as 'best conference' on top of other events?</h2> 76 <p>If youâre hosting a top tech event â whether a conference or workshop â please reach out at <a class="text-black underline" href="/cdn-cgi/l/email-protection#8ae2efe6e6e5caeeeffca4effcefe4fef9"><span class="__cf_email__" data-cfemail="d5bdb0b9b9ba95b1b0a3fbb0a3b0bba1a6">[email protected]</span></a>
76 to discuss partnership options.</p> 77 </li> 78 <li> 79 <h2 class="font-bold">Clicking my event shows 'preview is not available'. ð</h2> 80 <p> 81 If clicking your event link shows a warning message 82 <b>preview is not available, visit the conference's website 83 directly,</b> ask your 84 developer/sysadmin to allow dev.events to embed your website in an 85 iframe. This is done by setting correct HTTP headers (or removing the ones that prohibit embedding). For troubleshooting, click asterisk (*) next to the warning message. If the issue is due to a timeout, your website is probably blocking our requests. In this case, allow requests with the 'x-dev-events' header. 86 </p> 87 </li> 88 <li> 89 <h2 class="font-bold">How can I suggest an idea / report a bug?</h2> 90 <p>Email us at <a class="text-black underline" href="/cdn-cgi/l/email-protection#ff979a939390bf9b9a89d19a899a918b8c"><span class="__cf_email__" data-cfemail="523a373e3e3d123637247c3724373c2621">[email protected]</span></a>. Thank you! ð 91 </p> 92 </li> 93 </ul> 94 </main>
vendor: 109 bytes, lines 94-95
94 95<script data-cfasync="false" src="/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js"></script>
95<script>(function(){function c(){var b=a.contentDocument||(a.contentWindow&&a.contentWindow.document);if(b){var d=b.createElement('script');d.innerHTML="window.__CF$cv$params={r:'a43ad5872984dfb0',t:'MTc5MDg1MTA2OA=='};var a=document.createElement('script');a.src='/cdn-cgi/challenge-platform/scripts/jsd/main.js';document.getElementsByTagName('head')[0].appendChild(a);";b.getElementsByTagName('head')[0].appendChild(d)}}if(document.body){var a=document.createElement('iframe');a.height=1;a.width=1;a.style.position='absolute';a.style.top=0;a.style.left=0;a.style.border='none';a.style.visibility='hidden';document.body.appendChild(a);if('loading'!==document.readyState)c();else if(window.addEventListener)document.addEventListener('DOMContentLoaded',c);else{var e=document.onreadystatechange||function(){};document.onreadystatechange=function(b){e(b);'loading'!==document.readyState&&(document.onreadystatechange=e,c())}}}})();</script>
95</body> 96 97</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.