#angular 8 notes angular 8 questions asked in companies | Explore Tumblr posts and blogs

juniperhayes123 · 6 months ago

Text

How to Get Creative and Effective Logo Design Ideas: A Comprehensive Guide

Introduction

1. Understand Your Brand Identity

Before diving into the design process, it’s crucial to have a clear understanding of your brand. What message do you want your logo to convey? What emotions should it evoke? A logo isn’t just an image; it’s a symbol that reflects your company’s values, mission, and target audience.

Key Questions to Ask:

What is the core mission of my business?

Who is my target audience?

What tone or personality does my brand have? (e.g., professional, fun, innovative)

What message do I want to convey through my logo?

2. Research Your Industry

Looking at other logos in your industry can provide insight into design trends, colors, and styles that are effective in your niche. However, the goal isn’t to copy others but to understand what works and how you can differentiate yourself.

How to Research:

Explore competitors’ logos and note what you like and dislike

Look at successful brands within your industry and analyze their logo design choices

Pay attention to color schemes, typography, and logo shapes

3. Brainstorm Ideas and Concepts

Start the ideation process by brainstorming key elements of your brand that could translate into visual symbols. Think about objects, animals, or abstract shapes that align with your brand’s identity. Create a list of potential ideas and images that could represent your business.

Brainstorming Techniques:

Mind Mapping: Create a mind map around your business’s core values and expand into related imagery

Word Association: Write down keywords that describe your brand, and then think about images or symbols related to those words

Mood Boards: Gather images, colors, and fonts that inspire you to create a visual representation of your brand’s personality

4. Consider Simplicity and Scalability

When designing a logo, keep it simple. Overly complex logos can be difficult to reproduce, especially at smaller sizes or in different formats. A simple design ensures that your logo will look good in all applications, from business cards to billboards.

Key Tips for Simplicity:

Use minimalistic shapes and clear lines

Limit the number of colors to avoid visual clutter

Ensure the logo is easily recognizable at any size

5. Experiment with Shapes and Colors

Shapes and colors play a significant role in how a logo is perceived. Different shapes can evoke specific emotions, while colors can influence the mood of your audience. For example, circular logos can symbolize unity and completeness, while angular shapes can convey strength and stability.

Color Psychology:

Blue: Trustworthy, professional, calming

Red: Bold, energetic, passionate

Green: Growth, nature, freshness

Yellow: Optimistic, friendly, creative

Shape Significance:

Circles: Unity, community, wholeness

Squares: Stability, professionalism, reliability

Triangles: Innovation, strength, movement

6. Look for Inspiration Beyond Logos

Sometimes the best logo ideas come from sources outside the world of design. Explore different industries, nature, architecture, or even fine art for fresh perspectives. Inspiration can strike from the most unexpected places.

Sources of Inspiration:

Nature: Flowers, trees, mountains, or animals can inspire organic and simple designs

Art & Architecture: Look at geometric patterns, sculptures, or historical architecture for unique shapes and ideas

Typography: Explore creative fonts and lettering styles to see how text can form part of the design

7. Test Your Ideas with Sketches

Once you have a few concepts in mind, start sketching. Even if you’re not a professional designer, rough sketches can help bring your ideas to life and refine them before turning them into a digital version. This step allows you to play with different variations and placements.

Sketching Tips:

Start with basic shapes and build on them

Try several variations of the same concept

Don’t focus on perfection at this stage — sketch freely and creatively

8. Use Logo Design Tools and Inspiration Websites

There are several online tools and platforms that can help you bring your logo ideas to life, whether you’re a beginner or an experienced designer. Websites like Canva, Looka, and Adobe Spark offer easy-to-use logo design tools and inspiration galleries.

Popular Logo Design Platforms:

Canva: Simple design tools for beginners, with templates and ideas

Looka: AI-powered logo generator for quick inspiration

Hatchful by Shopify: Free tool that offers design templates based on your industry

9. Get Feedback

Once you have a few logo options, seek feedback from friends, family, or colleagues. Getting external perspectives will help you understand how others perceive your logo. If possible, gather input from people who represent your target audience to ensure the design resonates with them.

How to Gather Feedback:

Conduct informal surveys or focus groups

Ask for specific feedback (e.g., does the logo feel modern? Does it communicate trustworthiness?)

Take note of any recurring comments or suggestions

10. Refine and Finalize Your Design

After gathering feedback, refine your logo by making necessary adjustments to color, typography, or proportions. A professional logo should be versatile, so ensure it works in black and white as well as color, and looks great in various sizes.

Refining Tips:

Test the logo in different formats (e.g., digital, print)

Make sure it looks good on both light and dark backgrounds

Ensure it’s scalable for various applications (business cards, websites, billboards)

Conclusion:

Generating creative logo design ideas involves a balance of understanding your brand, researching industry trends, brainstorming unique concepts, and experimenting with shapes and colors. By combining these strategies, you can craft a logo that not only represents your business effectively but also stands out in a crowded market. Remember, a logo is more than just an image — it’s a visual symbol of your brand’s story and values, so take the time to get it right.

#logo design #branding #graphic design #creative logo #editorial design #digital illustration #finance #ecommerce

0 notes

madhuvemula · 2 years ago

Text

Innovations Ahead: What the Future Holds for Full Stack Developers

Certainly! I’m excited to start the full-stack development journey with you. My expertise in this field has significantly grown over time. Selenium has become universally recognized and extensively utilized across various industries. Take your Full-Stack Developer career to the next level by enrolling in a leading institution in Chennai, like ACTE Technologies.

The Future Of Full-Stack Development Presents Optimistic Trends With Continuous Evolution. Here Are Key Points Indicating A Positive Trajectory:

1. Growing Demand: The demand for proficient full-stack developers remains robust, with companies actively seeking professionals adept at both front-end and back-end development, streamlining the overall development process.

2. Technological Versatility: Full-stack developers are expected to showcase proficiency in diverse technologies, encompassing front-end frameworks (e.g., React, Angular), back-end languages (e.g., Node.js, Python, Java), databases, and more. This adaptability proves valuable for addressing varied project requirements.

3. Agile Development Adoption: The Agile development methodology, emphasizing flexibility and collaboration, aligns seamlessly with the versatile skill set of full-stack developers. The widespread adoption of Agile practices by organizations further fuels the demand for full-stack development expertise.

4. Tech Stacks and Frameworks: Full-stack developers routinely engage with a spectrum of tech stacks and frameworks. Staying abreast of the latest technologies and frameworks empowers them to select optimal tools for specific projects.

5. Remote Work Opportunities: The accelerating trend of remote work aligns well with full-stack developers’ capabilities in handling both front-end and back-end tasks. This positions them favorably for collaboration in distributed teams, offering opportunities for remote work across diverse geographical locations.

6. Emergence of Full-Stack Frameworks: The rise of full-stack frameworks, such as MEAN (MongoDB, Express.js, Angular, Node.js) and MERN (MongoDB, Express.js, React, Node.js), streamlines development processes. These frameworks enhance the efficiency of full-stack developers, allowing them to work more effectively.

7. User Experience Focus: Full-stack developers play a pivotal role in elevating user experience by contributing to both client and server sides. As the emphasis on user experience continues to grow, the skills of full-stack developers remain in high demand.

8. Commitment to Continuous Learning: Given the dynamic nature of technology, continuous learning remains paramount for successful full-stack developers. The commitment to acquiring new tools and methodologies is expected to stay relevant in this evolving landscape.

It’s crucial to note that the technology field evolves, and trends may shift. Aspiring full-stack developers are advised to stay updated on industry developments, continuously enhance their skills, and seek the latest information as market conditions may have evolve.

Certainly! If you’re considering enrolling in a Full-Stack Developer course in Chennai, I highly recommend exploring esteemed institutions like ACTE Technologies. They offer comprehensive certification programs and job placement opportunities, guided by experienced instructors to enhance your learning journey. These resources are available both online and in person. Opting for a gradual, step-by-step course enrollment can prove to be a wise decision if it aligns with your interests.

I believe this adequately addresses your inquiry. For any further questions or clarification, feel free to ask in the comments section.

If you’ve found this information valuable, I encourage you to follow me on this platform and give it an upvote to foster more discussions and insights about Full-Stack Development. Your time and engagement are genuinely appreciated, and I wish you a wonderful day ahead.

0 notes

eklavyaonline · 5 years ago

Text

angular 8 interview questions

angular 8 notes, angular 8 questions asked in companies, angular 8 questions asked in interview, angular 8 questions asked in mnc, angular 8 questions for interview, angular 8 tutorials, complete notes on angular 8, complete tutorials on angular 8, faq for angular 8, faq on angular 8, interview questions on angular 8, latest interview questions on angular 8, most asked angular 8 interview questions, notes on angular 8, rapid fire on angular 8, rapid fire questions on angular 8, top interview questions on angular 8, tutorials on angular 8, updated interview questions answers on angular 8, angular 8 interview questions

#angular 8 notes angular 8 questions asked in companies

0 notes

skepticalcatfrog · 6 years ago

Text

Shattered Crown Chapter 8

First Chapter Previous Chapter Next Chapter Masterpost

Summary: After disaster strikes in Prince Roman's kingdom, he must go on a quest in order to take back the crown that is rightfully his. He will travel with three companions on an epic adventure, gaining many friends and enemies along the way. Those three companions are an intelligent inventor with a mysterious past, a cheerful wizard with a dark secret, and.. the assassin who was sent to kill him two years prior.

Pairings: Logicality, (Eventual) Prinxiety

Word count: 3,282

Author's Notes: We've got some more developments in this chapter! I actually really like this one, I think it's pretty good.

The next morning, when Patton and Logan got back to the room that the group had been staying in, Roman and Virgil were both awake. They had gone through a momentary panic, because of course they hadn't expected Logan to be gone. But it didn't last long, since they knew he was a smart guy.

So when Logan and Patton got back, and they were together, it was easy for Roman and Virgil to piece together what had happened. Still, they listened to the story. Both Patton and Logan decided to leave out the part about revealing their pasts to one another.

"So, you guys are a thing now?" Virgil asked, gesturing between the two of them.

"Yeah… I hope so, at least." Patton told him, glancing at Logan.

"Yes, we are." The inventor nodded.

"Guess that means we're now the third and fourth wheels, huh?" Roman laughed, nudging Virgil gently. "Unless we somehow manage to get boyfriends on this weird trip."

"Yeah, guess so…" Virgil didn't look at Roman, a faint blush creeping onto his face. Okay, fine. Maybe Virgil did have a huge crush on Roman. But why did he have to be such a clueless moron all the time? It was hard enough to have a crush on a prince, let alone one who didn't know he existed beyond being stuck with him.

Little did Virgil know, Roman was very aware of his existence. In fact, he also had a crush. But he still thought the assassin hated him. Which was unfortunate.

"Well… We've got nothing else to do here. Should we just leave?" Patton asked.

"Probably." Logan shrugged. "Time efficiency is everything, we wouldn't want to waste our time somewhere we don't have to be."

The others agreed, and they left their room. They went out to the street, making sure to stop and say goodbye to Remy and Emile before they left the kingdom.

"And now, to Aurum!" Roman called out triumphantly as they walked out of the gate. Virgil laughed, smiling at him. Logan and Patton exchanged knowing glances.

About an hour later, it started snowing. It kept going for a while, and soon enough there was a thin layer of snow on the ground. Roman noticed Virgil shivering a little, and gave him his cloak without another word. Virgil accepted it, just holding it in his hand for a moment, glancing at Roman in disbelief.

"What?" Roman blushed a little, seeing Virgil looking at him. "You looked cold, I'm letting you borrow it."

"...Thanks." Virgil put the cloak on, wrapping it around him like a blanket and pulling up the hood. Roman smiled faintly. Logan and Patton were screaming internally. They knew that Roman and Virgil liked each other, and it was kind of frustrating watching them be so clueless.

They walked for hours more, until they were all super tired. It wasn't dark out yet, but they were tired, and their feet hurt.

"Should we take a break?" Patton suggested.

"And maybe make a fire for warmth." Logan nodded. "I can use my glasses, and we can find some firewood somewhere."

"Yeah, that's…" Virgil was interrupted by a yawn. "That's a good idea."

"Okay then. Who's going to collect firewood?" Roman asked.

"I will." Patton volunteered. He then turned to Roman. "And I want you to come with me."

"Sure." The prince nodded. "I don't know if there's a forest super close by, but I thought I saw one a little while ago."

"Great!" Patton turned back to Logan, kissing his cheek. "We'll be back soon!"

"And we'll be waiting for you here." Logan told him. And with that, Patton and Roman left to find some firewood.

"Patton, can I ask you a question?" Roman asked randomly once they were out of earshot of the other two.

"You just did." Patton giggled, proud of his joke. "But really, of course you can."

"What do you do if… what do you do if you like someone, a lot, but you think he hates you?" Roman kept his eyes forward, frowning slightly.

"Hm… I don't really know." Patton kept his cool, pretending he didn't know exactly who Roman was talking about. "What's this person like?"

"Well… He's talented… and funny, and smart…" A fond smile grew on Roman's face as he talked about Virgil. He soon found himself ranting. "He listens when people talk, which is good for me because I need to talk about my problems sometimes. He's absolutely adorable, and I lo- I like him a lot." Patton could tell he was about to say 'love', but corrected himself. "But he seems to get nervous around me, almost like he wishes I wasn't there, and I just wish I could stop feeling the way I do and everything could just go back to normal!" He stopped to breathe for a second, as he'd said most of his last sentence in one breath.

"Breathe, Roman. I promise, it's not as bad as it seems." Patton put his hand on Roman's shoulder comfortingly. They approached the forest, walking through the trees and occasionally picking up sticks along the way.

"But it is, Patton. It is this bad. Because he's just so graceful, every move he makes is perfectly executed. It's almost like he can't make mistakes." Roman sighed. "But me… I'm an idiot. I can't go three steps without making a fool of mysel-"

Before he could finish his sentence, his foot caught on a tree root and he fell forward rapidly, dropping all the sticks he'd been carrying in every different direction. For a moment after this happened, he just stayed on the ground. He knew Patton was still there. But he didn't want to look at him. He'd landed in snow, and not only that, but it had started to melt. Which meant that dirty melted snow was soaking through gaps in his armor and onto his clothes. He rolled over and looked at Patton. His face and hair were also dirty. "What are the odds… that right now, when I'm talking about making a fool of myself… I make a fool of myself."

"Oh my… well, first things first…" Patton offered Roman his hand and helped him up. "Now, let's pick up those sticks and get back to Logan and Virgil."

When they finally did rejoin the other half of the group, the sun was already too far down to be able to use it to start the fire. Luckily, Logan knew another method, and soon enough they had a nice fire crackling in front of them.

"What happened while you were gone?" Virgil asked, examining Roman's face, which was now pretty dirty.

"I tripped into a pile of muddy melted snow." Roman explained bluntly.

"Oh… well, you don't look that bad." Virgil's words caught up to him, and he blushed heavily, causing him to pull the mask on to his face. "I mean it doesn't look that bad- like, the damage done to you- not that there was any, but-" He sighed, giving up. "Whatever, you know what I mean."

"Yeah, I get it." Roman laughed. Then they fell into silence, but neither was sure if it was awkward or comfortable.

Patton and Logan were sitting next to the fire. Logan had his arm (the mechanical one, which was now fully functional again) wrapped around Patton. The wizard was resting his head on the inventor's shoulder. They were just enjoying each other's company. Patton still couldn't believe any of this was real. He'd spent almost a year all alone, and suddenly he had two great friends and a wonderful boyfriend. It was almost too good to be true, but it was true, and he was absolutely over the moon.

Roman looked at the fire and thought about Virgil. He had been concerned about Roman earlier, and that wasn't something someone who hated him would be. Maybe… it was possible that Virgil liked him back? He didn't want to get his hopes up, because it was just a possibility. And it was a very unlikely possibility.

Roman was so caught up in his thoughts that he didn't notice Virgil staring at him. The assassin found himself admiring the way the warm light of the fire accentuated the features of the prince's face. It seemed to make his eyes glow like molten metal. The angular parts of his face were brought out more. In conclusion, he was absolutely gorgeous and Virgil was absolutely gay.

Before he had time to think, he was talking.

"Hey, Roman?" Once his words caught up to him, it was already too late. But hey, at least he hadn't accidentally revealed his crush. That seemed like something that would definitely happen.

"Yeah?" Roman turned to look at him, and as he did, Virgil felt his heart skip a beat. Why did he have to be so attractive all the time?

"Nevermind, it's nothing… guess I'm just tired." Great save, Virgil. Possibly the best yet.

"Oh… okay. Well… you could lean on me, if you want to sleep." Roman offered, blushing a little.

Looks like that save was more successful than he thought. Plus, it's not like it wasn't true, he was really tired. And he could definitely use a rest…

Virgil scooted a little closer to Roman, and rested his head on his shoulder. Within a few minutes, he was asleep.

"What am I supposed to do now?" Roman turned to Patton and Logan for advice. "It's like when a cat falls asleep on you, I'm not allowed to move."

"Well, the first thing to do is to admit that I was right." Patton smiled. "He does like you. Would he do that if he hated you?" He asked rhetorically, pointing to Virgil.

"Yeah, yeah, I know… okay, maybe he doesn't hate me. But that doesn't mean he likes me, it could just be a friendly thing." Roman pointed out.

Patton sighed and shook his head, and Logan rolled his eyes. There was really no getting through to him, was there.

"So, are we going to put out the fire and sleep here tonight?" Roman asked, entirely ready to just move right on from the previous topic.

"I'd think so, yes." Logan nodded. "One member of our group is already sleeping, so it would make more sense to stay here than to wake him up, since we are all tired."

"Can you guys set up the tents please?" Roman asked, gesturing to Virgil. "I'm kind of needed elsewhere right now."

"It's okay, Roman." Patton smiled. "We can do it by ourselves."

Logan and Patton went to set up the tents, making light conversation as they did. Once they had the tents all set up, Roman was half asleep. He was still awake, but barely.

"Hey, Ro? Come on, the tents are ready." Patton shook him lightly.

"But Virgil…" Roman opened his eyes sleepily and frowned a little, looking at the sleeping assassin. "How are we supposed to get him to our tent?"

"I don't know…" Patton crossed his arms.

"I'd probably be able to carry him." Roman suggested. "He's pretty light."

"Yeah, I guess that would work." The wizard nodded. "Are you sure you've got him?"

"I'm sure. You go with Logan." The prince pointed towards the tent which was now being illuminated by a lantern.

"Okay. Goodnight, Ro." Patton waved a little and left, going into the tent.

"Goodnight Patton." He replied as he watched his friend go, returning the small wave.

Once Patton was inside, Roman looked at Virgil for a moment. He just looked so… peaceful. Unbelievably peaceful, especially since he had nightmares often. Roman didn't know what it was that was helping him sleep, but whatever the case, Virgil deserved rest.

The prince turned slowly, trying his best to not wake Virgil, and positioned himself in a place where it would be easier to lift him. He carried him to their tent, carefully putting him down once they were inside. He let the assassin keep his cloak. He didn't need it anyway.

Roman took off his armor, and being as tired as he was, he fell asleep almost immediately after getting himself settled. Everything was dark for a long time, until it wasn't. The dream that followed was unpleasant.

He was standing in the throne room of his castle, definitely himself this time. Ethan was in front of him, holding his father's crown. He was talking, clearly distressed about something, but Roman couldn't hear him. Patton and Logan were standing behind him, their eyes changed from their normal color to a bright yellow. Patton's glasses were broken and bent, and Logan's mechanical arm seemed out of shape. Something was wrong. Virgil was slumped against a wall nearby, and even though he showed no signs of injury, he looked like he was in pain. Something was very wrong.

Ethan stepped closer to him. He was angry, his expression and movements holding more emotion than Roman had ever seen in him. He felt like all of this was building up to something. He was right. In one sharp movement, that seemed like slow motion, Ethan threw the crown towards the wall.

Just as it was about to hit the stone wall, the scene went dark. Roman felt someone shaking him.

~~~

Virgil had woken up about a half an hour after Roman went to sleep. He was surprised to actually feel well rested for once. No nightmares. It was a pleasant surprise. And it was so quiet in the tent. He felt like he could fall asleep again. But he didn't, instead he just stared at the ceiling of the tent and contemplated life. You know, like you do when you wake up late at night and you have nothing else to do.

It stayed like that for a while, and then something weird happened. Roman started muttering something. Of course, Virgil knew that this happened sometimes, but that time was particularly strange. With every unintelligible word, Roman seemed to get more and more distressed. Virgil placed his hand on the prince's shoulder and shook him gently.

"Ro? Hey, Ro, are you okay? Wake up." He spoke quietly, so he wouldn't disturb Patton and Logan. It went on like this until Roman finally woke up.

~~~

Roman opened his eyes to find Virgil, entirely awake, trying to get him to wake up.

"What is it?" He asked, still quite tired.

"I was getting a little worried about you." Virgil admitted. "You seemed kind of upset about something."

"It's nothing, just a dream." Roman rolled over so his back was facing Virgil.

"Do you want to talk about it?" Virgil offered. He was suddenly reminded of the moment in Patton's house, where Roman had listened to Virgil about a nightmare. So much had changed since then, it felt like forever ago.

"Would you listen?" Roman asked. Virgil was slightly surprised by this response. He thought that they'd built some sort of trust. But apparently Roman didn't even know that he'd always listen when he spoke, no matter what.

"Of course I would." Virgil nodded. "I know what it's like to get nightmares. Probably better than either of the other two."

Roman rolled on to his back, looking up at the ceiling. He sighed softly, and hesitated before finally starting to talk.

"It was like a vision of the future, but it was terrible. We were back at the castle, all four of us, and Ethan was there too. Logan and Patton were being mind controlled, or something like that, and they both looked pretty beaten up." He looked at Virgil. "And I could barely even look at you. You were in so much pain, and I wished I could have done something to help, but it was like I was frozen to my spot. And then… well…"

"You can keep going." Virgil encouraged him.

"Ethan had my father's crown. He threw it against the wall, and I didn't get to see what happened next, but I know it broke." Roman sighed. "And for some reason, that was the worst part of the dream. It kind of makes me feel stupid, because it's just an object. But for whatever stupid reason, that was worse to watch than anything else."

"Could it be some sort of symbolism?" Virgil asked. "Like, the last part of your kingdom being taken away?"

"Maybe. But still, I feel… bad." Roman told him.

"You have no reason to." Virgil put his hand on the prince's shoulder reassuringly. "You lost your father. And now, you just watched the loss of one of your last connections to him. You have nothing to feel bad about."

There was a moment of hesitation before Roman spoke again.

"... Thank you Virgil." He placed his hand over Virgil's.

"Of course." The assassin smiled softly. "Do you think you'll be able to get back to sleep?"

"Yeah, I think so." Roman nodded, returning the smile.

"Good. We'll probably be in Aurum by this time tomorrow, so we'll need some energy." Virgil told him.

"Yeah." Roman agreed, pulling his blanket back over him. He closed his eyes and rolled on to his side, but he was facing Virgil this time. Virgil did the same, but since he didn't have a real blanket, he was using Roman's cloak as a substitute.

Everything was still for a while, but then Virgil reached out and held Roman's hand, squeezing it lightly before loosening his grip again.

"What was that?" Roman asked, laughing softly.

"It's nothing, really... I know that sometimes after I have a nightmare, I like knowing that there are people I trust with me. I just… wanted to let you know that I'm still here." Virgil explained shyly.

"Oh… well, thanks." Roman's eyes were closed, and he hoped that Virgil's were too, because the prince was blushing heavily.

The two of them got to sleep again that night, and the traveling began again the next morning. In order to not cause stress, they chose not to mention the nightmare to Patton and Logan. They kept walking for most of that day, and Virgil was right about being in Aurum by that night.

The kingdom was in the middle of a bunch of hills, a place that was quite secluded, and nor very fitting for such a beautiful kingdom. The village was made up of many different shops and houses, and it spread over a vast majority of the land. In the middle of the village stood a tall elegant castle. It was made mostly of some sort of white mineral that looked like a type of quartz, and all the doors and windows were surrounded by gold. The kingdom itself wasn't as loud as Caeruleum, but it wasn't as quiet and lifeless as Shadowbrook. It was a comfortable quiet, and reminded Roman of his own kingdom. This was also the only kingdom they'd encountered that didn't have walls around it.

The people of the kingdom seemed to be preparing for some sort of event, but it wasn't clear what it was.

"Alright, let's go." Roman smiled, beginning to walk towards the kingdom. Virgil followed him.

"Yeah, let's!" Patton agreed, taking Logan's hand and walking alongside the other two.

It felt extremely satisfying to be walking towards the last kingdom. But also kind of sad. They'd come so far together, as a group, that they didn't know what they'd do once the journey was over. They'd become so used to being around each other. But they would cross that bridge when they came to it.

For now, all they had to worry about was getting to the kingdom, and getting the relic they came for.

Taglist: @musikasworld @icequeenoriginal @i-am-the-queen-you-idiot @romanknite @idkwhyimhere0o0 @mellow-yellow-nutella

#patton sanders #virgil sanders #roman sanders #logan sanders #deceit sanders #ts virgil #ts deceit #ts patton #ts roman #ts logan #logicality #prinxiety #fantasy #fanfic #shattered crown au #unsympathetic deceit

91 notes · View notes

lightbreatheslife-blog · 7 years ago

Text

Multiplicity

Originally published by Twiniversity.com. Follow the link or read below: https://www.twiniversity.com/2019/05/idea-of-twins/

We sit in firm, angular chairs in the grey-carpeted waiting room of Duke Fertility as smooth jazz wafts from speakers in the ceiling. My husband checks work email on his phone while I scribble updated contact information on a medical clipboard. My stomach is bloated and the top button on my jeans is jabbing into belly rolls I would generally rather pretend do not exist. My body is lethargic, heavy, the way it feels the morning after I’ve taken sleeping pills and the grogginess has yet to wear off. My mind, however, is alert, anxious, awaiting the next set of data to determine if our first pregnancy, at six weeks in, is still a go.

“Kathleen Straight,” the nurse calls, poking her head around a heavy wooden door to beckon us back to the land where dreams just might come true. I feel a bit like Dorothy being let in to see the Wizard--if Dorothy were bloated and nauseous and about to lose her lunch. We hop up and scuffle through the doorway, down a bright hallway shellacked with pictures of newborn babies with thank you notes taped beside. “Our little miracle! Thanks Duke Fertility!” I read quickly as the nurse ushers us into a darkened exam room. Two chest-height machines topped with computer screens flank a tissue-covered table, beside the table another chair.

“Here’s a robe—it opens in the front,” the nurse says. “Go ahead and take off everything but the robe and I’ll be back.”

Quite sure of our places, my husband settles into the chair while I change into the starched sheet with arm holes and lie on the exam table, crinkling the paper below as I adjust to get comfortable. The nurse reenters, confirms my date of birth while staring into the computer monitor, clicking the little mouse every few seconds with her index finger.

“Your numbers look great,” she says, “We are going to take a look and see if we can’t find a nice heartbeat.”

She squeezes what looks like a ballpark condiment bottle of clear goo onto a long grey wand with a chord that trails back to the machine beside her. Noticing my breathing is shallow, my heartbeat quick, I force a deep breath in and out and make a feeble attempt to relax my lower body as she inserts the machine wand up into my uterus.

Indiscriminate motions flash on a black and white screen as the nurse adjusts the wand, searching for life. The machine speakers emanate indistinguishable shushes and slurs, much like the sound of the old home videos my dad used to take (almost without fail) directly into the wind. This moment, with the screen like a black ocean and the white noise of a microphone searching for sound, this moment lasts forever. My breathing freezes somewhere halfway into an inhalation.

Shushshssh….shlurrrrr….shushshsh…schlurrrr.

“Wup, there’s a nice heartbeat!” the nurse finally says as she zeros in on a tiny black dot I never could have found in a million years amid an ocean of dark grey on the screen. “Let’s see if there’s another…”

And before we can exhale, before we can celebrate the first, the sound of a second heartbeat fills the room.

“Oh, there it is--twins! Let me just see if there are any more…”

In a split second upsurge, every conceivable emotion rockets its way from the bottom of my gut, through my heart and up into my head. Joy, fear, shock, trepidation, insecurity, wonder: all of them at once explode like a giant Fourth of July firework trapped in the space between my ears. My eyes fill with involuntary tears.

“What?! Twins!?” Justin exclaims, smiling, as the weight of tears in his eyes, too, gives way and trails down his cheeks.

We look at each other to ground ourselves, check in on a reality too surreal to grasp without each other’s witness. In this moment, we are mirrors reflecting back at one another the same kaleidoscope of emotions: we smile, eyes wide and watery, each shaking our heads to somehow let the news settle where it needs to in our brains before it can be classified as reality (much how that little disk plinks its way to its final category in the game of Plinko on The Price is Right).

“Twins?!” I finally say, ever late to the party when it comes to formulating words in the midst of intense emotions. “Twins?!…Twins.” My brain has found a tiny space. The news begins to settle in.

“Looks like your uterus dropped two eggs: see here, and here,” the nurse says as she somehow identifies two small dark spots amidst the sea of near blackness.

“Almost certainly fraternal. They’re di-di--each have their own sack and placenta--which is good, statistically lower risk…”

Nothing she is saying makes any sense to me except that there are two little lives with beating hearts growing deep inside my body.

My mind races to a conversation I had just two days earlier while walking with a friend. “What if you have twins?” she asked.

“Ha! Well, I know there’s a chance…I guess we’ll just have to figure it out, won’t we?!” I replied, laughing all the while as if there really was no chance, as if we’d never really have to (get to?) figure it out. “We did go to a prayer service a few months ago at our church and out of nowhere this lady says, ‘Lord, I feel like you’re asking me to pray for twins for this couple.’ So there’s that! Ha!” I say, again dismissing it all as the over-spiritualized fancy of a well-meaning cat lady who volunteers to pray at church and goes home to keep company with 15 felines and a basket full of crocheted cat sweaters.

We had a similar experience years back, after all, when that crazy Korean missionary had us over for dinner and prayed for Justin and me, newly dating and unsure of each other at the time, to get married. Obviously she was certifiably nuts. Except, I suppose, for the fact that in the end we did get married.

Now, sprawled on the crinkling paper of the exam table with a (seemingly magic) wand waving around my uterus, it appears that cat lady may have been on to something (or she just prays for every human to have a litter like her kitties). I rub my hand over my bloated belly and wonder how my 5’3, 115lb frame is going to grow and carry two little babies around for the next 8 months without constantly tipping over front-wise.

The nurse explains that our pregnancy is considered high risk and we will now need to pursue obstetric care through one of the established hospitals around Durham—UNC or Duke—as opposed to the zen birthing center I had my eye on (the one that lets you birth in pools of Alpine spring water blessed by the Dalai Lama while getting a henna tattoo and seaweed facial). I push aside a split second of disappointment to take in our new reality: a high risk pregnancy will mean bi-monthly doctor visits, frequent ultrasounds, and enough data about premature birth risks to make any expecting mom all but confine herself to a padded room for the duration of the pregnancy.

“Congratulations,” the nurse says, handing me a folder of photocopied pamphlets titled “What to expect when expecting multiples.”

Thoroughly checked and deemed “all systems go” by a medical team for which hearing two heartbeats is a happy but routine data point, we are dismissed until the next follow-up appointment. I squeeze myself gingerly back into my jeans--leaving the top button undone--and walk with a new sense of caution out into the parking lot. The blinding sun bounces off hot black asphalt as Justin and I attempt to wrap our heads around our burgeoning reality.

It takes several weeks before the news begins to settle into all the parts of my brain, seeping slowly into the far corners, as my body rounds into curves. My chest, my hips, my butt, my belly—all the parts of my athletic, linear figure (that just sounds so much better than flat and angular, doesn’t it?) begin to plump and push outward. It seems my body is determined to share the happy news of my pregnancy before my words can get to it. But this pregnancy is young and high risk and Justin and I agree that we’ll wait to share after the first trimester is safely behind us.

This agreement lasts about one day before I am confronted with the reality that I have no self control. I’m convinced I will actually explode like one of those gender-reveal balloons unless I can share our insane news with someone.

“So...how about I just tell my mom?” I say.

“Okay, that makes sense.”

“aaaand, Lashelle. …aaaaand Kristen and Shey? But that’s it,” I say.

“Okay. I’ll tell Micah,” Justin relents (secretly busting at the seams himself).

I think of a clever way to share with my mom—a texted picture of two buns in an oven. Well, a bun and a bagel to be precise: the grocery was low on buns. She doesn’t get it, thinks I’ve taken up baking.

I call to clarify. “We’re pregnant! With twins!”

My mom, now a 69-year-old widow and mother of four middle-aged adults, has waited years for grandkids. To her credit, she never nags or pulls the passive aggressive, “It must be so nice for all your friends’ moms to have grandkids already.” She hopes secretly, wordlessly, ready to pounce on all the baby clothes Target has to offer as soon as she’s given the word. With the news of not one but two grandkids on the way, my mom is at once thrilled and beyond mystified (and likely already in the car headed to Target).

“Where are you going to put them?” she says.

“Well…huh, I guess we’ll make the back office a nursery…”

“No, in your body! Where are you going to fit them?!”

That question is trickier than the back-office renovation. I’m not sure what to say. I have no idea where I’m going to “put them,” but I’ll do my damndest to stretch out a comfy little cubby somewhere between my neck and their eventual exit door.

There are so many questions--posed by others and myself--that I am suddenly fielding. How are you going to manage two babies at once? How will you breastfeed two? Is the fertility medicine behind the multiple pregnancy? Or is it simply (or not so simply) an act of God? Will I be put on bedrest? Can my body nurture and carry two babies to term? Sweet Jesus, will they make it? Will they both make it? Will I be a good mom? Will I ever sleep again? Where have these voluptuous breasts been all my life?

I do not have a single answer. I am in territory I have never in a million years imagined my life navigating. What I do know is multiple doctors told me I would have a difficult time getting pregnant. Multiple doctors offered multiple diagnoses—from polycystic ovarian syndrome to hypothalamic amenorrhea—as the reason I have not yet been pregnant and might not ever be. And now, seven years into our marriage, seven years of not knowing whether we would ever have the joy of welcoming a child into our family, I am pregnant—with not one, but two babies. I do not know how the story will play out, but I recognize the grace, the excessive giving of a Cosmic Mom who offers two funfetti smash cakes when I ask for a crust of bread.

“Lord, I feel like you’re asking me to pray for twins,” that cat lady prayed while Justin and I both resisted the urge to interrupt.

“Whoa, whoa. You’re off script, lady,” I wanted to say at the time. “That’s not what we asked you to pray for.”

It wasn’t. And I’m scared. But I’ve lived long enough to understand that life is so rarely filled with precisely what we ask for. And every so often, that’s a good thing. Sometimes, it’s the best thing.

Katie Straight is a writer, poet and stay-at-home mom of three: twin five-year-old boys and one two-year-old little girl. Previously, her professional work focused on international development and international education policy (Harvard, MEd ‘12). She lives in Charlottesville, VA, with her husband and kids.

Photo credit: Lashelle Chappell Photography

#twins #multiples #infertility #prayer #birth announcement #ultrasound #motherhood #pregnancy #surprise #parenting #moms #babies #lashellechappellphotography

0 notes

alanajacksontx · 7 years ago

Text

An SEO’s survival guide to Single Page Applications (SPAs)

SEOs beware: if you haven’t heard of Single Page Applications (SPA for short), or if you have been resistant to learning about these JavaScript methods for creating websites, the time for hiding your head in the sand is over.

Check out this tweet from Google Webmaster Trends Analyst John Mueller:

The web has moved from plain HTML – as an SEO you can embrace that. Learn from JS devs & share SEO knowledge with them. JS’s not going away.

— John ☆.o(≧▽≦)o.☆ (@JohnMu) August 8, 2017

John Mueller is correct. It’s not going away.

A quick search on Google Trends for “Single Page Application” reveals the sharp rise in popularity and awareness of SPAs over time:

Some developers are positively enamored with using JavaScript frameworks and libraries to create websites, and SPA popularity has been steadily growing.

Take Angular (also known as AngularJS and Angular.js), for example.

Here’s a Google Trends search for the Angular JavaScript framework showing the past 5 years, and Trends even recognizes the application platform – you can see popularity has increased greatly over the last couple of years:

The React JavaScript library shows a similar up and to the right trend:

In my role as a professional SEO, I can’t say that Single Page Applications are the rule and not the exception when it comes to how businesses choose to develop websites these days, but I am running across more and more SPAs, and so are my colleagues.

Yes, it’s true that JavaScript was never intended for web page content delivery.

Yes, it’s true that SPAs to date have not been great for SEO.

Yes, it’s true that many developers who had fun quickly creating websites using SPAs had to later spend more time fixing SEO problems than the time they would have spent if they just coded the site to deliver content via HTML5 in the first place.

But, none of that matters, my SEO friends.

Like it or not, SPAs look like they’re here to stay.

It’s time to stop thinking bad thoughts about SPAs and trying to wish them into the cornfield.

Single-Page Applications: Resistance is futile

I admit it – for a while there I was hoping I could ignore Single Page Applications, and maybe eventually SPAs would end up in the trash heap of obsolete website trends such as the <blink> tag, and web page content that’s free of annoying and intrusive advertising interruptions.

Programming and coding languages live and die by developer adoption. For example, if, by some weird turn of events, developers across the world suddenly decided they hated PHP and fell in love with some super-cool new server-side scripting language, then PHP withers, maybe even dies.

It’s just that simple.

That’s why, for example, Google has been pushing Accelerated Mobile Pages (AMP) super hard – because they need major and widespread developer adoption for AMP to succeed and not wind up as the <blink> tags’ roommate.

Talk to developers who’ve created sites using Angular, React, or other JavaScript frameworks or libraries. See if they light up as they talk about the ease and speed of development and how debugging was not as hard as the rumors have it.

SPAs are popular with developers, and that popularity is not showing any sign of slowing down.

Dipping a toe into the SPA

Looking “under the hood” of SPAs, a distinguishing characteristic is that there’s a lot less back and forth between the server and the browser making requests to the server.

After the initial JavaScript framework download to the browser and first page view, there is no page reloading going on when navigating to a second, third, and fourth (etc.) page, hence the “single page” part of Single Page Application.

After that initial JavaScript framework download and first page view, subsequent pages viewed load very quickly, exactly because of the lack of back and forth requests between the server and browser that “traditional” web sites require.

And this means a very good user experience because no extra page load means no extra wait time. And, as we all know, everyone prefers fast-loading pages.

The main aspect to remember here is that with an SPA there is far less back and forth between the browser and the server.

But JavaScript was never intended for web page content delivery

Before JavaScript started being used commonly in website development, web pages were static and created using HTML.

Using JavaScript enabled website developers to add interactivity to their web pages such as pop-up dialog boxes when a user is filling out a form, expandable content when a user clicks on text or a button, or a drop-down menu when the user hovers their mouse over a navigation element.

These and other user interactive features JavaScript allows can be executed in the browser without requiring a call to the server.

And thus, for many years, website developers used HTML for content delivery, CSS for layout and styling, and JavaScript for adding user interactivity.

It’s a fair generalization that JavaScript has become vital to websites and to a developer’s resume; JavaScript is pretty much ubiquitous. JavaScript is not that difficult to learn compared to full-blown programming languages such as Java and C++. The “J” in AJAX and jQuery is – you guessed it – JavaScript.

I only bring this up because in retrospect, and hindsight is always 20/20, we SEOs all should have seen the rise of Single Page Applications looming on the horizon.

But viewed glass-half-full, the rise of SPAs presents an opportunity for technically-minded SEOs to gain experience and become even more valuable now and in the future.

If SPAs can cause SEO issues, then why do developers create SPA websites?

If you’ve never done any coding, then you might not realize what it’s like to be in a developer’s mindset.

Think about it this way: if you were going to have to sit down and write code to create a certain web page functionality and you could either write 10 lines of code to achieve that, or write 1,000 lines of code, which would you choose? You’d opt for the expedience of 10 lines of code, right?

Developers are not lazy; they simply prefer efficiency and elegance when it comes to writing code. I’ve seen developers frame code and hang it on their office wall. Ever heard the saying “code is poetry?”

If you’re trying to get somewhere the fastest way possible, you take the shortest route, correct?

Single Page Application frameworks and libraries, in crude summary, provide building blocks that allow developers to create a website quickly and efficiently.

Consider the fact that SPAs allow developers to efficiently create modern-looking websites that load pages quickly, which makes for a great user experience, and you can see why you might choose an SPA over coding a website from scratch in HTML, CSS, and JavaScript, or hassling with the constraints of a Content Management System.

SPAs present a fast-loading user experience because they don’t need to reload most resources such as HTML, CSS, and scripts with each user interaction like a “traditional” website does. These files only require initial loading and then after that only new data is retrieved and downloaded from the server.

SPAs reduce response times primarily by moving the heavy-lifting of data processing from the server to the browser.

SEO may be a lesser consideration given the SPA developments upsides, an afterthought, or perhaps not a consideration at all during the website development process. Any SEO pro who has been in digital marketing for very long has seen the all-too-common situation where a company develops a website, only later to ask the question “how do we SEO this thing?”

Not everyone realizes that SEO should be baked-in at the beginning and not sprinkled-on at the end, or that their website development choices can have definite downstream negative impacts with respect to SEO.

JavaScript libraries vs. JavaScript frameworks

Untangling the technology behind SPAs eventually leads us to the topic of JavaScript libraries and frameworks.

Ask a developer “what’s the difference between a library and a framework” and you’ll get a lot of interesting answers.

One overriding distinction you hear repeatedly goes something like this:

The code you write calls a library, whereas a framework calls the code you write.

React and Angular are both SPAs, but React is technically a library, whereas Angular is technically a framework. However, you will hear often people refer to SPA technology generally as “JavaScript frameworks”.

Frameworks can be thought of as a structure, like a pre-fab home which comes with the framing, drywall, plumbing, and electrical wiring and all you have to do is add the appliances, windows and coverings, flooring, paint, etc.

A library can be thought of as a place that contains a set of ready to use pre-built tools and functionalities. You’d call a library in your code for a specific function.

You can see that starting a web development project using frameworks and/or libraries can streamline the process, as opposed to writing from scratch all the necessary code to create a website.

Common SEO problems of Single Page Applications

There’s a lot of talk about how well Google can handle JavaScript when it comes to crawling and indexation.

Crawling and indexing is critical to ranking.

Google discovers web pages using software called Googlebot during a very fast process often called “crawling” or “spidering”, during which it downloads an HTML file it finds, extracts the links and visits them simultaneously, and then sends the downloaded resources to the indexer.

But when it comes to a JavaScript-based single page application website, the process gets a bit more complicated.

It’s like the process noted above, but there’s a delay and extra step involved because part of the indexer must do some heavy lifting by parsing and executing the JavaScript, and the new links found then must be passed back to the crawler to look at and then sent back to the indexer; you can see that this is less efficient because of the JavaScript.

SEO is more than just having “great content” and earning high-quality links; it’s also about making your web pages easy to discover by search engines like Google and making it simple for them to know which pages are more important than other pages via internal linking.

A “traditional” HTML-based site is far easier to crawl and index, and by extension, rank. Google can get all the links easily and see what the importance of pages are via internal linking.

A JavaScript-based SPA website makes Google’s life more difficult, and some testing would seem to indicate that there may be downsides when relying on JavaScript for purposes of indexation.

Google is evidently willing to do the extra heavy lifting here, and to my mind that indicates that they’ll improve over time rather than announce to webmasters in the future that they have decided they don’t want to bother with the extra work required to crawl and index JavaScript-based sites.

Another potential SEO problem related to the extra work to discover links is that Google may have issues with evaluating the link equity of those pages.

It’s likely that in time, at least some of the SPA frameworks in popular use will evolve the rendering process to make it easier for Google to crawl and index, perhaps even making it on par with “traditional” HTML-based websites.

But in the meantime, we’re where we are and those who’ve tested how well Google can handle JavaScript-based sites have shown that Google’s ability is inconsistent, and we’re also still in a place where those who have developed SPAs frequently must use workarounds, for example using prerender.io along with Angular to serve fully-rendered pages to the crawler.

Another solution is isomorphic JavaScript, sometimes called “Universal JavaScript”, where a page can be generated on the server and sent to the browser, which can immediately render and display the page. This solves the SEO issues as Google doesn’t have to execute and render the JavaScript in the indexer.

Headless Chrome is another option recently proposed as an easy solution by a Google engineer, who also mentions another solution called Preact, which ships with server-side rendering.

It’s also a good idea to create a properly formatted XML Sitemap and submit that to Google Search Console.

Right now, there doesn’t appear to be any single solution or a paint-by-numbers approach to handing the problems you may encounter if you’re an SEO assisting a client with launching or redeveloping a website using an SPA.

It boils down to effectively communicating the correct end result that’s needed, and dealing with issues as they’re presented based on the library or framework being deployed.

Some important Single Page Application resources

Some super-sharp SEOs and developers have written helpful articles about Single Page Applications, and here are a few resources I have enjoyed that I think you will find helpful:

Tomasz Rudzki wrote an excellent post here; the title says it all: The Ultimate Guide to JavaScript SEO

Watch this video by Google ‎Senior Webmaster Trends Analyst John Mueller – he provides a terrific general overview of Single Page Applications and how Google treats them

Justin Briggs is quite conversant with both SEO and JavaScript and wrote 2 pieces you should check out: Auditing JavaScript for SEO, and Core Principles of SEO for JavaScript

Richard Baxter wrote this awhile back, but it’s still very much worth your time: The Basics of JavaScript Framework SEO in AngularJS

Will Critchlow shared this excellent post: Early Results from Split Testing JavaScript for SEO

Hold on to your hat when you click on Barry Adams’ JavaScript & SEO: The Definitive Resource List

If you’re a bit short on time, this is an excellent quick read: SEO Considerations for Single Page Applications

I definitely recommend reading this from Angular University: Angular Single Page Applications (SPA): What are the Benefits?

This Microsoft article is not geared to SEOs, but it’s a quick and helpful read: Choose Between Traditional Web Apps and Single Page Apps (SPAs)

This is also a relatively quick read covering a few different SPA types by Johann Wagner

Lastly, I strongly suggest you make time to read this, a very good overview: Single Page Applications: When & Why You Should Use Them

Final thoughts

Single Page Applications are evolving rapidly, as is the web technology landscape in general. It’s worth the effort for professional SEOs to be as conversant as possible with not only Single Page Applications, but also Accelerated Mobile Pages, Progressive Web Apps, Content Management Systems in general, and of course the tech behind how websites are coded from scratch.

My sense of the situation is that SPAs, and Google’s ability to handle JavaScript-based websites, will advance at a quickening pace because the stakeholders involved are aware that SPAs come with a definite SEO downside as it stands right now.

It’s entirely possible that in a year or so the most popular SPAs will ship with SEO solutions built in because awareness of the need for SEO friendly JavaScript-based websites is growing. But there’s no guarantee of that happening soon or at all, so my recommendation for today’s SEOs is to get excited about and embrace this technology trend.

from IM Tips And Tricks https://searchenginewatch.com/2018/04/09/an-seos-survival-guide-to-single-page-applications-spas/ from Rising Phoenix SEO https://risingphxseo.tumblr.com/post/172758142370

0 notes

oscarkruegerus · 7 years ago

Text

An SEO’s survival guide to Single Page Applications (SPAs)

Check out this tweet from Google Webmaster Trends Analyst John Mueller:

The web has moved from plain HTML – as an SEO you can embrace that. Learn from JS devs & share SEO knowledge with them. JS's not going away.